Developer · Remote MCP server
Neon
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.neon/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- com.neon
- Namespace
- Namespace verified by the MCP Registry via the domain neon.com · how
- Listed under
- PostgreSQL MCP servers
- Website
- neon.com/docs/ai/neon-mcp-server
- Repository
- github.com/neondatabase/mcp-server-neon
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.neon.tech/mcp | Authorization (secret), x-read-only |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Neon
Neon is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.neon.tech/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares HTTP headers for the connection: Authorization (secret) and x-read-only. A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, neon.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| Nel VeilFree passive security scanning - check any domain's DMARC, TLS, headers, and exposures. | Local · stdio |
| Neleto CMSCreate and edit pages, posts, events, files and layouts on your Neleto CMS site. EU-hosted. | Remote · HTTP |
| Nelly the ElephantSearch and resume past Claude Code conversations. An elephant never forgets. | Local · stdio |
| Nemesis ShieldPositive-security for apps, APIs, LLMs and edge, plus fraud scoring and identity/AML screening. | Local · stdio |
| Neon Zero-Trust GatewayZero-Trust MCP gateway securing internal database tools behind an API key firewall. | Remote · SSELive check: ✗ no handshake |
| Neon Zero-Trust MCP GatewayAI security firewall & DLP proxy protecting API keys and blocking destructive commands. | Remote · HTTP, SSELive check: sign-in required |
| Neonia: The Cloud Backend for AI AgentsMultiple MCP tools, persistent graph memory, token-saving data pointers, and more. | Remote · HTTPLive check: ✗ no handshake |
| NeoSQL MCPUse NeoSQL Desktop database connections from MCP hosts: schemas, SQL, ERD, and code generation. | Local · stdio |