Developer · Remote MCP server
PlanetScale
Connect to PlanetScale databases, branches, schema, query insights, and execute SQL.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.planetscale/mcp-server- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-15
- Updated
- 2026-04-15
- Publisher
- planetscale (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/planetscale) · how
- Website
- planetscale.com/docs/connect/mcp
- Repository
- github.com/planetscale/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.pscale.dev/mcp/planetscale | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect PlanetScale
PlanetScale is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.pscale.dev/mcp/planetscale, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, planetscale.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| pkgxrayPre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence. | Local · stdio |
| Plaid MCPQuery Plaid sandbox: institutions, categories, sandbox public tokens. Sandbox only. | Local · stdio |
| PlainQuery | MCP DB AgentQuery PostgreSQL databases in plain English - LLM-generated, safety-validated SQL. | Remote · HTTPLive check: ✗ no handshake |
| Plainsight MCPSearch the Plainsight playbook and review code against proven best practices. | Remote · HTTPLive check: ✗ no handshake |
| PlanExeMCP server for generating rough-draft project plans from natural-language prompts. | Remote · HTTPLive check: ✓ handshake |
| Plate Website SourceRead-only catalog of free Plate website source projects a coding agent can adapt. | Remote · HTTPLive check: ✓ handshake |
| Plateau Creative MCPPLATEAU 3D city data as scene-editing and glTF export tools for creative LLM agents. | Local · stdio |
| PlatformBackend for AI-built apps: database, auth, files, email, AI, payments, deploy, realtime. 170+ tools. | Remote · HTTPLive check: sign-in required |