Arketa MCP connector
The Arketa connector brings your studio's classes, clients, reservations, purchases, referrals, locations and rooms to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can book, check in and look things up by asking.
- Connects with an API key
- Free 14-day trial
- No credit card
Which classes still have spots at the downtown location this evening?
Working in Arketa with Elaichi
-
Get single Arketa class by ID
-
List all Arketa classes
-
Get single Arketa client by ID
How to connect Arketa to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Arketa 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.
Arketa 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.
Arketa 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.
Arketa 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.
Arketa 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 Arketa 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 Arketa through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Arketa is logged.
-
Front desk
Book a client into a class
Ask for the client by name, find the right class at the right location, and create the reservation without clicking through the Arketa schedule. A walk-in gets a spot while they are still standing at the counter.
-
Front desk
Check people in as they arrive
Pull up this evening's reservations and check clients in one by one as they come through the door. The class roster in Arketa updates as you go.
-
Studio managers
See what is on across every room
Ask which classes are running today, in which rooms and at which locations, and spot the gaps or the double bookings before anyone turns up.
-
Owners
Review what sold this week
List purchases from the last seven days and ask which packages, memberships and drop-ins moved. You get the answer in a sentence instead of an export.
-
Marketing
Find out who is referring new clients
List referrals in Arketa and ask which existing clients brought in the most newcomers this month, so you know who to thank and who to reward.
-
Operations
Move a reservation when a class changes
When an instructor cancels or a room swaps, ask to update the affected reservations in Arketa and tell the client what changed, in one go.
Try asking
- “Which classes still have spots at the downtown location this evening?”
- “Book Maya Chen into tomorrow's 7am reformer class.”
- “Who referred the clients who joined this month?”
What connecting Arketa gets you
6 screens from Elaichi, each doing one job for your Arketa account.
Ask Elaichi to work across your apps.
Which classes still have spots at the downtown location this evening?
Book Maya Chen into tomorrow's 7am reformer class.
Who referred the clients who joined this month?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about today's classes in plain language.
Type a question and the Elaichi Agent answers from live Arketa classes, clients and reservations.
Copy the endpoint
AI apps
Arketa works from Claude, ChatGPT and Cursor.
One governed endpoint, every client signs in over OAuth, no SDK and no shared API key.
Tool catalog
12 Arketa tools, ready without writing code.
Classes, clients, locations, purchases, referrals, reservations and rooms, cataloged the moment you connect.
Toolboxes
Every team gets its own Arketa toolbox.
Front desk books and checks in, owners review purchases, each from a toolbox scoped to them.
Shared connections
Share one Arketa connection, never a credential.
The connections table shows who connected Arketa and which teams and members work through it.
Audit log
Every Arketa reservation change has a name.
The audit log records when, who, what happened, the type and the Arketa resource touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Arketa digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch classes
Arketa
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
Arketa
Queued
Workflows
Schedules run Arketa work end to end.
Reservations are fetched, grouped and drafted into a digest, a person approves, Arketa gets it back.
Arketa health
Refreshed 4 minutes ago · every 15 minutes · from the classes collection
Classes
1,284 ↓ 12%
Clients
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Classes created
Last 14 days
By team
Share of activity
Front desk 34%
Downtown studio 27%
Westside studio 21%
Marketing 18%
Collections and dashboards
Arketa health numbers, computed with no model.
Four metrics, 14 days of reservations created and a split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Arketa
All three can connect Arketa 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 Arketa tools | Allow or restrict single Arketa 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 Arketa 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.
Arketa tools for your AI agents
12 tools are ready to call through Elaichi's MCP endpoint the moment you connect Arketa, 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 Arketa to Claude?
Two steps. First connect Arketa in Elaichi, where the sign-in step is pasting the API key from your Arketa account, 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 the endpoint https://api.elaichi.ai/mcp. Claude signs you in with your own Elaichi login and Arketa is ready to use.
Does Arketa work with ChatGPT and Cursor as well as Claude?
Yes. Once Arketa 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 Arketa once and every client picks it up.
What can an AI agent actually do with my Arketa data?
It can look up a client or a class, list the classes, rooms and locations on your schedule, and show purchases and referrals. It can also create a reservation, change an existing one, and check a client in when they arrive. Short, concrete asks such as "book Maya into tomorrow's 7am class" work better in Arketa than long paragraphs.
Does connecting Arketa give the AI access to all of my studio's clients and purchases?
No. Every call into Arketa runs inside the access of the person who signed in, so an agent can only see and change what that person could see and change in Arketa themselves. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Arketa?
Yes. Restrictions in Elaichi are set per action, on a role or on one person, so you can let the front desk check clients in but stop anyone from creating or changing reservations in Arketa. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Arketa connection when someone leaves?
Offboarding that person in Elaichi ends their access to Arketa at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Arketa connection keeps working for everyone else on the team. If you want to remove Arketa entirely, disconnecting it once in Elaichi removes it from every client.
Does the Arketa MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Arketa 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 Arketa?
Yes. Both let Claude, ChatGPT or Cursor use Arketa. 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 Arketa call.
How is Elaichi different from Composio for Arketa?
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 Arketa: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Arketa 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