MCP Server Neon logo

MCP Server Neon

by neondatabase

Manage Neon Postgres projects, branches, schemas, endpoints, and queries through natural-language MCP requests.

Install MCP Server Neon

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "neondatabase-mcp-server-neon": {
      "command": "npx",
      "args": [
        "-y",
        "neon@latest"
      ],
      "env": {
        "NEON_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

neondatabase/mcp-server-neon connects MCP clients to Neon through a remote server and the Neon API. It translates natural-language requests into database-management operations covering projects, branches, compute endpoints, schemas, queries, and related services. Reach for it when an agent needs to inspect or change Neon databases during local development or IDE work. The project warns against using it in production because requests can perform consequential database operations.

Use cases

  • Create Neon Postgres projects and databases
  • Create branches for schema changes and migrations
  • Run queries and inspect database schemas
  • Review project query logs and compute endpoints
  • Provision Neon Auth or the Data API

Key features

  • Natural-language Neon database management
  • Project, branch, endpoint, and snapshot operations
  • Schema comparison and migration support
  • Postgres querying and query-log access
  • Neon Auth and Data API provisioning
  • Category-filtered remote MCP access

Tools80

What MCP Server Neon lets your agent do. Expand a tool for its parameters.

Self-reported~290 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

19/23 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · neon@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars655Stargazers on the source repository.
npm downloads19kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Neon works

What neondatabase/mcp-server-neon does

neondatabase/mcp-server-neon exposes Neon database management through the Model Context Protocol. An MCP client can use natural-language instructions to work with Neon projects and their Postgres resources instead of calling the Neon API directly or writing every management operation by hand.

Supported work includes listing, describing, and deleting projects; creating branches; resetting a branch from its parent; inspecting schemas; comparing database schemas; running queries; reviewing query logs; and managing compute endpoints. The server also exposes capabilities for snapshots, Postgres roles, database creation, Neon Auth, the Data API, observability, documentation, functions, storage, and realtime features.

How it works

The hosted endpoint receives MCP requests and translates them into calls to the Neon API. Clients can connect over HTTP to https://mcp.neon.tech/mcp. The endpoint can publish all available tool categories or restrict the connection to selected categories such as projects, branches, endpoints, querying, and schema.

Natural-language requests can combine multiple operations. For example, an agent can create a project, create a database table, or apply a schema change to a branch. The MCP client remains responsible for presenting and authorizing requests before execution.

Setup and configuration

Three connection approaches are described:

  • Run npx neon@latest init to configure the server for Cursor, VS Code with GitHub Copilot, or Claude Code. This flow authenticates with OAuth, creates a Neon API key, and updates the editor configuration.
  • Connect to the managed endpoint with OAuth using npx add-mcp, or add the endpoint to an MCP configuration file. OAuth avoids storing an API key in the client.
  • Connect to the same endpoint with a Neon API key in the Authorization: Bearer header.

A Neon account and an MCP client are required. Node.js version 18 or newer is listed as a prerequisite. If Neon IP Allow is enabled, the two documented static MCP service IP addresses must be added to the allowlist. OAuth connections default to projects in a personal Neon account; organization projects require an org_id or project_id in the request.

Tools and capabilities

The published categories and tool names cover:

  • Projects, branches, endpoints, snapshots, schemas, and database queries
  • Project listing, project deletion, project descriptions, branch creation, and parent resets
  • Schema comparison, query-log retrieval, Postgres role listing, and Postgres database creation
  • Neon Auth and Neon Data API provisioning
  • Documentation lookup, search, fetching, and feedback submission
  • Functions, storage, realtime, observability, and branch compute inspection

Limitations and notes

The server grants access to database-management actions through natural language. Review and authorize requests before they run, and restrict access to trusted users and applications. The project positions the server for local development and IDE integrations rather than production environments. A client can request read or write OAuth scopes; a wildcard scope is treated as write by the server.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Neon

neondatabase/mcp-server-neon is an MCP server that connects AI clients to Neon Serverless Postgres through the Neon API. Its main tools manage projects, branches, endpoints, schemas, snapshots, queries, query logs, Postgres databases, Neon Auth, and the Data API using natural-language requests.

Use `npx neon@latest init` for automatic setup in Cursor, VS Code with GitHub Copilot, or Claude Code. Alternatively, connect an MCP client to `https://mcp.neon.tech/mcp` with OAuth or configure a Neon API key in the Authorization header.

Yes, it works with Cursor. Run `npx neon@latest init` to configure it automatically, or add the managed HTTP endpoint to Cursor's MCP configuration. The repository also provides a Cursor installation link.

Yes, add category query parameters to the managed endpoint URL. Categories such as projects, branches, endpoints, querying, and schema can be published selectively; using the unfiltered endpoint publishes every category.

No; the project recommends it for local development and IDE integrations, not production environments. Natural-language requests can make powerful database changes, so review and authorize actions and restrict access to trusted users and applications.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Neon AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/neondatabase-mcp-server-neon?style=directory)](https://allmcps.com/mcp/neondatabase-mcp-server-neon)
HTML Embed
<a href="https://allmcps.com/mcp/neondatabase-mcp-server-neon"><img src="https://allmcps.com/api/badge/neondatabase-mcp-server-neon?style=directory" alt="MCP Server Neon on AllMCPs" /></a>