MCP For Claude Marketplace
PlanetScale

PlanetScale MCP Connector for Claude

A+

Provision, branch, and manage serverless MySQL databases dynamically via AI.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner
More Details Connect to Claude

Empower your AI agents to manage your PlanetScale serverless infrastructure seamlessly. Leverage the power of Vitess-backed MySQL without leaving your IDE. Ask your AI to branch a production database for testing, list regions, or drop obsolete schema forks instantly.

What you can do

  • Database Provisioning — Instantly list (list_databases), inspect, create (create_database), or destroy serverless MySQL clusters running across global regions.
  • Branch Management — Harness PlanetScale's Git-like schema workflows. Direct your LLM to spawn a temporary shadow-test branch cloned from main (create_branch), allowing consequence-free migrations before orchestrating Deploy Requests.
  • Infrastructure Exploration — Discover strict organizational IDs (list_organizations) and query available physical cloud provider edges (list_regions) to optimize latency targets.

How it works

  1. Ensure your AI environment has this connector subscribed
  2. Provide an active PlanetScale Service Token
  3. Manage fleets of serverless data clusters via natural language inside Cursor or Claude

Who is this for?

  • DevOps Engineers — automate the destruction of stale staging branches (delete_branch) via simple LLM terminal chat commands.
  • Full-stack Developers — spin up ephemeral database branches for isolated feature development without touching the web console.
  • Platform Architects — audit distribution footprints, node metadata, and connection strings across multiple organizational environments automatically.
mysqlserverlessdatabase-branchingvitessschema-managementdevops

10 tools expose this connector's capabilities to your AI agent.

create_branch

Does *not* duplicate data (creates an empty schema clone of the parent) for secure CI testing uncoupled entirely from `main` load balancing layers. Fork a PlanetScale schema mapping to a new isolated Branch

create_database

Creates empty environments ready to execute explicit DDL definitions via non-blocking Deploy Requests. Provision a radically scalable Serverless Database instance

delete_branch

Utilized constantly within CI/CD pipelines following a successful Deploy Request morphing `main` schema structure directly. Purge an obsolete Git-like Schema testing ground

delete_database

Dropping the database effectively wipes terabytes of records scattered globally. Fails fully if unacknowledged connection logic binds it. Destroy a PlanetScale MySQL construct irreversibly

get_branch

Returns access hostnames for code integration. Deconstruct the layout of a single explicit Database Branch

get_database

Analyze core configuration of a specific MySQL cluster logic

list_branches

Essential for migrating schemas without locking production reads/writes. List Development Database Branches mirroring Prod architectures

list_databases

Retrieves explicitly mapping IDs orchestrating distributed Vitess backend shards. List high-availability PlanetScale MySQL DB distributions

list_organizations

Used solely to resolve the foundational string key prerequisite for all subsequent MySQL endpoint management. List root PlanetScale organizational identifiers

list_regions

Critical reference required during new Database/Branch physical provisioning routines. Locate physical edge availability zones supported by Vitess

See how to talk to your AI agent using PlanetScale.

List all physical cloud regions currently exposed by the PlanetScale integration.

I executed `list_regions` successfully against your organization map. I found 15 edge locations. The primary North-American targets are `us-east` (AWS N. Virginia) and `us-west-2` (AWS Oregon). There are also `eu-west` endpoints available for immediate Database generation. Would you like me to create an instance there?

We're starting a new feature. Fork testing branch from the main database 'store-backend'.

Executed `create_branch`. Branch `feature-test-1y82` has been successfully spun up under `store-backend`. It copied the exact static schema logic from `main` without migrating standard rows, resulting in an empty, compliant Vitess environment ready for raw testing strings. What's the new DDL injection you're planning?

Drop the specific 'staging-01' branch inside the 'web-portal' database.

Command `delete_branch` deployed explicitly specifying target DB 'web-portal' aiming for branch 'staging-01'. The environment hook has been severed internally and queued for complete data physical destruction. Staging-01 operates out of existence as of now.

Yes. The integration provides `delete_branch` and `delete_database`. They map directly to infrastructure teardowns. You should scope the Service Token carefully inside the PlanetScale dashboard to avoid catastrophic misinterpretations if your explicit intent is just testing. Deletions via `delete_database` are absolute and irretrievable.

Related Connectors

RA

Railz MCP

12 tools Official

Financial data integration platform — connect accounting, banking, and commerce data via AI.

A+ View details →
CR

crowd.dev (LFX CDP) MCP

10 tools Official

Equip your AI agent to manage community members, activities, and organizations directly via the crowd.dev (LFX) API.

A+ View details →
LA

Langfuse (LLM Tracing & Evals) MCP

10 tools Official

Monitor LLM apps via Langfuse — track traces, manage prompt templates, and audit evaluation scores.

A+ View details →
PC

Pipedrive CRM (Full) MCP

11 tools Official

Manage deals, contacts, organizations, activities, notes, and pipelines — complete Pipedrive CRM access through natural conversation.

A+ View details →