Ecommerce
Clover MCP connector
The Clover connector brings items, stock levels, item groups, tags, devices and merchant details into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update what Clover holds, signed in as themselves.
-
How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Clover to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Clover once
-
Open Connections, choose Add connection, and pick Clover.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Clover app, then approve. Clover needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Clover to 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.
Connect Clover to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Clover to 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.
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.
Use cases
What teams do with Clover through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
Clover tools for your AI agents
171 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.
See it in Elaichi
What connecting Clover gets you
6 screens from the product, each doing one job for your Clover account.
The agent
Ask Clover questions, get real answers.
Type a question in plain language and get answers pulled straight from live Clover records.
- items
- merchants
- devices
- stock
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 or Cursor
MCP clients
One Clover endpoint, every client connects.
Claude, ChatGPT and Cursor all reach Clover through one governed org endpoint, no SDK required.
Copy the endpoint
Tool catalog
171 Clover tools, zero custom code.
Every Clover method, from items to devices, cataloged and ready to call without writing a single line.
- Get single Clover merchant by ID
- Update a Clover merchant by ID
- List all Clover devices
- Get single Clover device by ID
Toolboxes
Every team gets its own Clover toolbox.
Sales, support and operations each work from a toolbox scoped to what their team needs.
- Sales
- Support
- Inventory
- Finance
Shared connections
Delegate Clover access without sharing logins.
See who connected each Clover account and how many teams and members share it.
- Retail West
- Downtown Store
- Flagship Location
- Warehouse Ops
Audit log
Every Clover action, logged and attributable.
Every call against Clover lands in an append-only log with who, what and when.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
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 digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Clover
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 block deleting items, stock or groups. A blocked Clover action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
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 and every other client at the same time.
Put Clover in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.