4,000+ servers built on MCP Fusion
Vinkius

Integrate Neon with Claude, Cursor, Chatbots & AI Agents MCP Server

Manage serverless PostgreSQL databases via Neon — provision projects, branches, endpoints and roles from any AI agent.
MCP Inspector GDPR Free for Subscribers

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
create

Create branch on Neon

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

Create database on Neon

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

Create endpoint on Neon

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

Create project on Neon

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

Create role on Neon

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

Delete branch on Neon

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

Delete project on Neon

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

Get branch on Neon

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

get

Get connection uri on Neon

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

Get project on Neon

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

list

List branches on Neon

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

List databases on Neon

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

List endpoints on Neon

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

List projects on Neon

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

List roles on Neon

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

Set primary branch on Neon

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

Update project on Neon

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

Security & Code Integrity Audit

Every tool in the Neon MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

MCP Inspector
A+Score: 100

How Vinkius protects your data

Can I set different limits for each virtual assistant on my team?

Absolutely. You have full control in our command center. You can create an AI agent that only "reads" data so the support team can answer questions, and another superpowered agent that can "edit" and "create" information exclusively for your operations team. Each AI gets exactly the level of access you allow.

Can I audit what my AI agents are doing with this integration?

Yes, Vinkius provides an immutable, HMAC-chained audit log. Every tool execution, payload, and response is tracked in real-time on your dashboard, giving you complete visibility into your agent's actions.

What if the AI ends up reading customer data or confidential information?

We have a built-in digital "bodyguard" called DLP (Data Loss Prevention). If a tool fetches data and the response contains social security numbers, credit cards, or personal customer info, Vinkius magically blocks and erases that information before it is delivered to the AI. The AI works only with what is strictly necessary, and your sensitive data never leaks.

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.

What can AI Agents do with Neon?

Build automated workflows with Cursor and Claude Code by connecting to the Neon MCP server.

Execute postgresql Commands with AI

The Neon MCP translates LLM intent into specific postgresql actions. Agents like Cursor use this to interface securely with your loved by devs infrastructure.

AI Semantic Routing for serverless

Connect your AI agent to Neon for comprehensive serverless coverage. The integration features standard schemas for reliable loved by devs tool execution.

Explore More MCP Servers

View all →