2,500+ MCP servers ready to use
Vinkius

Neon MCP Server for Claude Code 17 tools — connect in under 2 minutes

Built by Vinkius GDPR 17 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add Neon as an MCP server in one command and Claude Code will discover every tool at runtime — ideal for automation pipelines, CI/CD integration, and headless workflows via the Vinkius.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Neon and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·bash
# Your Vinkius token — get it at cloud.vinkius.com
claude mcp add neon --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
Neon
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Neon MCP Server

Connect your Neon account to any AI agent and take full control of your serverless PostgreSQL infrastructure through natural conversation.

Claude Code registers Neon as an MCP server in a single terminal command. Once connected, Claude Code discovers all 17 tools at runtime and can call them headlessly — ideal for CI/CD pipelines, cron jobs, and automated workflows where Neon data drives decisions without human intervention.

What you can do

  • Project Management — List, create, update and delete Neon projects with region and PostgreSQL version selection
  • Branch Operations — Create instant branches via copy-on-write cloning, set primary branches and manage branch lifecycle
  • Compute Endpoints — Provision read-write and read-only compute hosts for your branches
  • Database Administration — Create and list PostgreSQL databases within any branch
  • Role Management — Create database roles (users) with auto-generated passwords for secure access
  • Connection URIs — Get ready-to-use psql connection strings for any branch

The Neon MCP Server exposes 17 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Neon to Claude Code via MCP

Follow these steps to integrate the Neon MCP Server with Claude Code.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using Neon

Ask Claude: "Using Neon, show me..."17 tools are ready

Why Use Claude Code with the Neon MCP Server

Claude Code provides unique advantages when paired with Neon through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly — no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using Neon tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

Neon + Claude Code Use Cases

Practical scenarios where Claude Code combined with the Neon MCP Server delivers measurable value.

01

CI/CD integration: embed Neon tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query Neon nightly and generate reports without human intervention

03

Shell scripting: pipe Neon outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query Neon status endpoints and alert on anomalies

Neon MCP Tools for Claude Code (17)

These 17 tools become available when you connect Neon to Claude Code via MCP:

01

create_branch

Optionally set a human-readable name and a parent branch ID to clone from (if omitted, clones from the project's primary branch). Branches are created instantly with zero data copy overhead. Returns the new branch along with its initial endpoints, databases and roles. Create a new branch in a Neon project

02

create_database

Requires the database name. Optionally set the owner role name (must exist in the branch — see list_roles). Returns the new database metadata. Create a new database in a Neon branch

03

create_endpoint

Specify the endpoint type: "read_write" for full access or "read_only" for read replicas. A branch can have at most one read_write endpoint. Returns the new endpoint with its connection host and configuration. Create a compute endpoint for a Neon branch

04

create_project

Optionally set a human-readable name, AWS region (e.g. "aws-us-east-2", "aws-eu-central-1") and PostgreSQL version (15, 16, 17). A default branch, database and read-write endpoint are automatically provisioned. Returns the new project along with its initial connection URIs, roles, databases and endpoints. Create a new Neon project

05

create_role

The role can be used to authenticate database connections and own databases. Provide the project_id, branch_id and desired role name. Returns the new role metadata including the generated password. Create a new database role in a Neon branch

06

delete_branch

The primary branch cannot be deleted — set another branch as primary first. Provide the project_id and branch_id. WARNING: this action is irreversible and destroys all branch data. Delete a Neon branch

07

delete_project

The project is recoverable for 7 days via the Neon console. All associated branches, databases, endpoints and data are deleted. Provide the project_id. WARNING: this action destroys all data in the project. Delete a Neon project

08

get_branch

Provide both the project_id and branch_id. Get details for a specific Neon branch

09

get_connection_uri

Optionally specify a branch_id to get the URI for a specific branch (defaults to the primary branch). The URI includes the host, database name, role and password. Use this to connect psql, ORM tools or application clients. Get a PostgreSQL connection URI for a Neon project

10

get_project

Provide the project_id (e.g. "purple-shape-411361") obtained from list_projects. Get details for a specific Neon project

11

list_branches

Each branch is an isolated PostgreSQL environment with its own compute, databases and roles. Branches can be created from any point-in-time using copy-on-write cloning. Returns branch ID, name, parent ID, primary status, creation date and current state. Use the project_id from list_projects. List branches in a Neon project

12

list_databases

Each database has a name, owner role and creation metadata. Use the project_id and branch_id to scope the query. List databases in a Neon branch

13

list_endpoints

Each endpoint has a type (read_write or read_only), host address, current state (active, idle, suspended) and autoscaling configuration. A branch can have at most one read_write endpoint. Use the project_id and branch_id. List compute endpoints for a Neon branch

14

list_projects

Each project is a workspace that contains branches, compute endpoints, databases and roles. Returns project ID, name, region, PostgreSQL version, creation date and resource usage metadata. Use this as the starting point for all Neon operations — you need a project_id to manage branches, databases or endpoints. List all Neon projects

15

list_roles

Each role has a name, creation date and privilege metadata. Use the project_id and branch_id to scope the query. Roles are used to authenticate database connections and control access. List database roles in a Neon branch

16

set_primary_branch

The primary branch is the default source for new branch cloning and receives the default read-write compute endpoint. Provide the project_id and the branch_id to promote. Set a branch as the primary branch of a Neon project

17

update_project

Provide the project_id and the new name. This does not affect branches, databases or endpoints. Update a Neon project name

Example Prompts for Neon in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with Neon immediately.

01

"List all my Neon projects and show me which regions they're in."

02

"Create a new branch called 'feature-auth' from the primary branch of my project."

03

"Get the connection URI for the main branch of my project."

Troubleshooting Neon MCP Server with Claude Code

Common issues when connecting Neon to Claude Code through the Vinkius, and how to resolve them.

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Neon + Claude Code FAQ

Common questions about integrating Neon MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect Neon to Claude Code

Get your token, paste the configuration, and start using 17 tools in under 2 minutes. No API key management needed.