PlanetScale MCP connector
Connect PlanetScale to Elaichi and Claude, ChatGPT, Cursor, and the Elaichi Agent can list your databases and branches, read schemas, run queries, review insights and error patterns, and check invoices, each person inside their own PlanetScale access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
25 tools
How to connect
How to connect PlanetScale to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect PlanetScale once
-
Open Connections, choose Add connection, and pick PlanetScale.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in PlanetScale. PlanetScale's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
PlanetScale MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
PlanetScale MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
PlanetScale MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect PlanetScale to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with PlanetScale through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Check a branch schema before merging
Ask for the schema on a PlanetScale branch, compare it with the main branch, and pull the open schema recommendations before a deploy request goes out.
-
Data
Answer a question straight from the database
Ask how many orders shipped last week or which accounts went quiet, and get the answer from a read query against the PlanetScale database you already have access to.
-
Engineering
Find out why queries keep failing
Pull the query error patterns, see the individual executions behind them, and read the Postgres logs for the same window without leaving the conversation.
-
Platform
Size the next cluster with real numbers
Review query insights for a database, then list the regions and cluster sizes available to the organization before deciding what to change.
-
Finance
Reconcile the PlanetScale invoice
List last month's invoices, break each one down into line items by database, and confirm the payment method on file is still the right card.
-
Support
Look up a customer record on a ticket
Run a read query for the customer's account while the ticket is open, with access limited to the databases the support agent can already see in PlanetScale.
Try asking
- “Show me the schema for the main branch of the orders database”
- “Which queries failed most often this week and why?”
- “Pull last month's PlanetScale invoice line items by database”
Native MCP
Why connect PlanetScale's MCP server through Elaichi
PlanetScale builds and runs this MCP server. Elaichi sits in front of it, so PlanetScale's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to PlanetScale's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT and Cursor reach PlanetScale's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds PlanetScale's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own PlanetScale sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches PlanetScale's server. By default, a tool PlanetScale does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to PlanetScale
PlanetScale builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the PlanetScale team.
Compare
Elaichi vs Zapier MCP vs Composio for PlanetScale
All three can connect PlanetScale to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over PlanetScale tools | Allow or restrict single PlanetScale tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per PlanetScale call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
PlanetScale tools for your AI agents
25 tools are ready to call through Elaichi's MCP endpoint the moment you connect PlanetScale, governed by the same roles, restrictions, and audit log as everything else in Elaichi. PlanetScale builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting PlanetScale gets you
6 screens from the product, each doing one job for your PlanetScale account.
The agent
Ask PlanetScale a question, get the answer.
Three starter prompts pull live databases, branches and query insights into plain-language answers.
- databases
- branches
- organizations
- invoices
Ask Elaichi to work across your apps.
Show me the schema for the main branch of the orders database
Which queries failed most often this week and why?
Pull last month's PlanetScale invoice line items by database
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches PlanetScale from any client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
25 PlanetScale tools, ready without any code.
Databases, branches, schemas, queries, insights, invoices and logs, cataloged with every resource and method.
- PlanetScale list organizations
- PlanetScale list databases
- PlanetScale list branches
- PlanetScale get organization
ElaichiToolsToolboxes
Every team gets its own PlanetScale toolbox.
Engineering, Data and Finance each see a toolbox scoped to the work they do.
- Engineering
- Data
- Platform
- Finance
ElaichiToolboxesShared connections
Teammates query PlanetScale without ever seeing a credential.
One person connects an account, shares it with teams, and the table shows who has it.
- Platform
- Data
- Finance
- Support
ElaichiConnectionsAudit log
Every PlanetScale query is logged with a name.
When, who, what happened, type and resource, appended for every call and never edited.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts PlanetScale work, a person approves.
Query error patterns are fetched, grouped, drafted into a digest, approved, then written back to PlanetScale.
PlanetScale digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch databases
PlanetScale
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
PlanetScale
Queued
Collections and dashboards
PlanetScale health numbers arrive without anyone asking.
Four metrics, 14 days of branches created and a team breakdown, computed with no model.
PlanetScale health
Refreshed 4 minutes ago · every 15 minutes · from the databases collection
Databases
1,284 ↓ 12%
Branches
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Databases created
Last 14 days
By team
Share of activity
Platform 34%
Data 27%
Finance 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect PlanetScale to Claude?
Connect PlanetScale in Elaichi first: you sign in to PlanetScale over OAuth and authorize access, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi, and PlanetScale is available in the conversation from then on.
Does PlanetScale work with ChatGPT and Cursor as well as Claude?
Yes. Once PlanetScale is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect PlanetScale once and every client picks it up.
What can an AI agent actually do with my PlanetScale data?
It can list your organizations, databases and branches, read a branch schema, run read and write queries, and pull query insights, error patterns and Postgres logs. It can also list invoices and their line items, check the payment method, review schema recommendations, and search PlanetScale documentation. Short, concrete asks such as "show the schema on the staging branch" work better than long sentences.
Does connecting PlanetScale give the AI access to every database in my organization?
No. Every call runs as the person who signed in to PlanetScale, so the agent sees only the organizations, databases and branches that person can already open. Elaichi can narrow that further, for example to read queries only, but it can never grant more than PlanetScale itself allows.
Can I stop an agent from deleting or changing things in PlanetScale?
Yes. Restrictions in Elaichi apply per action, so you can allow read queries against PlanetScale while blocking write queries and payment method changes. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a PlanetScale connection when someone leaves?
Offboarding a person in Elaichi ends their access to PlanetScale through every client at once. If they had shared a PlanetScale connection with a team, it keeps working for everyone else. Disconnecting PlanetScale once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the PlanetScale MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. PlanetScale is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for PlanetScale?
Yes. Both let Claude, ChatGPT or Cursor use PlanetScale. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every PlanetScale call.
How is Elaichi different from Composio for PlanetScale?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to PlanetScale: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put PlanetScale in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.