Neon MCP Server for Cline 17 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Neon through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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.
{
"mcpServers": {
"neon": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Neon tool calls without waiting for prompts between steps. Connect 17 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
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 Cline 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 Cline via MCP
Follow these steps to integrate the Neon MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Neon
Ask Cline: "Using Neon, help me...". 17 tools available
Why Use Cline with the Neon MCP Server
Cline provides unique advantages when paired with Neon through the Model Context Protocol.
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Neon + Cline Use Cases
Practical scenarios where Cline combined with the Neon MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Neon and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Neon tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Neon and generates snapshot tests or mocks based on actual payloads
Incident response: query Neon for real-time status and let Cline generate hotfix patches based on the findings
Neon MCP Tools for Cline (17)
These 17 tools become available when you connect Neon to Cline via MCP:
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
Example Prompts for Neon in Cline
Ready-to-use prompts you can give your Cline agent to start working with Neon immediately.
"List all my Neon projects and show me which regions they're in."
"Create a new branch called 'feature-auth' from the primary branch of my project."
"Get the connection URI for the main branch of my project."
Troubleshooting Neon MCP Server with Cline
Common issues when connecting Neon to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Neon + Cline FAQ
Common questions about integrating Neon MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Neon with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Neon to Cline
Get your token, paste the configuration, and start using 17 tools in under 2 minutes. No API key management needed.