Neon is an MCP server that connects LLM clients to the Neon serverless Postgres platform. Built for software engineers, database administrators, and technical teams, it translates natural language requests into direct actions against the Neon API and live Postgres databases. Users can manage Neon projects, spin up and merge database branches, inspect table structures, and run schema migrations within their developer workflows. It also provides tools to execute SQL statements, run multi-statement transactions, list slow-running queries, and explain SQL execution plans to identify performance bottlenecks. Because it can be deployed via a remote hosted endpoint with OAuth or API key authentication, users can connect environments like Cursor, Claude Code, and VS Code without installing a local service. Configurable access parameters allow developers to restrict the server to specific functional scopes or read-only modes, keeping schema design, query tuning, and database testing safe during active local development.
Category: Cloud & Infrastructure
Tags: neon, postgres, serverless, SQL
Follow these steps to connect the remote Neon MCP server to your client: 1. Automatically configure compatible editors such as Cursor, VS Code, or Claude Code by running: bash npx neon@latest init 2. Alternatively, add the hosted remote MCP server across detected workspace agents with OAuth by executing: bash npx add-mcp "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema" 3. If configuring manually in an mcp.json or mcp_config.json file, add the server definition: json { "mcpServers": { "Neon": { "type": "http", "url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema" } } } 4. For API key authentication, include the Authorization header with your key: json { "mcpServers": { "Neon": { "type": "http", "url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema", "headers": { "Authorization": "Bearer <$NEON_API_KEY>" } } } } 5. Restart your MCP client and complete the browser OAuth flow if prompted.
Part of MCP Servers
You can configure the remote server automatically using the npx neon@latest init command in editors like Cursor, VS Code, and Claude Code. Alternatively, you can register the remote URL https://mcp.neon.tech/mcp in your client configuration using npx add-mcp or by adding an HTTP entry to your client settings file with OAuth or API key headers.
The Neon MCP server manages serverless Postgres instances on Neon. It allows clients to create and delete projects, manage database branches, inspect table structures, execute single queries or multi-statement transactions, diagnose slow queries, explain SQL statements, and prepare schema migrations using plain language prompts.
Neon supports MCP clients capable of connecting to remote HTTP servers or standard MCP integrations, including Cursor, Claude Code, VS Code through GitHub Copilot, and Kiro. It works with both OAuth and API key authentication methods.
Yes, the Neon MCP Server is an open-source project released under the MIT license. You can view the source code, review updates, and report issues on its GitHub repository at neondatabase/mcp-server-neon.
Yes, you can enable read-only mode by deselecting write permissions during OAuth authorization or by appending readonly=true to the MCP server URL query parameters. Read-only mode restricts write operations like branch creation or migrations and limits the run_sql tool to read-only queries.