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

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

## Facts

| | |
| --- | --- |
| Application | Pike13 |
| Category | Scheduling |
| AI tools | 187 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| 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 Pike13 is connected

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

## Connect Pike13 in Elaichi

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

1. Open Connections, choose Add connection, and pick Pike13.
2. Optionally set Share with, then press Connect.
3. Supply your own Pike13 app, then approve. Pike13 needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

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

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

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

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

## Pike13 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 Pike13 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 Pike13 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 Pike13 through Elaichi

### Find an open slot and book it

Front desk. Ask which appointment times are open with a given instructor this week, then book the client straight into the one they want.

### Move or cancel a booking after a call

Front desk. When a client phones to reschedule, update the booking to the new time or cancel it, without clicking through the calendar.

### Hold a spot while a client decides

Operations. Place a short lease on an appointment slot so it is reserved while the client confirms, then extend or release it.

### Log what happened in a class

Instructors. Add a note to today's class occurrence about who struggled, who progressed and what to cover next time, then edit it later.

### Check who can enroll before promising

Membership. See whether a client is eligible to enroll in a class occurrence before telling them they have a place, and review their visit history.

### See every location in one place

Franchise. List the businesses and franchisees on the account, pull client profiles and custom fields, and compare visits across locations without logging into each one.

## 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. Endpoint: 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](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 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 my team share one Pike13 connection?

Yes. One person connects Pike13 and shares the connection with a team, and nobody else sees the client ID, secret or any other credential. Each teammate still signs in to Elaichi as themselves, so every booking or note they make through Pike13 is logged under their own name.

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

## All 187 Pike13 tools

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

