Neon MCP Server
Official remote MCP server for Neon Postgres, projects, branches, SQL, schema, and migrations.
- Skill Road
- Neon MCP Server
Categories
Description
Neon MCP Server is Neon’s official Model Context Protocol server for working with Neon Postgres. It connects natural language in an MCP client to the Neon API and selected database capabilities. The direct product link points to Neon documentation, while the neondatabase/mcp-server-neon repository contains source code, setup options, and the license. According to the provider, the server can manage projects and branches, run SQL, describe database schemas, prepare migrations, and provide Neon documentation. Its focus is therefore not generic data analysis, but database-adjacent development and operations work.
Remote server for Postgres workflows
Neon documents several setup paths. The quick API-key flow runs npx neon@latest init and, according to the README, configures the MCP Server for Cursor, VS Code/GitHub Copilot, and Claude Code. Alternatively, the hosted remote server can be connected through https://mcp.neon.tech/mcp using OAuth or an API key. SSE remains available for older clients, but Streamable HTTP is the modern path. The hosted server runs as a Next.js application on Vercel according to the repository; local development uses Node.js, Corepack, and pnpm.
Projects, branches, queries, and migrations
The practical value sits in common Postgres tasks that developers otherwise spread across a console, SQL client, and codebase. An agent can summarize a Neon project, explain table structures, run read-only SQL queries, use branches for changes, or prepare a migration. The approach is especially useful for feature work with branching: a database schema can be inspected or changed in an isolated Neon branch before anything moves toward the main branch. For editorial, analysis, and support work, the server can also help understand existing data structures without manually clicking through the UI first.
Security, read-only mode, and data flow
Neon explicitly warns that the MCP Server grants powerful database management capabilities through natural language. Users should review and authorize actions requested by the LLM, and Neon does not recommend using the server in production environments. Project scoping, organization context, OAuth scopes, and read-only mode are central. readonly=true can disable write tools such as project or branch creation and migrations; read tools such as schema and performance inspection remain available depending on configuration. If IP allowlists are enabled, the README lists static IP addresses for mcp.neon.tech that must be deliberately allowed.
License, GitHub stars, and fit
The repository is MIT licensed. The GitHub API reported exactly 629 stars on 2026-09-07; that snapshot reflects popularity, not a security or quality guarantee. The server itself is open source, but using it requires a Neon account and appropriate permissions. Public catalog copy should not state fixed prices; current plan and usage terms are published by Neon. This entry fits DevOps and Data Analysis because it combines database operations, schema understanding, queries, and migration-adjacent automation. A safe starting point is a test project with a read-only URL or a tightly scoped API key.
Requirements
MCP client, Neon account, and depending on setup Node.js 18+, OAuth, or a Neon API key.
Installation instructions
Neon MCP can manage Postgres projects, branches, and databases. This walkthrough starts with its hosted read-only connection. Neon recommends the server for local development and IDE integration, not production database environments. Use a development branch without real customer records.
Step 1: Prepare development access
You need a Neon account and an HTTP MCP client supporting OAuth. Identify the test branch in the Neon console and note its project and branch IDs. Remote access requires no local server process. Check Claude Code in the terminal:
claude --version
Step 2: Connect Neon with read-only access
Register the explicitly restricted endpoint:
claude mcp add --transport http neon "https://mcp.neon.tech/mcp?readonly=true"
Expected result: a connection named neon. readonly=true restricts the exposed tools; telling the agent not to write is not an equivalent technical control.
Step 3: Review OAuth authorization
Inside an interactive Claude Code session, open:
/mcp
Select neon, sign in through the browser, and inspect the confirmed grant. Provide project or organization IDs explicitly when working with organization-owned projects. Authorization fixed by readonly=true cannot simply be expanded to writes in the dialog. A different grant requires deliberate reauthorization.
Step 4: Inspect the test branch
Replace the placeholders with your development project and branch identifiers and send this message to the client:
Use neon for project PROJECT_ID and branch BRANCH_ID. Describe only the existing table schema. Do not create projects, branches, tables, or migrations, and do not output credentials.
Compare the answer with the console. Review later SQL requests, especially filters and data volume. Read-only access does not prevent sensitive information from entering the model context.
Step 5: Understand the automatic setup alternative
With Node.js and npm available, Neon also provides this setup assistant:
npx neon@latest init
It can detect editors, authenticate through OAuth, create an API key, and configure additional agent tooling. This is an alternative, not a required extra step after the remote configuration above. Inspect proposed configuration changes and manage duplicate connections deliberately. The local stdio option requires Node.js and a Neon API key; consult the repository for details.
Alternative: configure read-only access in Cursor
Merge this entry into the existing MCP configuration and complete OAuth afterwards:
{
"mcpServers": {
"neon": {
"type": "http",
"url": "https://mcp.neon.tech/mcp?readonly=true"
}
}
}
For connection errors, check the account, project identifier, and any Neon IP allowlist. Migrations and branch creation require write privileges and should follow a separate, reviewed development workflow. Official source: https://github.com/neondatabase/mcp-server-neon. No authenticated hands-on test was performed.
npx neon@latest init
Authentication
OAuth or Neon API key; read-only mode and tool categories can be limited through scopes or URL parameters.
Required access permissions
Permissions follow OAuth scopes, API key, project/organization context, and URL parameters such as readonly or category.
Transmitted or stored data
Tool calls go to the Neon API and database functions; responses return to the MCP client.
Security risks
Natural language can trigger powerful database changes. Review actions, avoid production access, and use read-only/project limits.
License and costs
- License
- MIT
- Cost
- free
The server is MIT licensed. Costs depend on the Neon account, resource usage, selected plan, and AI client.
Alternatives
Not recorded yet.
At a glance
- Provider
- Neon
- Status
- Official server
- Deployment
- Remote
- Current version
- Not recorded yet.
- GitHub stars
- 665
- Last reviewed
- 07.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.