# 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.

Source: https://elaichi.ai/connectors/arketa/

## Facts

| | |
| --- | --- |
| Application | Arketa |
| Category | CRM |
| AI tools | 12 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Arketa is connected

- 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?

## Connect Arketa in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Arketa.
2. Optionally set Share with, then press Connect.
3. Paste an Arketa API key. One person generates a token in Arketa and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Arketa tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Arketa MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Arketa MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Arketa tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Arketa through Elaichi

### Book a client into a class

Front desk. 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.

### Check people in as they arrive

Front desk. 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.

### See what is on across every room

Studio managers. 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.

### Review what sold this week

Owners. 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.

### Find out who is referring new clients

Marketing. 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.

### Move a reservation when a class changes

Operations. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Arketa connection?

Yes. One person connects Arketa in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every reservation booked or check-in made through Arketa is logged under their own name.

### 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.

## All 12 Arketa tools

Every tool below is callable through https://api.elaichi.ai/mcp once Arketa is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Arketa class by ID** (Get). Get single class. Retrieve details for a specific class. Required: id.
- **List all Arketa classes** (List). List partner classes. Retrieve a paginated list of partner classes with optional filtering. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **Get single Arketa client by ID** (Get). Get single client. Retrieve details for a specific client. Required: id.
- **List all Arketa clients** (List). List partner clients. Retrieve a paginated list of partner clients with optional filtering. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **List all Arketa locations** (List). List partner locations. Retrieve a paginated list of partner locations with optional filtering. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **List all Arketa purchases** (List). List partner purchases. Retrieve a paginated list of partner purchases with optional filtering. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **List all Arketa referrals** (List). List partner referrals. Retrieve a paginated list of partner referrals with optional filtering. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **Create a Arketa reservation check in** (Create). Check in reservation. Mark a reservation as checked in. Required: class_id, reservation_id.
- **Create a Arketa reservation** (Create). Create reservation. Create a reservation for a class with either an existing client or new client. Required: class_id. Body: clientId and purchaseId to book an existing client, or firstName, lastName and email (phone and purchaseId optional) to book a new client.
- **List all Arketa reservations** (List). List class reservations. Retrieve reservations for a specific class. Required: class_id. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
- **Update a Arketa reservation by ID** (Update). Cancel reservation. Cancel an existing reservation with optional refund. Required: id, class_id. This call only cancels: set isLateCancel for a late cancellation and issueRefund to refund the client.
- **List all Arketa rooms** (List). List location rooms. Retrieve a paginated list of rooms for a specific location. Required: location_id. The connector pages through all results (Arketa's start_after cursor; limit sets the page size).
