Clover MCP connector
The Clover connector brings items, stock levels, item groups, tags, devices and merchant details into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and update what Clover holds, signed in as themselves.
- OAuth or API key
- Free 14-day trial
- No credit card
Show me items low on stock across all Clover stores.
Working in Clover with Elaichi
-
Get single Clover merchant by ID
-
List all Clover devices
-
Get single Clover device by ID
How to connect Clover to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Clover 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.
Clover 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.
Clover 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.
Clover 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.
Clover 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 Clover 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 Clover through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Clover is logged.
-
Inventory
Fix stock counts after a delivery
Read the delivery note aloud and have the stock level for each Clover item updated to match, then confirm what changed before the next shift opens the register.
-
Merchandising
Add a new product line in one go
Paste a supplier list and create the whole set of Clover items at once, with prices, tags and an item group so they show up together on the register.
-
Operations
Reprice a whole category before the weekend
Ask for every item in a group, review the new prices in a table, and push the bulk update to Clover so all locations ring up the same amount.
-
Store management
Know which registers are set up where
List the Clover devices attached to a merchant, spot one that is missing or misnamed, and get the answer without walking the floor or calling support.
-
Kitchen and menu
Keep menu groups and tags tidy
Find items that were added without a group or tag, sort them into the right Clover item group, and retire duplicates so the menu on the register matches the one on the wall.
-
Owners
Keep merchant details current across locations
Pull the details Clover holds about each merchant, check them against what is on the door, and update anything that has drifted, all from one conversation.
Try asking
- “Show me items low on stock across all Clover stores.”
- “Draft a summary of today's Clover orders by device.”
- “List merchants added to Clover this month.”
What connecting Clover gets you
6 screens from Elaichi, each doing one job for your Clover account.
Ask Elaichi to work across your apps.
Show me items low on stock across all Clover stores.
Draft a summary of today's Clover orders by device.
List merchants added to Clover this month.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Clover questions, get real answers.
Type a question in plain language and get answers pulled straight from live Clover records.
Copy the endpoint
AI apps
One Clover endpoint, every client connects.
Claude, ChatGPT, Cursor and Microsoft Copilot all reach Clover through one governed org endpoint, no SDK required.
Tool catalog
272 Clover tools, zero custom code.
Every Clover method, from items to devices, cataloged and ready to call without writing a single line.
Toolboxes
Every team gets its own Clover toolbox.
Sales, support and operations each work from a toolbox scoped to what their team needs.
Shared connections
Delegate Clover access without sharing logins.
See who connected each Clover account and how many teams and members share it.
Audit log
Every Clover action, logged and attributable.
Every call against Clover lands in an append-only log with who, what and when.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Clover digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch items
Clover
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
Clover
Queued
Automations
A schedule fires, Clover work gets done.
Records are fetched, grouped and drafted into a digest, then a person approves before it posts back.
Clover health
Refreshed 4 minutes ago · every 15 minutes · from the items collection
Items
1,284 ↓ 12%
Merchants
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Items created
Last 14 days
By team
Share of activity
Retail West 34%
Downtown Store 27%
Flagship Location 21%
Warehouse Ops 18%
Collections and dashboards
Clover metrics that update themselves.
A 14 day chart of records created and a breakdown by team, refreshed on a schedule with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Clover
All three can connect Clover 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 Clover tools | Allow or restrict single Clover 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 Clover 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.
Clover tools for your AI agents
272 tools are ready to call through Elaichi's MCP endpoint the moment you connect Clover, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 263 of 272 Clover tools here. Connect Clover and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Clover to Claude?
First connect Clover in Elaichi. Clover needs an OAuth application that your company registers inside its own Clover account, so one person brings a client ID and secret once, or uses a Clover API key instead, and Elaichi keeps it from then on. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and Clover is ready to use.
Does Clover work with ChatGPT and Cursor as well as Claude?
Yes. Once Clover 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 Clover once and every client sees it, with the same access and the same audit log.
What can an AI agent actually do with my Clover data?
With Clover connected, an agent can look up items, stock levels, item groups, tags, devices and merchant details, and it can create, update or remove items, stock counts and groups, one at a time or in bulk. In practice that means asking for a stock count, adding a batch of new products, repricing a category or checking which registers are attached to a location. Clover exposes a lot of actions, so short, concrete asks like update the stock for these five items work better than one long paragraph.
Does connecting Clover give the AI access to every merchant and location?
No. When you connect Clover through Elaichi, the agent works inside the Clover account you signed in with and can only reach the merchants, items, devices and stock that account already sees. Elaichi can narrow that further, for example to reading items but never deleting them, but it can never widen what your Clover account is allowed to do.
Can I stop an agent from deleting or changing things in Clover?
Yes. In Elaichi you restrict Clover actions individually, so you can allow reading items and stock, allow updates, and restrict deleting items, stock or groups. A restricted Clover action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Clover connection when someone leaves?
Offboarding that person in Elaichi ends their access to Clover at once, across every client they used. If they had shared a Clover connection with a team, it keeps working for everyone else. If you want Clover gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Clover MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Clover 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 Clover?
Yes. Both let Claude, ChatGPT or Cursor use Clover. 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 Clover call.
How is Elaichi different from Composio for Clover?
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 Clover: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Clover 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