MCP server · Databases
Neon MCP server
Lets an assistant manage Neon Postgres projects and branches, run SQL, and test schema migrations on a temporary branch first.
- Maintainer
- Neon (official)
- Licence
- MIT
- Runs
- Remote (URL)
- Sign-in
- OAuth sign-in in the app
- Registry version
- 1.0.0 (updated 2026-09-17)
- Last activity
- 2026-10-13
Overview
What it does
Neon’s MCP server is a hosted endpoint at mcp.neon.tech that turns plain-language requests into calls to the Neon API and to your Postgres databases. You sign in with OAuth, or send a Neon API key in an Authorization header, and nothing runs on your machine. URL parameters limit what the assistant sees: tool categories, a single project, read-only mode, or a fixed Postgres role for every query.
It suits day-to-day development on Neon. The assistant can create a project or branch, inspect tables, explain a slow query and suggest an index. Migrations and query tuning run on a temporary branch first, so you can review the result before it reaches your main branch. Neon says the server is meant for local development and IDE use, not production. If you would rather not set up a key by hand, the README also offers “npx neon@latest init” to configure your editor in one step.
Tools
What the assistant can do
- Project, organisation and branch management
- SQL execution with run_sql and run_sql_transaction
- Schema inspection and schema diffs between branches
- Migrations tested on a temporary branch before they are applied
- Query tuning, slow-query lists and EXPLAIN plans
- Compute endpoints, snapshots, Neon Auth and Data API tools
- Search across organisations, projects and branches
Install
Install Neon MCP server in your app
You need:
- A Neon account
- An MCP client that supports remote servers and OAuth
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local --transport http neon 'https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema'
- neon: if the server needs a sign-in, the app will ask (run /mcp in Claude Code).
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"neon": {
"type": "http",
"url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema"
}
}
}
- neon: if the server needs a sign-in, the app will ask (run /mcp in Claude Code).
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {}
}
- neon is a remote server: add it as a custom connector (Customize → Connectors → + Add → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors), with the URL https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema.
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"neon": {
"url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema"
}
}
}
- neon: if the server needs a sign-in, the app will ask.
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"servers": {
"neon": {
"type": "http",
"url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema"
}
}
}
- neon: if the server needs a sign-in, the app will ask.
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"neon": {
"url": "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema"
}
}
}
- neon: if the server needs a sign-in, the app will ask.
Want it alongside other servers? Open Neon MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- With write access the assistant can create and delete projects and branches and run any SQL, so review each action before it runs.
- Add readonly=true to the URL to remove write tools; run_sql then runs each query in a READ ONLY transaction. Add projectId to limit it to one project.
- Use roleName to run all SQL as a Postgres role with only the grants the agent needs.
- A remote server sees whatever the assistant sends it. Sign in with the narrowest access the service offers. See how to choose a safe server.
Why it’s listed
Why we list it
Official, actively developed and hosted, with unusually fine-grained scoping for a database server.
Related
More MCP servers
- Prisma MCP serverLets an assistant create and query Prisma Postgres databases, restore backups, and manage Prisma Compute apps and Object Storage.
- MongoDB MCP ServerLets an assistant query and manage MongoDB databases and, with Atlas credentials, manage Atlas projects, clusters and users.
- Redis MCP ServerLets an assistant read and write Redis data types, streams and JSON documents, and run vector search on a Redis database.
- ClickHouse MCP ServerLets an assistant list ClickHouse databases and tables and run SQL queries, read-only by default, plus optional embedded chDB queries.
- DuckDB / MotherDuck Local MCP ServerLets an assistant run DuckDB SQL on local files, in-memory databases, S3-hosted databases or MotherDuck, read-only unless you allow writes.
- mcp-server-qdrantGives an assistant a semantic memory: it stores notes in a Qdrant collection and finds them later by meaning rather than exact words.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?