PlanetScale documents a hosted Model Context Protocol server at planetscale.com/docs/connect/mcp, reachable at `https://mcp.pscale.dev/mcp/planetscale` with OAuth authentication for organizations, databases, branches, schemas, and Insights data. An insights-only endpoint at `https://mcp.pscale.dev/mcp/planetscale-insights-only` omits read/write query tools. Tools documented include organization/database/branch listing, schema inspection, `planetscale_get_insights`, documentation search, and—when scopes allow—`planetscale_execute_read_query` and `planetscale_execute_write_query` with replica routing, ephemeral credentials, and destructive-query safeguards per the January 2026 changelog. PlanetScale notes the older local CLI MCP path is deprecated in favor of the hosted HTTP server for Cursor, Claude Code, and other MCP clients.
Use cases
- Ask Cursor to pull slow-query Insights for a production branch before tuning indexes
- Inspect branch schemas and deploy-request context without pasting credentials into chat
- Use insights-only OAuth scopes when analysts need metrics but not live SQL execution
- Debug ORM regressions by combining schema tools with natural-language query plans
- Grant read-only database OAuth to contractors while blocking write-query tools
Key features
- Cursor
- Claude Desktop
- Claude Code
- VS Code
- Codex
Frequently Asked Questions
- Is this the deprecated local CLI MCP?
- No—PlanetScale docs direct users to the hosted OAuth server; the CLI MCP path is deprecated.
- Can I avoid write-query tools entirely?
- Yes—use the insights-only URL documented at planetscale.com/docs/connect/mcp.
- What safeguards apply to SQL execution?
- Docs cite replica routing, ephemeral credentials, destructive-query protection, and human confirmation for schema changes.
Related
Related
3 Indexed items
Convex MCP Server
Convex documents a Model Context Protocol server shipped in the Convex CLI at docs.convex.dev/ai/convex-mcp-server, started locally with `npx -y convex@latest mcp start` over stdio after linking a project via `npx convex dev`. Tools include `status` (deployment selector), `tables` (declared and inferred schemas), `data` (paginated documents), `runOneoffQuery` (sandboxed read-only JS), `functionSpec`, `run` (invoke deployed functions), `logs`, `insights` (72-hour OCC and resource-limit health), and `envList`/`envGet`/`envSet`/`envRemove`. Flags such as `--prod`, `--preview-name`, `--deployment-name`, and `--disable-tools` restrict scope; production writes require `--dangerously-enable-production-deployments` per changelog defaults.
Upstash MCP Server
Upstash documents an official Model Context Protocol server at upstash.com/docs/agent-resources/mcp implemented in the `upstash/mcp-server` repository and npm package `@upstash/mcp-server`. Started with `npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY`, it exposes tools for serverless Redis, QStash, Workflow runs, and Upstash Box so agents can manage and debug account resources from Cursor, Claude Code, VS Code, Codex, and other MCP clients. Read-only API keys automatically disable mutating tools per docs; optional `--transport http`, `--disable-telemetry`, and Upstash Box API key flags are documented for advanced setups.
Turso MCP Server
Turso documents a built-in Model Context Protocol server in the Turso CLI (`tursodb`) at docs.turso.tech/cli/mcp-server, started with `tursodb /path/to/database.db --mcp` over stdio JSON-RPC. Tools include `open_database`, `current_database`, `list_tables`, `describe_table`, `execute_query` (SELECT-only), `insert_data`, `update_data`, `delete_data`, and `schema_change` (CREATE/ALTER/DROP) per the Mintlify MCP reference. Turso's launch blog at turso.tech/blog/introducing-the-turso-database-mcp-server shows Claude Desktop and Claude Code configuration via `claude mcp add` with the same `--mcp` flag—no separate npm package required for local embedded databases.