Neon MCP — Serverless Postgres via AI Agents

What it is

Neon MCP is a Model Context Protocol server that connects AI agents like Claude Code to Neon's serverless PostgreSQL platform. Through natural language, you can create database projects, branch databases for safe migrations, run SQL queries, and get query optimization suggestions. The MCP server handles authentication and API calls to Neon behind the scenes.

Neon MCP is designed for developers using AI coding agents who want database operations integrated into their AI workflow without switching to a database GUI.

How it saves time or tokens

Database operations typically require switching between your code editor, a database client, and the Neon console. Neon MCP brings all of that into your AI agent's context. Ask Claude Code to 'create a branch, apply the migration, and verify the schema' and it executes the entire workflow through the MCP server. Database branching is particularly powerful: you can test migrations on a branch without risking your production data, all from natural language commands.

How to use

1. Add the Neon MCP server to your .mcp.json (Claude Code) or MCP client config:

{
  "mcpServers": {
    "Neon": {
      "type": "http",
      "url": "https://mcp.neon.tech/mcp"
    }
  }
}

1. Restart Claude Code. Authenticate when prompted.

1. Ask natural language database questions:

'Create a new Neon database called analytics'
'Branch the production database for testing my migration'
'Run SELECT count(*) FROM users WHERE created_at > now() - interval 7 days'

Example

A typical database migration workflow using Neon MCP:

You: Create a branch from production called 'add-orders-table'
Agent: Created branch 'add-orders-table' from production.

You: On the branch, create a table:
  CREATE TABLE orders (
    id SERIAL PRIMARY KEY,
    user_id INT REFERENCES users(id),
    total DECIMAL(10,2),
    created_at TIMESTAMPTZ DEFAULT now()
  );
Agent: Table 'orders' created on branch 'add-orders-table'.

You: Verify the schema looks correct
Agent: Schema verified. The orders table has 4 columns...

You: Merge the branch to production
Agent: Branch merged. The orders table is now in production.

Related on TokRepo

• Database tools — Browse database management tools
• MCP Postgres integration — Explore PostgreSQL MCP servers

Common pitfalls

• Running destructive queries on the main branch instead of a test branch. Always create a branch before running DDL changes or data modifications. Branches are cheap and instant in Neon.
• Not setting up proper authentication. The Neon MCP server requires an API key. Follow the authentication flow on first use.
• Expecting the MCP server to handle complex multi-statement transactions. For complex migrations, write a SQL file and ask the agent to execute it, rather than sending individual statements.