2,500+ MCP servers ready to use
Vinkius
MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED
Neon

Neon MCP Server

Built by Vinkius GDPR ToolsFree for Subscribers

Manage serverless PostgreSQL databases via Neon — provision projects, branches, endpoints and roles from any AI agent.

Vinkius supports streamable HTTP and SSE.

AI AgentVinkius
High Security·Kill Switch·Plug and Play
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

What is the Neon MCP Server?

The Neon MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Neon via 17 tools. Manage serverless PostgreSQL databases via Neon — provision projects, branches, endpoints and roles from any AI agent. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.

Built-in capabilities (17)

create_branchcreate_databasecreate_endpointcreate_projectcreate_roledelete_branchdelete_projectget_branchget_connection_uriget_projectlist_brancheslist_databaseslist_endpointslist_projectslist_rolesset_primary_branchupdate_project

Tools for your AI Agents to operate Neon

Ask your AI agent "List all my Neon projects and show me which regions they're in." and get the answer without opening a single dashboard. With 17 tools connected to real Neon data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.

Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.

Why teams choose Vinkius

One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.

Build your own MCP Server with our secure development framework →

Vinkius works with every AI agent you already use

…and any MCP-compatible client

CursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWSCursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWS

Neon MCP Server capabilities

17 tools
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

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

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

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

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

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

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

get_branch

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

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

get_project

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

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

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

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

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

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

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

update_project

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

What the Neon MCP Server unlocks

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

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

How it works

1. Subscribe to this server
2. Enter your Neon API Key
3. Start managing your serverless Postgres from Claude, Cursor, or any MCP-compatible client

No more clicking through the Neon console to provision a branch or grab a connection URI. Your AI acts as a dedicated DBA.

Who is this for?

  • Developers — instantly provision development branches, grab connection URIs and create test databases without leaving your IDE
  • DevOps Engineers — audit project configurations, manage branches for CI/CD pipelines and review compute endpoint status
  • DBAs — create roles, manage databases across branches and track PostgreSQL version upgrades via conversation

Frequently asked questions about the Neon MCP Server

01

How do I create a Neon API Key?

Log in to the Neon Console, go to Account Settings > API Keys (or Organization Settings > API Keys), click Create New, choose the scope (Personal, Organization or Project-scoped), and copy the token immediately — it is shown only once.

02

What is a Neon branch and how does branching work?

A Neon branch is an isolated PostgreSQL environment with its own compute, databases and roles. Branches are created instantly using copy-on-write cloning from a parent branch (default: primary). This means zero data copy and instant provisioning. Each branch gets its own compute endpoints and can have different PostgreSQL schemas and data.

03

Can I get a ready-to-use connection URI?

Yes! Use the get_connection_uri tool with your project_id and optionally a branch_id. It returns a complete PostgreSQL connection string (postgres://user:password@host/dbname) ready to use with psql, ORMs or application clients.

04

Can the agent delete projects and branches?

Yes, the agent has tools to delete both projects and branches. Deleting a project marks it for recovery (7-day grace period) but destroys all associated data. Deleting a branch is irreversible and removes all its databases, roles and endpoints. Use caution when executing these actions.

More in this category

You might also like

Give your AI agents the power of Neon MCP Server

Production-grade Neon MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.