Skip to content

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.

1

In Elaichi

Connect Clover once

  1. Open Connections, choose Add connection, and pick Clover.

  2. Optionally set Share with to give a team access, then press Connect.

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

clover
Clover
Active Ants
Bigcommerce
Bol.com
Channable
Cin7
2

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.

Clover MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Clover MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 171 Clover tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Clover, by what to check
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 $15 per user per month. 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.

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
Get single Clover merchant by ID Get Get a single Clover merchant by id. Returns the merchant record including id, name, reseller_id, owner account details, and address. Required: id.
Update a Clover merchant by ID Update Update a Clover merchant by id, changing fields such as its name, owner account, or address. Returns the updated merchant record including id, name, reseller_id, owner, and address. Required: id, name, owner.
List all Clover devices List List all devices provisioned to a Clover merchant. Returns each device's id, name, serial, model, deviceTypeName, merchant, deleted_time, and orderPrefix. Required: m_id.
Get single Clover device by ID Get Get a single device provisioned to a Clover merchant by id. Returns: id, trackStock, updateStock. Required: m_id, id.
List all Clover sync List Get the sync token for a merchant data table in Clover. Returns a table-specific record including its id and attributes. Required: m_id, table. This endpoint is deprecated.

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
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Clover · orders and merchants

Clover starter 18 Mar 4, 2026

Support toolbox

Clover · devices and sync issues

— 9 Mar 2, 2026

Inventory toolbox

Clover · items and stock levels

— 24 Feb 27, 2026

Finance toolbox

Clover · merchant payouts and totals

Clover starter 6 Feb 19, 2026

Operations toolbox

Clover · bulk item updates

— 31 Jan 30, 2026

IT toolbox

Clover · devices and merchant accounts

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
CL

Clover (Retail West)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CL

Clover (Downtown Store)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CL

Clover (Flagship Location)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CL

Clover (Warehouse Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CL

Clover (Regional Franchise)

Connected by Ryan Hayes

Personal • Active Not shared
CL

Clover (Pop-up Shop)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Clover Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Clover Items Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Clover Items List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch items

    Clover

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 my team share one Clover connection?

Yes. One person connects Clover in Elaichi and shares the connection with a team, and nobody else ever handles the Clover client ID, secret or API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who changed a price or a stock count in Clover.

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.