2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 17 Tools IDE

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Neon through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.

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·json
{
  "mcpServers": {
    "neon": {
      "url": "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.

Windsurf's Cascade agent chains multiple Neon tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 17 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

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 Windsurf 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 Windsurf via MCP

Follow these steps to integrate the Neon MCP Server with Windsurf.

01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

02

Add the server

Paste the JSON configuration above into mcp_config.json

03

Save and reload

Windsurf will detect the new server automatically

04

Start using Neon

Open Cascade and ask: "Using Neon, help me...". 17 tools available

Why Use Windsurf with the Neon MCP Server

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

01

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

02

Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively

03

JSON-based configuration means zero code changes: paste a URL, reload, and all 17 tools are immediately available

04

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Neon + Windsurf Use Cases

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

01

Automated code generation: ask Cascade to fetch data from Neon and generate models, types, or handlers based on real API responses

02

Live debugging: query Neon tools mid-session to inspect production data while debugging without leaving the editor

03

Documentation generation: pull schema information from Neon and have Cascade generate comprehensive API docs automatically

04

Rapid prototyping: combine Neon data with Cascade's code generation to scaffold entire features in minutes

Neon MCP Tools for Windsurf (17)

These 17 tools become available when you connect Neon to Windsurf 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 Windsurf

Ready-to-use prompts you can give your Windsurf 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 Windsurf

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

01

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Neon + Windsurf FAQ

Common questions about integrating Neon MCP Server with Windsurf.

01

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
02

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
03

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.

Connect Neon to Windsurf

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