# How to connect the Neon MCP server

To connect the official Neon MCP server, add https://mcp.neon.tech/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. If your client can't use OAuth, use a Neon API key. Neon documents setup for Cursor, Claude Code, Codex and Claude.

- Endpoint: https://mcp.neon.tech/mcp
- Transport: Streamable HTTP
- Registry: com.neon/mcp 1.0.0
- Publisher documentation reviewed: 2026-11-05 (not a tested connection)
- Guide page: https://apitracker.io/mcp-guides/neon-mcp

## Before you start

- A Neon account with the projects the assistant should work on. With OAuth you authorize access to your Neon account in the browser.
- Neon recommends MCP for development and testing only. Don't connect it to production databases or to production or personal data; review each action the assistant asks to run.
- If your project uses IP allowlisting, allow the hosted server's outbound addresses listed in Neon's MCP documentation.

## Steps

1. **Open Neon's MCP server setup instructions** <https://neon.com/docs/ai/neon-mcp-server>
2. **Add the Neon MCP server to your client** Add https://mcp.neon.tech/mcp as a remote MCP server that uses the Streamable HTTP transport. Neon also publishes a config generator, a plugin for Cursor, Claude Code and Codex, and an official Claude connector for Claude.ai and Claude Desktop. The older SSE endpoints are retired and return 410 Gone, and the local stdio package is deprecated.
3. **Optional: limit what the assistant can do** To restrict the server to read operations, append ?readonly=true to the server URL, or choose read-only scope during OAuth authorization. You can also scope the server to one project, filter tool categories, or set a Postgres role for SQL tools with URL parameters described in Neon's documentation.
4. **Optional: x-read-only header**
5. **Authorize access to your Neon account in the browser**
6. **If your client can't use OAuth, use a Neon API key** Create a Neon API key and send it as a bearer token in the Authorization header. Keep the key in an environment variable or secret store, not in shared configuration.
7. **API key only: Authorization**
8. **List the server's tools**

## Questions

### What is the Neon MCP server URL?

The official Neon MCP server is at https://mcp.neon.tech/mcp and uses the Streamable HTTP transport.

### How do I authenticate with the Neon MCP server?

Sign in with OAuth when your client prompts you. If your client can't use OAuth, use a Neon API key: Create a Neon API key and send it as a bearer token in the Authorization header. Keep the key in an environment variable or secret store, not in shared configuration.

### Which AI clients can use the Neon MCP server?

Neon's documentation covers Cursor, Claude Code, Codex and Claude. Other clients that support remote Streamable HTTP MCP servers may also work.

### What do I need before connecting Neon MCP?

A Neon account with the projects the assistant should work on. With OAuth you authorize access to your Neon account in the browser. Neon recommends MCP for development and testing only. Don't connect it to production databases or to production or personal data; review each action the assistant asks to run. If your project uses IP allowlisting, allow the hosted server's outbound addresses listed in Neon's MCP documentation.

### Has this Neon MCP guide been tested?

Neon's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.

## Sources

- https://neon.com/docs/ai/neon-mcp-server (checked 2026-11-05)
- https://neon.com/docs/manage/api-keys#creating-api-keys (checked 2026-11-05)
- https://registry.modelcontextprotocol.io/v0.1/servers/com.neon%2Fmcp/versions/1.0.0 (checked 2026-11-05)
- https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization (checked 2026-11-05)

Guide JSON: https://github.com/apideck-libraries/mcp-connect/blob/626f6a146170ded34891b30dca3af26f09e07466/proposals/connection-guide/0.1/reviewed/guides/neon-mcp.json