Important API details:
- The Neon MCP Server is intended for development and testing environments only — always review AI-requested actions before they are executed against your database.
- Authentication requires a valid Neon API key passed as a Bearer token in the Authorization header (e.g., Authorization: Bearer YOUR_NEON_API_KEY).
- Each use of neonctl init generates a new Neon API key; users should audit and revoke unused keys from the Neon Console under API Keys settings.
- Branch-based migrations are the recommended approach for schema changes, as they isolate modifications before applying them to the main database branch.
Server Details
| Property | Value |
|---|---|
| Transport | Streamable HTTP |
| Server Type | External |
| Endpoint | https://mcp.neon.tech/mcp |
| Categories | Database, Development & DevOps |
Authentication
This server supports the following authentication methods:OAuth
During the server onboarding flow, you will be prompted to complete the OAuth flow to grant access. See the Neon Authentication guide for step-by-step credential configuration.Header Authentication
This server authenticates via HTTP headers. During the server onboarding flow, you will be prompted to confirm the required headers. Note that you do not provide the values for the headers during the server on-boarding. Header values are provided by the users during the Auth Link flow.Getting Started
Add the server
Navigate to the Server Library and click on the New Server button. Find Neon in the Caylex Catalog.
Use in a project
Add the server to a project by configuring project connections. Its tools are now available to any agents connected to that project.