1. Home
  2. Neon MCP Server
  3. Neon MCP Server for VS Code: Setup & Config

Data as of

Neon MCP Server for VS Code: Setup & Config

VS Code: Manage Neon Postgres projects, branches, queries, and migrations through an AI assistant.

What you can do with Neon in VS Code

Choose Neon-native branching and migrations with hosted authentication and project-scoped access.

  • Inspect Neon project databases and table schemas from an IDE.
  • Prepare schema migrations using development branches.

Before you start: Neon in VS Code

  • A Neon account
  • An MCP-compatible client
  • Node.js 18+ for the documented command-based setup

This command registers the hosted service with detected clients; it does not launch a local server. Complete OAuth authorization, or use the documented bearer API-key configuration. Production use is not recommended.

Neon VS Code configuration

  1. Choose VS Code configuration scope

    For Neon MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Neon MCP Server to VS Code

    Use the mcp-server-neon-neondatabase-labs entry below in servers. Keep Neon MCP Server's documented http connection fields and your other VS Code entries.

  3. Check Neon MCP Server in VS Code

    Neon MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "mcp-server-neon-neondatabase-labs": {
      "type": "http",
      "url": "https://mcp.neon.tech/mcp"
    }
  }
}

Neon tools available to VS Code

Neon's stored tool list documents 30 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

__node_version

Look for __node_version among VS Code's agent-mode tools after starting Neon through the MCP controls.

Report the Node.js runtime version used by the MCP server.

list_projects

Look for list_projects among VS Code's agent-mode tools after starting Neon through the MCP controls.

List projects available in the user's Neon account.

create_project

Look for create_project among VS Code's agent-mode tools after starting Neon through the MCP controls.

Create a Neon project for a new database workflow.

delete_project

Look for delete_project among VS Code's agent-mode tools after starting Neon through the MCP controls.

Remove an existing Neon project.

describe_project

Look for describe_project among VS Code's agent-mode tools after starting Neon through the MCP controls.

Inspect the details of a Neon project.

run_sql

Look for run_sql among VS Code's agent-mode tools after starting Neon through the MCP controls.

Execute one SQL statement, with read-only queries enforced in read-only mode.

run_sql_transaction

Look for run_sql_transaction among VS Code's agent-mode tools after starting Neon through the MCP controls.

Execute multiple SQL statements as a database transaction.

describe_table_schema

Look for describe_table_schema among VS Code's agent-mode tools after starting Neon through the MCP controls.

Inspect the structure of a selected database table.

get_database_tables

Look for get_database_tables among VS Code's agent-mode tools after starting Neon through the MCP controls.

create_branch

Look for create_branch among VS Code's agent-mode tools after starting Neon through the MCP controls.

prepare_database_migration

Look for prepare_database_migration among VS Code's agent-mode tools after starting Neon through the MCP controls.

complete_database_migration

Look for complete_database_migration among VS Code's agent-mode tools after starting Neon through the MCP controls.

describe_branch

Look for describe_branch among VS Code's agent-mode tools after starting Neon through the MCP controls.

delete_branch

Look for delete_branch among VS Code's agent-mode tools after starting Neon through the MCP controls.

get_connection_string

Look for get_connection_string among VS Code's agent-mode tools after starting Neon through the MCP controls.

provision_neon_auth

Look for provision_neon_auth among VS Code's agent-mode tools after starting Neon through the MCP controls.

Set up Neon project authentication through the documented Stack Auth integration.

list_shared_projects

Look for list_shared_projects among VS Code's agent-mode tools after starting Neon through the MCP controls.

Find Neon projects that have been shared with the current user.

list_organizations

Look for list_organizations among VS Code's agent-mode tools after starting Neon through the MCP controls.

List organizations available through the connection.

list_branch_computes

Look for list_branch_computes among VS Code's agent-mode tools after starting Neon through the MCP controls.

Inspect compute resources associated with a branch.

compare_database_schema

Look for compare_database_schema among VS Code's agent-mode tools after starting Neon through the MCP controls.

Compare database schemas through the schema tool category.

list_slow_queries

Look for list_slow_queries among VS Code's agent-mode tools after starting Neon through the MCP controls.

Inspect slow-query information for performance investigation.

explain_sql_statement

Look for explain_sql_statement among VS Code's agent-mode tools after starting Neon through the MCP controls.

Inspect how a SQL statement is planned.

search

Look for search among VS Code's agent-mode tools after starting Neon through the MCP controls.

fetch

Look for fetch among VS Code's agent-mode tools after starting Neon through the MCP controls.

list_docs_resources

Look for list_docs_resources among VS Code's agent-mode tools after starting Neon through the MCP controls.

get_doc_resource

Look for get_doc_resource among VS Code's agent-mode tools after starting Neon through the MCP controls.

reset_from_parent

Look for reset_from_parent among VS Code's agent-mode tools after starting Neon through the MCP controls.

provision_neon_data_api

Look for provision_neon_data_api among VS Code's agent-mode tools after starting Neon through the MCP controls.

prepare_query_tuning

Look for prepare_query_tuning among VS Code's agent-mode tools after starting Neon through the MCP controls.

complete_query_tuning

Look for complete_query_tuning among VS Code's agent-mode tools after starting Neon through the MCP controls.

Neon: full stored tool descriptions

Troubleshooting Neon in VS Code

  • The Neon MCP Server entry connects to mcp.neon.tech with type http. Start it through VS Code's MCP controls and review the endpoint before accepting trust prompts.
  • Neon MCP Server: check http connectivity to mcp.neon.tech from VS Code; a stdio command is not a replacement for this endpoint.
  • Transport mismatch: Neon's catalog lists stdio; the displayed VS Code configuration uses http.
  • Known limitation: The README advises against production use.
  • Known limitation: Write-enabled access includes destructive project and branch operations.
  • Known limitation: Organization projects require explicit context when using OAuth.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

Neon MCP Server — details. VS Code guide

Frequently asked questions

For Neon MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's mcp-server-neon-neondatabase-labs example uses http. The Neon MCP Server catalog lists stdio; these instructions follow the stored configuration instead.

VS Code connects Neon MCP Server to mcp.neon.tech using url.

Neon MCP Server's stored list contains 30 tools, including __node_version, list_projects, create_project. Compare those names with VS Code's connected tool list; the stored list is not a live check.

Not with hosted OAuth setup. API-key authentication is also supported for clients or agents that cannot use OAuth.

Yes. The projectId URL parameter scopes operations, and category can further restrict tool groups.