# Neon MCP server > Manage Neon serverless Postgres projects, branches, SQL queries and schema migrations in natural language. - Listing: https://mcp.tc/i/neon - Connect: use the server's own URL `https://mcp.neon.tech/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Databases & Backend](https://mcp.tc/c/databases) - Vendor: Neon - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: - Docs: - Repository: - Package: npm `@neondatabase/mcp-server-neon` ## About Connects an AI assistant to the Neon API and to Neon Postgres databases. You can create projects and branches, manage compute endpoints, run SQL queries, inspect schemas and perform migrations by describing what you want. It runs as a hosted streamable HTTP endpoint at mcp.neon.tech with OAuth sign-in. You can also send a Neon API key in the Authorization header, and an optional x-read-only header limits the tools. Tool categories can be filtered through URL query parameters. The vendor advises using it for local development, not production. ## What it can do - Create and manage Neon projects and branches - Manage compute endpoints - Run SQL queries against Neon databases - Inspect database schemas - Run schema migrations using branches - Filter exposed tools by category or read-only mode ## Example prompts - "Create a new Postgres database called my-database with a users table." - "Run a migration on my-project that adds a created\_at column to users." - "Summarize all of my Neon projects and the data in each one." - "Create a branch of my-project to test a schema change." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http neon https://mcp.neon.tech/mcp ``` 2. Start Claude Code, type `/mcp`, pick **neon** and choose **Authenticate**. A browser window opens for the Neon sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Neon** and paste this URL: ```url https://mcp.neon.tech/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Neon asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.neon.tech/mcp` and click **Add**. 3. Click **Connect** and sign in when Neon asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.neon.tech/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Neon to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "neon": { "url": "https://mcp.neon.tech/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"neon","type":"http","url":"https://mcp.neon.tech/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "neon": { "type": "http", "url": "https://mcp.neon.tech/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "neon": { "serverUrl": "https://mcp.neon.tech/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add neon --url https://mcp.neon.tech/mcp codex mcp login neon ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.neon] url = "https://mcp.neon.tech/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http neon https://mcp.neon.tech/mcp ``` Then, inside Gemini CLI, run `/mcp auth neon` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "neon": { "type": "http", "url": "https://mcp.neon.tech/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.neon.tech/mcp`. ## Details - Server version: 1.0.0 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/neon (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report