1. Home
  2. Servers
  3. Databases
  4. Neon MCP Server

Server profile

Neon MCP Server

Manage Neon Postgres projects, branches, queries, and migrations through an AI assistant. The hosted MCP service supports OAuth or API keys, read-only access, and project-level scoping.

View repositoryInstall & configure

Server facts

Neon MCP Server

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
652
Last commit
Data as of

Tags

  • Database Branching
  • Neon
  • Oauth
  • Postgresql
  • Schema Migrations

Overview

Neon MCP Server gives assistants an interface to Neon Postgres and the Neon API. It supports project discovery and creation, database queries, schema inspection, connection strings, and branch management. Migration workflows use Neon branching to prepare schema changes before completing them after user confirmation. This makes the integration relevant to developers working inside an IDE who want to inspect or change a development database through conversational requests rather than switching between separate administration tools.

The README centers on a managed remote service with Streamable HTTP. Authentication can use OAuth or a bearer API key, and an initialization command can configure supported editors automatically. OAuth normally starts in the user's personal account context; organization work requires the relevant project or organization identifier. Connection settings can restrict access to a single project, select tool categories, or enable read-only mode. Read-only access removes write tools and limits the SQL tool to read-only queries, rather than merely hiding destructive names in the client. SSE remains available as a deprecated fallback. The project explicitly recommends local development and IDE use, not production operation, and asks users to review and authorize assistant actions. Those boundaries matter because unrestricted access includes project deletion, branch changes, authentication provisioning, and database migration operations.

Install & configure

Requirements

  • A Neon account
  • An MCP-compatible client
  • Node.js 18+ for the documented command-based setup
Documented launch / install command
npx add-mcp https://mcp.neon.tech/mcp

This command registers the hosted service with detected clients; it does not launch a local server. Complete OAuth authorization, or use the documented bearer API-key configuration. Production use is not recommended.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

A supported configuration example is not available for this client and transport. Check the client documentation for its connection flow; do not substitute an undocumented JSON format.

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

Cursor configuration
{
  "mcpServers": {
    "mcp-server-neon-neondatabase-labs": {
      "url": "https://mcp.neon.tech/mcp"
    }
  }
}

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

VS Code configuration
{
  "servers": {
    "mcp-server-neon-neondatabase-labs": {
      "type": "http",
      "url": "https://mcp.neon.tech/mcp"
    }
  }
}

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

Windsurf configuration
{
  "mcpServers": {
    "mcp-server-neon-neondatabase-labs": {
      "serverUrl": "https://mcp.neon.tech/mcp"
    }
  }
}

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Code configuration
{
  "mcpServers": {
    "mcp-server-neon-neondatabase-labs": {
      "type": "http",
      "url": "https://mcp.neon.tech/mcp"
    }
  }
}

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

Source: repository tool metadata and repository README. Tool descriptions are a documented snapshot, not a live capability check.

ToolWhat it does
__node_versionReport the Node.js runtime version used by the MCP server.
list_projectsList projects available in the user's Neon account.
create_projectCreate a Neon project for a new database workflow.
delete_projectRemove an existing Neon project.
describe_projectInspect the details of a Neon project.
run_sqlExecute one SQL statement, with read-only queries enforced in read-only mode.
run_sql_transactionExecute multiple SQL statements as a database transaction.
describe_table_schemaInspect the structure of a selected database table.
get_database_tablesList tables in a Neon database.
create_branchCreate a branch within a Neon project.
prepare_database_migrationPrepare database schema changes using the documented migration workflow.
complete_database_migrationFinish a confirmed migration and remove its temporary branch.
describe_branchInspect a branch's databases, schemas, tables, views, and functions.
delete_branchRemove a branch from a Neon project.
get_connection_stringRetrieve a PostgreSQL connection string for a Neon database.
provision_neon_authSet up Neon project authentication through the documented Stack Auth integration.
list_shared_projectsFind Neon projects that have been shared with the current user.
list_organizationsList organizations available through the connection.
list_branch_computesInspect compute resources associated with a branch.
compare_database_schemaCompare database schemas through the schema tool category.
list_slow_queriesInspect slow-query information for performance investigation.
explain_sql_statementInspect how a SQL statement is planned.
searchSearch through the server's retrieval interface; unavailable with project scoping.
fetchRetrieve content through the server's retrieval interface; unavailable with project scoping.
list_docs_resourcesDiscover available documentation resources.
get_doc_resourceRetrieve a selected documentation resource.
reset_from_parentReset a branch from its parent; requires write access.
provision_neon_data_apiProvision the Neon Data API with write-enabled access.
prepare_query_tuningPrepare query tuning through a write-enabled workflow.
complete_query_tuningComplete the documented query-tuning workflow with write access.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Inspect Neon project databases and table schemas from an IDE.
  • Run SQL or multi-statement database transactions.
  • Prepare schema migrations using development branches.
  • Limit an assistant to read-only queries in a selected project.

Strengths

  • Hosted access supports OAuth without manually configuring an API key.
  • Includes project scoping, category filtering, and enforced read-only SQL.
  • Uses database branches in migration workflows.

Limitations

  • The README advises against production use.
  • Write-enabled access includes destructive project and branch operations.
  • Organization projects require explicit context when using OAuth.

Frequently asked questions

Not with hosted OAuth setup. API-key authentication is also supported for clients or agents that cannot use OAuth.

Yes. run_sql remains available but is restricted to read-only queries; write operations are disabled.

Yes. The projectId URL parameter scopes operations, and category can further restrict tool groups.

No. The README recommends development and IDE integrations and explicitly advises against production use.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

DBHub

Databases

DBHub exposes SQL execution and database discovery through a small MCP interface. It spans five database engines, supports multiple configured connections, and includes a web workbench for use without an assistant.

nodestdio3,664 GitHub stars

MCP Toolbox for Databases

Databases

MCP Toolbox for Databases connects agents and IDEs to enterprise data through prebuilt tools or custom query definitions. It combines database access with connection pooling, authentication integration, and observability.

gostdio16,669 GitHub stars

MCP Server for MySQL

Databases

MCP Server for MySQL lets Claude and other AI clients inspect schemas and execute SQL. It defaults to read-only access, with optional write flags, SSH tunneling, multi-database support, and result redaction.

nodestdio2,166 GitHub stars

Supabase MCP Server

Databases

Connect AI assistants to Supabase projects for SQL, schema changes, debugging, and Edge Functions. Hosted HTTP setup supports project scoping, read-only access, and selectable feature groups.

nodestdio2,955 GitHub stars

Postgres MCP Pro

Databases

Give assistants PostgreSQL schema access, SQL execution, health checks, and performance analysis. Postgres MCP Pro adds query plans and hypothetical index evaluation with configurable read-only operation.

pythonstdio3,403 GitHub stars

MySQL MCP Server

Databases

Expose MySQL schema inspection, data samples, and SQL execution to MCP assistants. It supports multi-database access, optional SSH tunnels, and local or network deployment, with database permissions controlling available operations.

pythonstdio1,399 GitHub stars

MongoDB MCP Server

Databases

MongoDB MCP Server connects AI clients to MongoDB databases and Atlas. Its tools cover queries, schema inspection, database changes, and MongoDB knowledge searches, with read-only launch examples for safer exploration.

nodestdio1,143 GitHub stars

Query MCP for Supabase

Databases

Query MCP connects coding assistants to Supabase SQL, schema changes, project management, and user administration. It includes SQL risk controls, but its author has stopped active maintenance.

pythonstdio832 GitHub stars