Claude PlanetScale connectorWhat Claude can do in your PlanetScale account.
The Claude PlanetScale connector exposes 15 tools: 14 read, 1 write. Claude browses your organisations, databases and branches, reads schemas and Insights, runs SQL and checks invoices. One tool can run write queries, and PlanetScale puts guards around it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your PlanetScale databases
Instead of switching between the PlanetScale console, a SQL client and the Insights tab, you describe what you need and Claude does the legwork: it finds the right branch, reads its schema, runs a query and explains the result. Most of the 15 tools only look. A single one runs write SQL, and that is where your attention belongs.
See how queries perform. planetscale_get_insights returns query performance insights for a database branch, so Claude can lay out in the reply what PlanetScale measured on that branch.
Answer a data question without writing SQL. Claude reads the table layout with planetscale_get_branch_schema, then runs a SELECT through planetscale_execute_read_query, which goes to a replica by default when the branch has one.
Explain the bill. planetscale_get_invoice_line_items returns every line of an invoice, with prorated costs broken down per database branch.
What it will not do on its own: PlanetScale blocks UPDATE or DELETE without a WHERE clause and refuses TRUNCATE, and schema changes make the model ask for human confirmation first. Nothing runs on a schedule either: Claude acts only while it answers. For jobs that must fire by themselves, an automation platform is the better fit; our Integrations hub lists them.
Five words before you connect
Claude's vocabulary for this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- PlanetScale's own sign-in screen, where you grant Claude the access it will use. Given once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before something that changes an account, shown in the conversation at the moment it matters.
- MCP
- The shared standard connectors are built on, the piece that lets an assistant talk to an outside service like PlanetScale.
Connect PlanetScale to Claude in three steps
- 01
Find PlanetScale in Claude
Open Claude's settings, go to Customize then Connectors, and look for PlanetScale in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organisation before members can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to PlanetScale in the window PlanetScale opens itself. If the link breaks later, use Disconnect and connect again.
- 03
Choose the access carefully
PlanetScale's authorization screen is where you decide, per organisation or per database, whether Claude gets no access, read-only access or full access. It belongs to PlanetScale, not to Claude, and it sets what every later query can reach.
The 15 tools, sorted by what they do
PlanetScale gives Claude 15 tools: 14 that read your account, 1 that change something in it.
Fourteen read and one writes, and PlanetScale's documentation describes each. Names stay exactly as Claude shows them.
- 14 read
- 1 write
What Claude reads (14)
14 toolsFourteen tools that look at organisations, databases, performance and billing without altering them.
planetscale_list_organizations
Returns every PlanetScale organisation that the access you granted can reach. Organisations sit at the top of PlanetScale's structure, above databases and branches, and they are also one of the two levels at which you set the connector's scope.
planetscale_list_databases
Lists all the databases inside one organisation. Database names are what the schema, branch, query and Insights tools then work on, and a database is the second level at which PlanetScale lets you grant or refuse access.
planetscale_list_branches
Enumerates every branch of a single database. On PlanetScale, schema, Insights and invoice line items are all tied to a branch, so this list is what the branch-level tools build on.
planetscale_get_organization
Brings back the details PlanetScale holds about one specific organisation, rather than the bare list of names. It only reads that organisation's record, within the scope you granted.
planetscale_get_database
Fetches the details of one specific database inside an organisation. Where the list tool gives names, this one returns what PlanetScale records about a single database.
planetscale_get_branch
Looks up one database branch and reports the details PlanetScale keeps on it. It works on a single branch, as opposed to the listing tool that returns all of them.
planetscale_get_branch_schema
Reads the schema of a database branch, as PlanetScale stores it. Knowing the tables and their columns is what lets a SELECT be written against the right names instead of guessed ones.
planetscale_execute_read_query
Runs a read-only SQL query, limited to SELECT, SHOW, DESCRIBE or EXPLAIN, against a PlanetScale database. It goes to a replica by default and can be sent to the primary instead; on Postgres it returns a warning when row-level security may filter the results.
planetscale_get_insights
Retrieves the query performance insights PlanetScale computes for one database branch. PlanetScale also offers an insights-only server that keeps this kind of data but drops both query tools.
planetscale_list_regions_for_organization
Lists every region available to one organisation. The answer is specific to that organisation, so two organisations may not get the same list. It reads the options and does not move any database.
planetscale_list_cluster_size_skus
Shows all the cluster size SKUs PlanetScale makes available. It is a reference list of sizes, with no effect on your clusters: resizing is not among the 15 tools on the sheet.
planetscale_list_invoices
Pulls every invoice PlanetScale has issued to one organisation. It returns the invoices themselves; the breakdown of a single invoice by branch comes from the line-items tool.
planetscale_get_invoice_line_items
Breaks one invoice into all its line items, with prorated costs per database branch. That per-branch split is what PlanetScale's description singles out for this tool.
planetscale_search_documentation
Searches PlanetScale's documentation, so an answer about the product can rest on the vendor's own pages. It touches the documentation, not your databases.
What Claude can change (1)
1 toolOne tool that runs write SQL. PlanetScale adds its own safeguards; Claude's general approval rule below also applies.
planetscale_execute_write_query
Approval: see the ruleExecutes INSERT, UPDATE, DELETE or DDL statements on a PlanetScale database. PlanetScale refuses UPDATE or DELETE without a WHERE clause, blocks TRUNCATE outright, and has DDL such as CREATE, DROP or ALTER prompt the model to ask for human confirmation.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. Here that matters for one tool, the write query, where PlanetScale also adds its own checks.
On Team and Enterprise, workspace owners decide whether a member may let some actions through without being asked each time. They can also limit what a connector may do across the organisation, for example keep reading and close writing, and nobody overrides that from their own account. Claude works with the rights of the person who connected and with the scope chosen on PlanetScale's screen: no access, read-only or full, per organisation or per database. Official per-tool labels appear only inside a connected account's settings.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. For PlanetScale, as for every other connector, that answer is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before members sign in. For the current state of this one, check its sheet in the official directory. Worth knowing: only PlanetScale documents this connector; no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it replies to you; nothing fires when a query slows down or an invoice arrives.
The directory's verification badge is not a security audit, and Anthropic states on every sheet that it does not choose the tools a publisher exposes or guarantee how they behave. PlanetScale itself urges caution before giving a language model write access to a production database and asks you to review queries before they run. Its documentation also lists more tools than the directory sheet shows; this page covers only the 15 on the sheet.
Need help connecting PlanetScale to Claude?
A person reads every message.