PlanetScale MCP Server

The PlanetScale MCP server is an officially hosted remote MCP server that gives MCP-compatible clients (Claude, Cursor, VS Code, Notion, OpenCode, Gemini CLI, and others) direct access to PlanetScale organizations, databases, branches, schemas, and Insights data. Authentication is handled via OAuth, with configurable scopes that let you grant read-only or full access at the organization, database, branch, or feature level. Queries are executed over HTTP using ephemeral credentials that are created on demand and destroyed immediately after execution.

The server exposes 16 tools covering discovery (list organizations, databases, branches, regions, cluster sizes), schema inspection, read and write query execution, query performance Insights, schema recommendations (including index suggestions and primary key exhaustion warnings), billing and invoice data, and documentation search. Read queries are automatically routed to replicas when available, and all queries are tagged with a source=planetscale-mcp comment so they can be tracked in Insights.

Built-in safeguards block UPDATE or DELETE statements without a WHERE clause, block TRUNCATE, and require the LLM to request human confirmation for schema-altering DDL. An Insights-only variant of the server is available at https://mcp.pscale.dev/mcp/planetscale-insights-only for teams who want analysis and recommendations without query execution. A partial source repository for the tool implementations is published at github.com/planetscale/mcp-server, while the full tool set is generated from the PlanetScale API OpenAPI spec on the hosted server.

Tools

The PlanetScale MCP server is hosted by PlanetScale. There is nothing to install: point your MCP client at the server URL and authenticate via OAuth.

Prerequisites

• A PlanetScale account with at least one organization and database
• An MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Notion, OpenCode, Codex CLI, Amp CLI, or Gemini CLI)

Server URLs

• Full server: https://mcp.pscale.dev/mcp/planetscale
• Insights-only (no query execution): https://mcp.pscale.dev/mcp/planetscale-insights-only

Config JSON (Cursor, Claude Code, VS Code, generic clients)

{
  "mcpServers": {
    "planetscale": {
      "url": "https://mcp.pscale.dev/mcp/planetscale"
    }
  }
}

Cursor

1. Open the command palette and run "Cursor Settings".
2. Go to Tools & MCP and click "New MCP Server".
3. Paste the JSON above and save.
4. When prompted, authorize Cursor against your PlanetScale account.

Claude Desktop

1. Open Settings, Connectors.
2. Click Browse connectors, search for "PlanetScale", click the "+" button.
3. Sign in to PlanetScale and approve the requested scopes.

Alternatively add it as a custom connector with URL https://mcp.pscale.dev/mcp/planetscale.

Scopes

During OAuth approval you choose which organizations, databases, and branches the server can access, and whether each is read-only or full access. You can re-authenticate later to change scopes.

• Ask an agent to inspect a branch schema and propose missing indexes using planetscale_list_schema_recommendations and planetscale_get_branch_schema.
• Run natural-language data analysis against a production replica via planetscale_execute_read_query, with automatic replica routing keeping load off primaries.
• Diagnose slow queries by pulling Insights data with planetscale_get_insights and correlating against the live schema.
• Audit billing usage by listing invoices and pulling prorated line items per branch for cost attribution.
• Search PlanetScale docs in-line during agent workflows with planetscale_search_documentation instead of context-switching to a browser.

• "List my PlanetScale organizations, then show all databases in the acme org."
• "Get the schema for the main branch of acme-prod and suggest any missing indexes."
• "Show me the top 10 slowest queries from Insights on the main branch over the last 24 hours."
• "Run a read query that counts orders per status from the main branch."
• "Pull the latest invoice for the acme org and break it down by branch."

• Officially built and hosted by PlanetScale, no self-hosting or credential management required.
• Strong safety model: ephemeral per-query credentials, replica routing for reads, blocks on unfiltered UPDATE/DELETE and TRUNCATE, and human-in-the-loop for DDL.
• Broad surface area, 16 tools spanning data, schema, Insights, infrastructure, billing, and docs search.
• OAuth scopes allow fine-grained, per-branch read-only or full-access permissions.

• Giving an LLM write access to a production database is inherently risky; PlanetScale explicitly recommends caution even with the built-in safeguards.
• Requires a PlanetScale account and is tied exclusively to PlanetScale-hosted databases.
• Postgres users must pass the postgres_database_name parameter to target a non-default database, which can trip up agents that do not know to set it.

• Neon MCP server, an official hosted MCP server for Neon Postgres with similar branching and query capabilities.
• Supabase MCP server, official server for managing Supabase Postgres projects and running SQL.
• Generic MySQL or Postgres MCP servers (e.g. @modelcontextprotocol/server-postgres) for self-hosted databases without PlanetScale-specific features.