What is Neon's 'Zero-Copy Branching' and how do I use it through the agent?

Zero-copy branching allows you to clone a multi-terabyte database instantly using Copy-on-Write (CoW). Use the `create_branch` tool by providing a parent branch ID. Your agent will trigger the backend to generate an isolated clone in milliseconds, perfect for running migrations or testing features against production-like data.

Can my agent retrieve the exact connection strings for my compute endpoints?

Yes. Use the `list_endpoints` tool with your Project ID. Your agent will retrieve the explicit hostnames (e.g., `ep-misty-water-123.aws.neon.tech`) used to actively ingest real query traffic to your serverless Postgres branches.

How do I check the storage consumption for a specific Neon branch?

The `get_branch` tool retrieves the deconstructed execution footprint of an individual branch. Your agent will report the storage limits and exact number of bytes consumed uniquely by that branch's data delta since it split from its parent.

Neon (Serverless PostgreSQL) MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Neon (Serverless PostgreSQL)
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

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 (Serverless PostgreSQL) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "neon-serverless-postgresql": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 (Serverless PostgreSQL) MCP Server

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

GitHub Copilot Agent mode brings Neon (Serverless PostgreSQL) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Project Orchestration — List all managed serverless workspaces and retrieve detailed regional deployment metrics and regional Caps directly from your agent
Zero-Copy Branching — Instantly spawn brand new database branches (CoW) containing identical production schema duplicates for isolated feature testing or rapid CI/CD cycles
Compute Management — Discover and list explicit compute endpoints (e.g., ep-misty-water-123) to retrieve the exact connection strings required for your application drivers
Branch Audit — Inspect the execution footprint of specific branches, tracking storage deltas and timeline points (LSN) to understand exactly when a branch split from its parent
Database Inventory — Enumerate internal SQL database schemas and catalog namespaces mapped inherently to specific branches to guide your connection logic
Role Management — List and audit PostgreSQL user identities and credential roles capable of querying against specific bounded logical nodes securely
Resource Provisioning — Initialize fresh serverless workspaces or permanently wipe out entire database ecosystems with irreversible architectural commands

The Neon (Serverless PostgreSQL) MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 (Serverless PostgreSQL) to VS Code Copilot via MCP

Follow these steps to integrate the Neon (Serverless PostgreSQL) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Neon (Serverless PostgreSQL)

Ask Copilot: "Using Neon (Serverless PostgreSQL), help me...". 10 tools available

Why Use VS Code Copilot with the Neon (Serverless PostgreSQL) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Neon (Serverless PostgreSQL) through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Neon (Serverless PostgreSQL) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Neon (Serverless PostgreSQL) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Neon (Serverless PostgreSQL) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Neon (Serverless PostgreSQL) to VS Code Copilot via MCP:

create_branch

Duplicates Petabytes of PostgreSQL storage instantly using filesystem CoW links, generating an isolated query testing ground tied back directly to the `parent_id` source. Spawn a zero-copy clone (Branch) of a PostgreSQL dataset

create_project

Provision an empty Neon Project Serverless Workspace

delete_project

Destroys all edge-served connection strings, severs active client connections, and completely evaporates physical NVMe-backed storage blocks. Permanently wipe out a complete Neon Postgres ecosystem

get_branch

Deconstruct the execution footprint of one specific Branch

get_project

g. AWS eu-central-1) and storage size consumption caps bounded specifically to this project ID. Analyze core routing logic mapping a Neon Project

list_branches

Maps `main` branches to experimental `feature-123` branches spawned in milliseconds containing identical production schema duplicates. List Copy-on-Write (CoW) Branches resolving to a Project

list_databases

g. `main_db`, `analytics_db_schema`). Crucial for forming absolute Postgres connection strings resolving directly to correct schemas. Identify internal SQL Database schemas mapped inherently to a Branch

list_endpoints

eu-central-1.aws.neon.tech`) used practically within standard PgBouncer drivers to actively ingest real query traffic to associated active branches. Discover connection routing endpoints spanning the Neon project

list_projects

List architectural Neon Serverless PostgreSQL Projects

list_roles

Maps directly to standard SQL internal `CREATE USER` outputs wrapped safely upstream. Extract PostgreSQL user Roles operating on a Branch

Example Prompts for Neon (Serverless PostgreSQL) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Neon (Serverless PostgreSQL) immediately.

"List all serverless projects in my Neon account"

"Create a new branch called 'feat-user-auth' from the 'main' branch"

"What databases and roles are configured on branch 'br-12345'?"

Troubleshooting Neon (Serverless PostgreSQL) MCP Server with VS Code Copilot

Common issues when connecting Neon (Serverless PostgreSQL) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Neon (Serverless PostgreSQL) + VS Code Copilot FAQ

Common questions about integrating Neon (Serverless PostgreSQL) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.