- **List all Pike13 account** (List). Account: Returns the account for the current access token. This endpoint is only accessible without a business subdomain (that is, the host must be pike13.com ) and requires an access token granted to pike13.com .
- **List all Pike13 account businesses** (List). Account: Returns all the business objects for the Pike13 account specified by the current access token. This is very useful if you are building an app that self-discovers which Pike13 businesses a user is tied to.
- **Create a Pike13 account confirmation** (Create). Account: Tells the system to send a confirmation email to the given email address. For security reasons, the response will always be a 201 even if an account with that email address does not exist. A confirmation email will not be sent if the account is already confirmed. Required: account.
- **Create a Pike13 account password** (Create). Account: Tells the system to send a password reset email to the given email address. For security reasons, the response will always be a 201 even if an account with that email address does not exist. This endpoint is only accessible without a business subdomain (that is, the host must be pike13.com ). Required: account.
- **List all Pike13 account people** (List). Account: Returns all the person objects for the Pike13 account specified by the current access token. This is very useful if you are building an app that self-discovers which Pike13 businesses a user is tied to.
- **List all Pike13 desk appointment available slots** (List). Desk (staff view): Lists all available times for the given appointment for the given date, or for a date range with from and to . Required: service_id.
- **Pike13 desk appointment available slots summary** (Action). Desk (staff view): Returns availability "heat map" scores for the given appointment for the given date range - the parameters from and to . The score for each day is the percentage of availability relative to the day with the most availability. Required: service_id.
- **List all Pike13 desk available times** (List). Desk (staff view): Returns the open time remaining in each staff member's scheduled availability: their working hours minus their booked event occurrences, their blocked-off times, and location blackouts. Only staff members who are active and not hidden are included. Requires permission to view staff availability.
- **Create a Pike13 desk booking lease** (Create). Desk (staff view): Add a new Lease to an existing Booking. Required: booking_id, lease.
- **Update a Pike13 desk booking lease by ID** (Update). Desk (staff view): Allows you to update a Lease. The only thing that can be updated on the Lease is the person associated with it. You cannot change the leased service. You would need to delete the Lease and create a new one if you want to change the service. You can add an existing person by id or email. Required: id, booking_id, lease.
- **Create a Pike13 desk booking** (Create). Desk (staff view): Creates a Booking with one or more Leases. Required: booking.
- **Delete a Pike13 desk booking by ID** (Delete). Desk (staff view): Destroys the given Booking. If the Booking was completed, then just the Booking will be destroyed. The Visits and Invoices that it created won't be destroyed. If the Booking was not completed, it and any Leases, visits, plans and invoices created by it will be destroyed. i.e. Required: id.
- **Get single Pike13 desk booking by ID** (Get). Desk (staff view): Returns the given Booking. Required: id.
- **Update a Pike13 desk booking by ID** (Update). Desk (staff view): Allows you to complete a Booking. You cannot add any more Leases to the Booking using this endpoint. To add or update Leases use the Leases endpoint. Required: id, booking.
- **List all Pike13 desk business** (List). Desk (staff view): Returns the basic details of a business.
- **List all Pike13 desk business franchisees** (List). Desk (staff view): Returns the basic details of franchisees for a business.
- **List all Pike13 desk custom fields** (List). Desk (staff view): Lists the available custom fields. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at custom_fields.
- **List all Pike13 desk event occurrence enrollment eligibilities** (List). Desk (staff view): Returns a list of enrollment warnings and restrictions for an event occurrence based on person ids. Does not include dependents. Required: event_occurrence_id.
- **Create a Pike13 desk event occurrence note** (Create). Desk (staff view): POST /api/v2/desk/event_occurrences/:event_occurrence_id/notes 
POST /api/v2/desk/people/:person_id/notes. Required: event_occurrence_id, note.
- **Delete a Pike13 desk event occurrence note by ID** (Delete). Desk (staff view): Deletes a note. The acting access token must be tied to a Person that is either a manager, an owner, or the author of the note. Required: id, event_occurrence_id.
- **Get single Pike13 desk event occurrence note by ID** (Get). Desk (staff view): Returns the details for a note. Required: id, event_occurrence_id.
- **List all Pike13 desk event occurrence notes** (List). Desk (staff view): GET /api/v2/desk/event_occurrences/:event_occurrence_id/notes 
GET /api/v2/desk/people/:person_id/notes. Required: event_occurrence_id. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at notes.
- **Update a Pike13 desk event occurrence note by ID** (Update). Desk (staff view): PUT /api/v2/desk/event_occurrences/:event_occurrence_id/notes/:id 
PUT /api/v2/desk/people/:person_id/notes/:id. Required: id, event_occurrence_id, note.
- **List all Pike13 desk event occurrence visits** (List). Desk (staff view): Lists visits for a person or event occurrence. For a person, they are sorted by event_occurrence.start_at in ascending order. Paginate using the page parameter. The parameters to and from can be used to specify an event occurrence time range on the person's visits endpoint. Required: event_occurrence_id. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at visits.
- **List all Pike13 desk event occurrence waitlist entries** (List). Desk (staff view): Lists waitlist entries for a person or event occurrence. Paginate using the page parameter. Required: event_occurrence_id. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at waitlist_entries.
- **List all Pike13 desk event occurrence waitlist status** (List). Desk (staff view): Returns the status of the event occurrence's waitlist. Requires permission to view client waitlist entries. Required: event_occurrence_id.
- **Pike13 desk event occurrences cancel** (Cancel). Desk (staff view): Cancels a single event occurrence. On success the response is 201 Created with an empty body. Required: event_occurrence_id, cancellation.
- **Pike13 desk event occurrences change** (Action). Desk (staff view): Changes the staff members assigned to a single event occurrence. On success the response is 204 No Content with an empty body. Send the complete set of staff members you want assigned in organizer_ids . The set is replaced rather than merged, so a staff member you leave out is unassigned. Required: event_occurrence_id, change.
- **Get single Pike13 desk event occurrence by ID** (Get). Desk (staff view): Returns the details of an individual Event Occurrence. Required: id.
- **List all Pike13 desk event occurrences** (List). Desk (staff view): This returns a list of Event Occurrences for a time range (defaulting to today). The parameters to and from can be used to specify a time range. When the business has rooms enabled, each event occurrence may include a read-only resources array of assigned rooms (with availability and capacity).
- **Pike13 desk event occurrences summary** (Action). Desk (staff view): Returns a count of event occurrences by day or by hour of each day.
- **Get single Pike13 desk event by ID** (Get). Desk (staff view): Returns the details of an individual Event. Required: id.
- **List all Pike13 desk events** (List). Desk (staff view): This returns a list of Events viewable by staff members. The parameters from and to can be used to specify a time range, with a maximum of 120 days. Leaving from/to blank will get all events. All attendees for an event will be included. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at events.
- **Pike13 desk invoice item discounts bulk delete** (Delete). Desk (staff view): Removes the discount from the invoice item. A DELETE without a record id: the connector names it bulk_delete. Required: invoice_id, invoice_item_id.
- **Create a Pike13 desk invoice item discount** (Create). Desk (staff view): Creates the discount on the invoice item. If one already exists, it replaces the existing one. Required: invoice_id, invoice_item_id, discount.
- **List all Pike13 desk invoice item discounts** (List). Desk (staff view): Returns the discount for the invoice item. If none exists, it returns 404. Required: invoice_id, invoice_item_id.
- **Pike13 desk invoice item prorates bulk delete** (Delete). Desk (staff view): Remove proration from memberships for both amount cents and initial punchcard count. The initial punchcard count will be set to the default count. A DELETE without a record id: the connector names it bulk_delete. Required: invoice_id, invoice_item_id.
- **Create a Pike13 desk invoice item prorate** (Create). Desk (staff view): Prorate the first invoice and the first punchcard count. If the request is invalid, no proration is created. If a proration already exists, it updates it. Required: invoice_id, invoice_item_id, prorate.
- **Create a Pike13 desk invoice item** (Create). Desk (staff view): Add a plan_product to an existing invoice. Required: invoice_id, invoice_item.
- **Delete a Pike13 desk invoice item by ID** (Delete). Desk (staff view): Remove an invoice item from an existing invoice. The invoice won't be destroyed even if it has no invoice item after removing. If you don't want to keep it, you can simply abandon it and it will be automatically cleaned up. Invoice items for signup fee cannot be removed on its own. Required: id, invoice_id.
- **List all Pike13 desk invoice payment methods** (List). Desk (staff view): Lists the available payment methods for an invoice. This includes the available forms of payment and any extraneous options, like account credit. Required: invoice_id.
- **Create a Pike13 desk invoice payment** (Create). Desk (staff view): Create a payment for an invoice. Required: invoice_id.
- **Delete a Pike13 desk invoice payment by ID** (Delete). Desk (staff view): Deletes a payment that is still in the checkout state, such as one started with GET /api/v2/desk/invoices/:invoice_id/payments/new but never completed. Payments in any other state return 403; use a refund or void instead. Requires permission to delete client payments. Required: id, invoice_id.
- **Create a Pike13 desk invoice** (Create). Desk (staff view): Creates an invoice given a list of plan products. Required: invoice.
- **Get single Pike13 desk invoice by ID** (Get). Desk (staff view): Returns the details of a invoice. Required: id.
- **List all Pike13 desk invoices** (List). Desk (staff view): Returns a list of invoices. Paginate using the page parameter. The connector pages with Pike13's next link (per_page = the caller's limit, max 100); records at invoices.
- **Update a Pike13 desk invoice by ID** (Update). Desk (staff view): Update the state, due date or coupon_code of an invoice, or connect it to a booking. In the curl example below, the invoice is being closed. If there is a booking associated with the invoice, closing the invoice will automatically complete the booking and its leases. Required: id, invoice.
- **Get single Pike13 desk location by ID** (Get). Desk (staff view): Returns the details of a location. Required: id.
- **List all Pike13 desk locations** (List). Desk (staff view): Lists all locations for the business. When the business has rooms enabled, each location may include a read-only resources array (with availability and capacity). Resources cannot be added or removed through this API; use the Staff/Desk UI to manage location rooms.
- **List all Pike13 desk make up reasons** (List). Desk (staff view): Lists all Business make ups reasons.
- ...and 137 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
