# SpotOn MCP connector

The SpotOn connector brings your employees, jobs, locations, menu items and loyalty customers into Claude, ChatGPT, Cursor and Microsoft Copilot, so everyone works in their own SpotOn access and every action is logged.

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

## Facts

| | |
| --- | --- |
| Application | SpotOn |
| Category | Ecommerce |
| AI tools | 48 |
| 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 SpotOn is connected

- List every employee at the Main Street location with their jobs.
- Add 250 loyalty points to Maria Lopez for her catering order.
- Which items does our Austin location carry right now?

## Connect SpotOn in Elaichi

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

1. Open Connections, choose Add connection, and pick SpotOn.
2. Optionally set Share with, then press Connect.
3. Supply your own SpotOn app, then approve. SpotOn 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 SpotOn tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

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

### Add a new hire to the right location

HR. Create the employee record in SpotOn with the correct job and location in one ask, or add a whole opening-day crew at once from a list.

### Keep employee records current after a change

HR. Update an employee's job or details when they move locations, and remove the record on their last day without opening SpotOn.

### Reward a loyal guest on the spot

Marketing. Add points to a guest's SpotOn loyalty account after a catering order, redeem them when asked, or reverse an accrual that was entered by mistake.

### Check what a promotion is worth before launch

Marketing. Calculate how a SpotOn loyalty promotion applies to a given order so the offer is right before it goes out to guests.

### Look up a location and its menu items

Operations. Pull a location's details, the items it carries and the jobs and break types set up there, all answered from live SpotOn records.

### Bring a new location online

Operations. Onboard a new SpotOn location, confirm it is authorized, and offboard one that has closed, with each step recorded in the audit log.

## Elaichi vs Zapier MCP vs Composio for SpotOn

All three can connect SpotOn 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 SpotOn tools | Allow or restrict single SpotOn 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 SpotOn 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 SpotOn to Claude?

Connect SpotOn in Elaichi first: SpotOn connects over OAuth, and it asks for an OAuth application that you register inside SpotOn yourself, so one person brings a client ID and secret a single time. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Claude can work with your SpotOn employees, locations and loyalty customers.

### Does SpotOn work with ChatGPT and Cursor as well as Claude?

Yes. SpotOn is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up per client.

### What can an AI agent actually do with my SpotOn data?

It can look up and update SpotOn employees, list jobs and break types at a location, pull the items a location carries, and onboard or offboard a location. It can also add, redeem or reverse loyalty points for a guest and work out what a loyalty promotion is worth. Short, concrete asks such as "add 200 points to Maria Lopez" work better than long paragraphs.

### Does connecting SpotOn give the AI access to every location?

No. Access follows whoever signed in: if your SpotOn account only reaches two locations, the agent only reaches those two. Elaichi can narrow that further with restrictions, and it never widens what SpotOn already lets a person see.

### Can my team share one SpotOn connection?

Yes. One person connects SpotOn in Elaichi and shares the connection with a team, and nobody else ever handles the client ID or secret. Each person still signs in as themselves, so the audit log names who added an employee or redeemed a guest's points.

### Can I stop an agent from deleting or changing things in SpotOn?

Yes. Restrictions in Elaichi work per action, so you can allow looking up SpotOn employees while restricting removing them, or allow accruing loyalty points while restricting reversals, set on a role or on one person. A restricted action still shows in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a SpotOn connection when someone leaves?

Offboarding a person in Elaichi ends their access to SpotOn at once, across every client they had connected. A SpotOn connection shared with a team keeps working for everyone else. If you disconnect SpotOn in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

### Does the SpotOn MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. SpotOn 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 SpotOn?

Yes. Both let Claude, ChatGPT or Cursor use SpotOn. 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 SpotOn call.

### How is Elaichi different from Composio for SpotOn?

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 SpotOn: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 48 SpotOn tools

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

