# PlanetScale — MCP Server

> Query branches, inspect schema and read performance insights on a serverless MySQL fleet.

**Source:** https://mcpplaygroundonline.com/mcp-servers/planetscale  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

The server covers PlanetScale’s control surface alongside its data. An agent can list organisations, databases and branches, then read the schema of any branch — which matters on a platform where branching is the normal workflow and "what does the schema look like" is always a question about a specific branch. Query insights are readable, so a model can surface the statements with the worst latency or highest row-read counts and reason about which index is missing. Deploy requests, the mechanism by which schema changes reach production, are inspectable too. The combination suits an agent well: ask which queries regressed, read the schema they touch, and get a concrete index proposal with the reasoning attached, rather than a generic suggestion to add an index somewhere.

## Tools exposed

- list databases and branches — walk the org, database and branch hierarchy
- schema — read table and column definitions for a specific branch
- query insights — slowest and most expensive queries with their statistics
- deploy requests — inspect pending and completed schema changes
- run query — execute SQL against a branch you have access to

## Example queries you can run

- "Which queries on the main branch have the worst p99 latency this week?"
- "How does the schema on the add-billing branch differ from main?"
- "Suggest an index for the slowest query, and explain the trade-off on write cost."
- "What deploy requests are open, and what tables do they touch?"

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Index advice needs the schema, the query and the access pattern held together. Sonnet 4.5 reasons about composite column order; smaller models suggest single-column indexes reflexively.
- **Transport:** http
- **Authentication:** Required — A PlanetScale service token or OAuth session. Scope it to the databases the agent should reach — tokens are per-organisation.
- **Hosted endpoint:** https://mcp.pscale.dev/mcp/planetscale
- **Official source:** [PlanetScale documentation](https://planetscale.com/docs)

## Frequently asked questions

### What is the PlanetScale MCP server?

A hosted MCP server for PlanetScale’s serverless MySQL platform. It exposes databases, branches, schemas, query insights and deploy requests as tools, so an agent can explore and reason about your fleet.

### Why does branching matter here?

Because on PlanetScale the schema is always a property of a branch, not of the database. An agent that does not name the branch is answering about an unspecified version of your schema — worth being explicit about in your prompts.

### Can it run destructive SQL?

That depends entirely on the token you give it. Scope the service token to read-only, or to a development branch, and the question resolves itself. Never hand an agent a production-write token for exploratory work.

### How is this different from the Postgres MCP server?

The Postgres server is a generic database connection you point at any instance. This one is platform-aware: it understands branches, deploy requests and PlanetScale’s own query insights, which are exactly the things a generic SQL connection cannot see.

### Is query insights data useful to a model?

It is one of the better fits for an agent, because the raw data is tedious and the pattern-matching is mechanical. Pulling the top twenty statements and correlating them against schema is a job models do well and humans postpone.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/planetscale — free, no install._