Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | PlanetScale MCPShortlist candidate | Google MCP Toolbox for DatabasesMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP PlanetScale · Publisher source ↗ | First-party MCP Google · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 24, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 16,485 GitHub stars · checked 2026-09-24T04:14:16.258000Z |
| Shared repository stars | 5 Shared repository stars (not MCP-specific) · checked 2026-10-20 | Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | The hosted PlanetScale MCP authenticates with OAuth. | Authentication depends on the database source and can include database username/password, Google Cloud IAM, or other source-specific mechanisms. Use a dedicated read-only identity and secret manager or protected environment variables. |
| Cost | PlanetScale is a paid database service; current pricing starts with paid clusters and also includes charges for items such as routers, backup storage, and public egress. | The Apache-licensed Toolbox and npm server have no documented MCP usage fee. Database services, Google Cloud resources, network transfer, observability backends, hosting, and the AI client may incur normal charges. |
| Permissions | PlanetScale documents configurable access including read-only or full-access permissions for production and development database branches. | Effective permissions come from each configured database identity and the enabled prebuilt or custom tools. Generic prebuilt sets can include schema discovery and execute_sql; custom tools can constrain statements, parameters, and accessible sources. |
| Data handling | PlanetScale states that short-lived database credentials are created on demand for each query and deleted immediately after execution. Queries include source SQL comments for traceability. | The Toolbox process connects directly to configured databases and returns selected schemas, rows, query results, and errors to the MCP client. Credentials may be supplied through environment variables or configuration; integrated cloud authentication and OpenTelemetry are available. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can execute database queries and, with sufficient permission, make consequential schema/branch changes. Database mutations can affect production data and service cost. | Generic SQL tools can expose or mutate large amounts of data and retrieved database text can carry prompt-injection content. Prefer a non-production replica, read-only credentials, allow-listed custom parameterized tools, query limits, audit logs, and no secrets in config. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| Candidate evidence | 2026-10-19 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →