Caspio MCP connector
The Caspio connector brings your Caspio tables, records, fields, views and files into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, so your team can look up, add and update records by asking, inside their own Caspio access.
- App credentials
- Free 14-day trial
- No credit card
Claude
Elaichi connected
List the tables in Caspio and their record counts.
Working in Caspio with Elaichi
-
List all Caspio tables
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Caspio to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Caspio 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.
Caspio MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Caspio 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. The plugin directory lives at chatgpt.com/plugins.
Caspio 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.
Caspio MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Caspio 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.
What teams do with Caspio through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Caspio is logged.
-
Operations
Update a tracking record without opening the app
Tell the agent which project, asset or order changed and it updates the matching Caspio record, so the tracker stays current while you keep working.
-
Support
Find a customer record in seconds
Ask for a customer by name, email or ticket number and get the Caspio record back in plain language, with the fields you care about pulled out.
-
Sales
Log a new lead straight into Caspio
After a call, describe the new contact and the agent creates the record in your leads table, with the right fields filled in.
-
HR
Check onboarding status across new hires
Ask which new hires still have open onboarding steps and the agent reads the Caspio records and summarizes where each person stands.
-
Field service
Attach a photo or document to a job
Replace or refresh the attachment on a Caspio job record from the field, and confirm the file details are correct before you move on.
-
App builders
Add a field to a table on request
When a team asks for a new column, describe it and the agent creates or adjusts the field in the Caspio table, then confirms the structure back to you.
Try asking
- “List the tables in Caspio and their record counts.”
- “Add a status field to the Applications table.”
- “Show records created in Caspio this week by table.”
What connecting Caspio gets you
6 screens from Elaichi, each doing one job for your Caspio account.
Ask Elaichi to work across your apps.
List the tables in Caspio and their record counts.
Add a status field to the Applications table.
Show records created in Caspio this week by table.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask in English, answer from Caspio tables.
Starter prompts read live Caspio records and fields, no query builder needed.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Caspio.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
70 Caspio tools ready on connect.
Tables, fields, records and password fields covered without writing custom code.
ElaichiToolboxesToolboxes
Every team gets its own Caspio toolbox.
Toolboxes scope which Caspio capabilities each team sees inside the endpoint.
ElaichiConnectionsShared connections
Share Caspio access, never the credential.
Connections show who connected each Caspio account and which teams use it.
ElaichiAudit logAudit log
Every Caspio call is on the record.
When, who, what happened, type and resource for each table and record change.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Caspio digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tables
Caspio
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 Jake Morgan
Approve Deny -
Post the digest
Caspio
Queued
Automations
A schedule fires, Caspio records move.
Fetch, group, draft a digest, approve it, then post back to Caspio.
Caspio health
Refreshed 4 minutes ago · every 15 minutes · from the tables collection
Tables
1,284 ↓ 12%
Fields
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tables created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Operations 21%
Support Desk 18%
Collections and dashboards
Caspio health, counted not summarized.
Four metrics, fourteen days of records created, and a per team breakdown.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Caspio
All three can connect Caspio 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 Caspio tools | Allow or restrict single Caspio 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 Caspio 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 | Free for one person; $15 per user per month on Gold. | 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.
Caspio tools for your AI agents
70 tools are ready to call through Elaichi's MCP endpoint the moment you connect Caspio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Caspio to Claude?
Connect Caspio in Elaichi first: Caspio signs in with app credentials, so you enter the credentials from your Caspio account once and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and your Caspio tables, records and views are available in the conversation.
Does Caspio work with ChatGPT and Cursor as well as Claude?
Yes. Once Caspio is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Caspio once and every client sees it.
What can an AI agent actually do with my Caspio data?
An agent connected to Caspio can list your tables and views, look up records, add new ones, update or remove existing ones, and change the fields a table is built from. It can also read and refresh the files and attachments on your records and browse your file folders. Because Caspio has a lot it can do, short concrete asks such as "find the order record for Acme" work better than long paragraphs.
Does connecting Caspio give the AI access to all my tables?
No. The agent works with whatever the Caspio credentials you connected can already reach, and nothing beyond that. Elaichi can narrow that further, for example to reading records only or to a particular set of actions, but it can never widen access beyond what Caspio itself allows.
Can I stop an agent from deleting or changing things in Caspio?
Yes. Restrictions in Elaichi work per action, so you can allow reading Caspio records while restricting deletes, field changes or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Caspio connection when someone leaves?
When you offboard a person in Elaichi, their access to Caspio through every client ends at once. A shared Caspio connection keeps working for everyone else on the team. If you want to remove Caspio entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Caspio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Caspio 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, Microsoft Copilot, 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 Caspio?
Yes. Both let Claude, ChatGPT or Cursor use Caspio. 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 Caspio call.
How is Elaichi different from Composio for Caspio?
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 Caspio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Caspio in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot