Pike13 MCP connector
The Pike13 connector brings class schedules, appointment slots, bookings, visits and client profiles into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so every booking an agent makes runs as the person who signed in and is logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which appointment slots are open with Maya on Thursday afternoon?
Working in Pike13 with Elaichi
-
List all Pike13 account
-
List all Pike13 account businesses
-
List all Pike13 account people
How to connect Pike13 to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Pike13 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.
Pike13 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.
Pike13 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.
Pike13 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.
Pike13 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 Pike13 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 Pike13 through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pike13 is logged.
-
Front desk
Find an open slot and book it
Ask which appointment times are open with a given instructor this week, then book the client straight into the one they want.
-
Front desk
Move or cancel a booking after a call
When a client phones to reschedule, update the booking to the new time or cancel it, without clicking through the calendar.
-
Operations
Hold a spot while a client decides
Place a short lease on an appointment slot so it is reserved while the client confirms, then extend or release it.
-
Instructors
Log what happened in a class
Add a note to today's class occurrence about who struggled, who progressed and what to cover next time, then edit it later.
-
Membership
Check who can enroll before promising
See whether a client is eligible to enroll in a class occurrence before telling them they have a place, and review their visit history.
-
Franchise
See every location in one place
List the businesses and franchisees on the account, pull client profiles and custom fields, and compare visits across locations without logging into each one.
Try asking
- “Which appointment slots are open with Maya on Thursday afternoon?”
- “Book Jordan Lee into Saturday's 9am yoga class.”
- “Who attended this morning's spin class and who missed it?”
What connecting Pike13 gets you
6 screens from Elaichi, each doing one job for your Pike13 account.
Ask Elaichi to work across your apps.
Which appointment slots are open with Maya on Thursday afternoon?
Book Jordan Lee into Saturday's 9am yoga class.
Who attended this morning's spin class and who missed it?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about today's schedule in plain words.
Open slots, bookings and class visits answered from live Pike13 records.
Copy the endpoint
AI apps
One Pike13 endpoint for every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared key.
Tool catalog
187 Pike13 tools, ready with no code.
Bookings, slots, leases, visits, notes and people, covered without a line of code.
Toolboxes
Every team gets its own Pike13 toolbox.
Front desk books, instructors take notes, owners see every location.
Shared connections
Share Pike13 without sharing a secret.
One person connects, teammates book through it and never see a credential.
Audit log
Know who changed every Pike13 booking.
When, who, what happened and which record, in an append-only log.
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.
Pike13 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch bookings
Pike13
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
Pike13
Queued
Workflows
A schedule starts the work, a person approves.
Bookings are fetched, grouped and drafted into a digest, then posted to Pike13.
Pike13 health
Refreshed 4 minutes ago · every 15 minutes · from the bookings collection
Bookings
1,284 ↓ 12%
People
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Bookings created
Last 14 days
By team
Share of activity
Front desk 34%
Instructors 27%
Membership 21%
Downtown studio 18%
Collections and dashboards
Pike13 numbers computed, not asked for.
Bookings created over 14 days, by team, refreshed on a schedule with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Pike13
All three can connect Pike13 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 Pike13 tools | Allow or restrict single Pike13 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 Pike13 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.
Pike13 tools for your AI agents
187 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pike13, 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 Pike13 to Claude?
Connect Pike13 in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Pike13 connects over OAuth using an application your organization registers inside Pike13, so one person brings a client ID and secret once, and after that everyone else simply signs in with their own Pike13 login. Nobody else ever handles a key.
Does Pike13 work with ChatGPT and Cursor as well as Claude?
Yes. Once Pike13 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 Pike13 once and every client gets it.
What can an AI agent actually do with my Pike13 data?
With Pike13 connected, an agent can find open appointment slots and available times, create, change and cancel bookings, hold a slot with a lease, check who is eligible to enroll in a class, list visits for a class occurrence and write or edit notes on it. It can also look up people, businesses, franchisees and custom fields on the account. Short, concrete asks like "book Sam into Tuesday's 6pm class" work better than long paragraphs.
Does connecting Pike13 give the AI every client record and every location?
No. Every call to Pike13 runs as the person who signed in, so an agent sees only the clients, locations and bookings that person can already see in Pike13. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Pike13 itself allows.
Can I stop an agent from deleting or changing things in Pike13?
Yes. Restrictions in Elaichi work per action on Pike13, so you can allow finding slots and reading visits while restricting cancelling bookings or deleting notes, for a role or for one person. A restricted action still shows up in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Pike13 connection when someone leaves?
Offboarding that person in Elaichi ends their access to Pike13 through every client at once. A Pike13 connection they shared keeps working for everyone else on the team. If you ever want Pike13 gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Pike13 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pike13 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 Pike13?
Yes. Both let Claude, ChatGPT or Cursor use Pike13. 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 Pike13 call.
How is Elaichi different from Composio for Pike13?
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 Pike13: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Pike13 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