Get started Dashboard
← All integrations
PlanetScale

PlanetScale integration: connect databases and branches to Polylane

Connect PlanetScale databases and branches to Polylane with OAuth or service credentials. Use Query Insights to investigate branch performance changes.

Why Polylane for PlanetScale

Get started for free

How to set up PlanetScale

The guide says inventory can take a few minutes to appear; total authorization time is not measured.

  1. Choose PlanetScale and open Continue to PlanetScale. Authorize the application on PlanetScale.
  2. If more than one organization is reachable, select the organization to connect. Each connection covers one organization.
  3. Alternatively, use the connection API with a service token ID and token from Organization Settings → Service tokens, granting organization/database reads such as read_databases and read_branches.

Permissions and access

The client declares user:read_organizations and user:read_user; organization and database read scopes for identity, databases, branches, backups, comments, deploy requests and members; and branch reads. It also declares organization/database restore_backups and restore_production_branch_backups, plus branch:restore_backups. OAuth scopes are configured on the PlanetScale app, not sent in the local authorize URL, so the consent screen is authoritative. The console has no read-only/full-access switch. A read-scoped service token is the documented alternative when using the API.

Discovery, refresh and the connected view

Databases and branches refresh on a 15-minute schedule. State, plan, region and schema activity appear on the map. Query Insights supplies per-branch metrics for investigations and issue detection. Select the database branch involved instead of treating production and development branches as one service.

Disconnect and revoke access

Disconnect the organization in Polylane. Delete a service token in PlanetScale if you used one; for OAuth, revoke the application authorization on PlanetScale as well.

Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.

In the graph.

Every PlanetScale resource Polylane picks up sits in the graph with its connections, config and history.

Database
Database Branch

Tools for the investigation.

What Polylane can do with PlanetScale while it investigates. Every call is recorded in the transcript.

PlanetScale Polylane MCP
  • planetscaleApi Call any PlanetScale REST API endpoint that lacks a dedicated tool
  • planetscaleGetQueryInsights Get PlanetScale Query Insights for a database branch: top queries, query errors, or latency anomalies

PlanetScale setup and troubleshooting

All guides for PlanetScale

Common questions.

How does Polylane connect to my PlanetScale organization?

Choose PlanetScale and open Continue to PlanetScale. Authorize the application on PlanetScale. If more than one organization is reachable, select the organization to connect. Each connection covers one organization. Alternatively, use the connection API with a service token ID and token from Organization Settings → Service tokens, granting organization/database reads such as read_databases and read_branches.

What PlanetScale resources does Polylane sync?

Databases and branches refresh on a 15-minute schedule. State, plan, region and schema activity appear on the map. Query Insights supplies per-branch metrics for investigations and issue detection. Select the database branch involved instead of treating production and development branches as one service.

Connect it once. Then get back to shipping.