What is the Model Context Protocol (MCP)?
MCP is a standardized protocol designed to manage context between large language models (LLMs) and external systems. Neon MCP Server implements this protocol to bridge natural language and the Neon API.
@neondatabase
Basic information
MCP server for interacting with Neon Management API and databases
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-server-neon": {
"command": "npx",
"args": [
"neonctl@latest",
"init"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Neon MCP Server is an open-source tool that lets you interact with your Neon Postgres databases in natural language. It acts as a bridge between natural language requests and the Neon API, enabling you to manage tasks such as creating projects and branches, running queries, and performing database migrations seamlessly.
Set up by running npx neonctl@latest init for quick OAuth-based configuration in Cursor, VS Code, and Claude Code, or connect to the remote managed server via OAuth or an API key. You need an MCP client, a Neon account, Node.js >= 18, and if IP Allow is enabled, add the listed static IPs to your allowlist. Configure your client with the URL https://mcp.neon.tech/mcp and optionally add headers, query params, or use the deprecated SSE endpoint https://mcp.neon.tech/sse.
MCP is a standardized protocol designed to manage context between large language models (LLMs) and external systems. Neon MCP Server implements this protocol to bridge natural language and the Neon API.
You need an MCP client application, a Neon account, and Node.js version 18 or higher. If IP Allow is enabled on your account, you must add `34.192.103.46` and `23.22.233.166` to your allowlist.
Yes. Read-only mode restricts tools to read-only actions (e.g., listing projects, querying data) and is enabled either by selecting read-only in the OAuth UI or by adding `?readonly=true` to the server URL. The `run_sql` tool remains available only for read-only queries.
No. The README warns that it is intended for local development and IDE integrations only and should not be used in production environments, as it can execute powerful operations that may lead to accidental or unauthorized changes.
Two methods: OAuth-based (recommended, no API key needed) or API key–based (set `Authorization: Bearer <key>` header). OAuth scopes (`read`, `write`, `*`) control permissions, and you can also use the `org_id` or `project_id` in prompts to scope operations to specific organizations or projects.
A Model Context Protocol server that provides read-only access to MySQL databases. This server enables LLMs to inspect database schemas and execute read-only queries.
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma
Postgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.

Model Context Protocol Servers
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases
Comments