- **Get single SpotOn break type by ID** (Get). Retrieve Break Type Details. Retrieve details for a specific break type. Required: id.
- **List all SpotOn break types** (List). Retrieve Break Types. Retrieve all break types associated with a specific Business Location ID.
- **SpotOn employees bulk create** (Create). Bulk Create Employees. Create multiple employees at a specific Business Location in a single request. EXPRESS ONLY. When every employee fails, the connector returns an error with their messages; a partial success (HTTP 207) stays a success with per-employee results. Required: requested_by_employee_id, employees.
- **Create a SpotOn employee** (Create). Create Employee. Create a new employee at a specific Business Location. EXPRESS ONLY. Required: first_name, last_name, permission, pin, requested_by_employee_id.
- **Get single SpotOn employee by ID** (Get). Retrieve Employee Details. Retrieve details for a specific employee. Required: id.
- **List all SpotOn employees** (List). Retrieve Employees. Retrieve all employees associated with a specific Business Location ID.
- **SpotOn employees remove** (Delete). Delete Employee. Delete an employee from a specific Business Location. EXPRESS ONLY. A DELETE with a JSON body (requested_by_employee_id): the connector drops the body of a method named delete, so this is remove, with the record id as a named field. Required: employee_id, requested_by_employee_id.
- **Update a SpotOn employee by ID** (Update). Update Employee. Update an existing employee at a specific Business Location. EXPRESS ONLY. Required: id, requested_by_employee_id.
- **SpotOn health check** (Action). Liveliness check.
- **List all SpotOn items** (List). Retrieve all Menu Items. Retrieve a list of all menu items for a given location. The connector pages with page / per_page (per_page = the caller's limit, max 500); records at items.
- **Get single SpotOn job by ID** (Get). Retrieve Job Details. Retrieve details for a specific job. Required: id.
- **List all SpotOn jobs** (List). Retrieve Jobs. Retrieve all jobs associated with a specific Business Location ID.
- **Get single SpotOn jobs v 2 by ID** (Get). Retrieve Job Details V2. Retrieve details for a specific job. Required: id.
- **List all SpotOn location candidates** (List). Get eligible locations for onboarding. Retrieves a list of locations assigned to the authenticated user that can be onboarded to the partner application. Needs a Sign In With SpotOn (user token) connection.
- **Get single SpotOn location by ID** (Get). Retrieve Location Details. Retrieve details for a merchant’s location. The id is the Business Location ID (BLID). Required: id.
- **SpotOn locations is authorized** (Action). Validate if an authenticated user has access to a BLID. Retrieves a list of locations assigned to the authenticated user and checks if provided BLID is one of them. Needs a Sign In With SpotOn (user token) connection. Required: location_id.
- **SpotOn locations offboard** (Action). Remove a third-party integration's access to a merchant's location. Provide the merchant's Business Location ID to revoke a third-party integration's API access. This endpoint supports both User Authorization tokens and Client Credential tokens for authentication. Works with either connection (user or service token). Required: location_id.
- **SpotOn locations onboard** (Action). Grant a third-party integration access to a merchant's location. Provide the merchant's Business Location ID to grant a third-party integration API access. Needs a Sign In With SpotOn (user token) connection. Required: location_id.
- **SpotOn loyalty customers accrue** (Action). Accrue Loyalty Points. Accrue loyalty points for a customer’s order. Required: customer_id, order_id, subtotal.
- **List all SpotOn loyalty customers** (List). Lookup Customers. Look up customers at a location using one of two mutually exclusive modes: - Search: set search_text (+ optional max_results) for a type-ahead query; returns any number of matches. - Exact lookup: set exactly one lookup key (customer_id, email, phone, external_app_id, or card_code); returns at most one match.
- **SpotOn loyalty customers redeem** (Action). Redeem Rewards. Redeem loyalty promotions for a customer’s order. Required: customer_id, order_id, promotion_ids.
- **SpotOn loyalty customers reverse** (Action). Reverse Transaction. Reverse all loyalty transactions associated with an order (ie. accruals & redemptions). Only one successful transaction reversal is allowed per order. All subsequent attempts after the first successful request will fail. Only promotions of ‘TYPE_REWARD’ can be reversed. Required: customer_id, order_id, loyalty_transaction_id.
- **SpotOn loyalty customers upsert** (Upsert). Manage Customer. [Upsert] Retrieve customer details using an ID, email address, or phone number. If the customer does not exist it will be created. If the customer exists it will be updated.
- **SpotOn loyalty promotions calculate** (Action). Retrieve Available Promotions. Retrieve the available promotions that can be applied to a customer’s order. Required: order.
- **Get single SpotOn loyalty status by ID** (Get). Retrieve Merchant Loyalty Status. Determine if loyalty is active at a merchant’s location. The id is the Business Location ID (BLID). Required: id.
- **List all SpotOn menu items** (List). Retrieve Menu Items. Retrieve the items associated with a location's menu. Required: menu_id. The connector pages with page / per_page (per_page = the caller's limit, max 500); records at items.
- **Get single SpotOn menu by ID** (Get). Retrieve Single Menu. Retrieve a single menu for a given location. Required: id.
- **List all SpotOn menus** (List). Retrieve Menus. Retrieve a list of all available menus for a given location. The connector pages with page / per_page (per_page = the caller's limit, max 500); records at menus.
- **List all SpotOn modifiers** (List). Retrieve all Menu Modifiers. Retrieve a list of all menu modifiers for a given location. The connector pages with page / per_page (per_page = the caller's limit, max 500); records at modifiers.
- **SpotOn orders cancel** (Cancel). Cancel Order. Cancel an order on the POS. Required: order_id.
- **Create a SpotOn order** (Create). Submit Order. Inject an order into the POS at a given location. Required: order.
- **SpotOn orders propose** (Action). Propose Order. Validate an order before injection to confirm pricing, taxes, and item availability. Required: order.
- **List all SpotOn reporting categories** (List). Retrieve Reporting Categories. Retrieve a list of all reporting categories for a given location. The connector pages with page / per_page (per_page = the caller's limit, max 500); records at reporting_categories.
- **List all SpotOn reporting orders** (List). Retrieve Orders. Retrieve a list of historical orders for a given location. The connector pages with page / per_page (per_page = the caller's limit, max 1000); records at orders.
- **SpotOn reservation locations activate** (Activate). Activate Location. Activate reservations for a location. Required: external_restaurant_id.
- **SpotOn reservations cancel** (Cancel). Cancel Reservation. Cancel a reservation. Required: external_reservation_id.
- **SpotOn reservations change party size** (Action). Change Party Size. Change the party size of a seated reservation. Required: external_reservation_id, party_size.
- **SpotOn reservations reseat** (Action). Reseat Reservation. Reseat a reservation at a new table(s) and/or with a new server(s). Required: external_reservation_id.
- **SpotOn reservations seat** (Action). Seat Reservation. Create and seat a reservation at a location. Required: external_restaurant_id, external_reservation_id, party_size, scheduled_time, customer.
- **SpotOn reservations unseat** (Action). Unseat Reservation. Unseat a seated reservation and remove it from the POS. Required: external_reservation_id.
- **Create a SpotOn shift** (Create). Create Shift. Create a new shift at a specific Business Location. EXPRESS ONLY. Required: requested_by_employee_id, employee_id, start_date, end_date.
- **Get single SpotOn shift by ID** (Get). Retrieve Shift Details. Retrieve details for a specific shift. EXPRESS ONLY. Required: id, requested_by_employee_id.
- **List all SpotOn shifts** (List). List Shifts. Retrieve all shifts associated with a specific Business Location ID. EXPRESS ONLY. Required: requested_by_employee_id.
- **SpotOn shifts remove** (Delete). Delete Shift. Delete a shift from a specific Business Location. EXPRESS ONLY. A DELETE with a JSON body (requested_by_employee_id): the connector drops the body of a method named delete, so this is remove, with the record id as a named field. Required: shift_id, requested_by_employee_id.
- **Update a SpotOn shift by ID** (Update). Update Shift. Update an existing shift at a specific Business Location. EXPRESS ONLY. Required: id, requested_by_employee_id.
- **List all SpotOn tables** (List). List Tables. List the dining tables configured for a location. To assign a table when seating or reseating a party, pass the table's name (not its id) in the table_names field of SeatReservation or ReseatReservation.
- **Get single SpotOn time punch by ID** (Get). Retrieve Time Punch Details. Retrieve details of a specific time punch. Required: id.
- **List all SpotOn time punches** (List). Retrieve Time Punches. Retrieve all time punches for a specific Business Location ID within a specified date range. Required: start_date, end_date.
