Clover for AI agents
Clover runs point-of-sale operations for merchants, covering orders, payments, inventory, and employees through one platform built for physical retail stores. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Clover.
Create a new order
Create a new order with line items ready to be charged at checkout.
Check inventory stock
Check an item's current stock level before confirming it's available to sell.
Confirm before applying a discount
Confirm before applying a discount to an order, since it changes the amount charged.
209 Clover actions, graded by risk.
Every Clover action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
85Look things up. Allowed by default.
- clover.get_tagGet Tag
- clover.get_roleGet Role
- clover.get_orderGet Order
- clover.get_shiftGet Shift
- clover.list_tagsList Tags
- clover.get_tenderGet Tender
- clover.list_rolesList Roles
- clover.get_paymentGet Payment
- clover.list_ordersList Orders
- clover.list_shiftsList Shifts
- clover.get_categoryGet Category
- clover.get_customerGet Customer
- clover.get_discountGet Discount
- clover.get_employeeGet Employee
- clover.get_merchantGet Merchant
- clover.get_modifierGet Modifier
write
81Create and change things. Allow, or ask the user first.
- clover.create_tagCreate Tag
- clover.update_tagUpdate Tag
- clover.create_roleCreate Role
- clover.update_roleUpdate Role
- clover.update_orderUpdate Order
- clover.update_shiftUpdate Shift
- clover.create_optionCreate Option
- clover.create_tenderCreate Tender
- clover.update_optionUpdate Option
- clover.update_tenderUpdate Tender
- clover.update_paymentUpdate Payment
- clover.create_customerCreate Customer
- clover.create_discountCreate Discount
- clover.create_employeeCreate Employee
- clover.create_modifierCreate Modifier
- clover.create_tax_rateCreate Tax Rate
destructive
43Delete, cancel or archive. Ask first, or deny outright.
- clover.delete_tagDelete Tag
- clover.delete_roleDelete Role
- clover.delete_tagsDelete Tags
- clover.delete_orderDelete Order
- clover.delete_shiftDelete Shift
- clover.delete_optionDelete Option
- clover.delete_tenderDelete Tender
- clover.delete_customerDelete Customer
- clover.delete_employeeDelete Employee
- clover.delete_modifierDelete Modifier
- clover.delete_tax_rateDelete Tax Rate
- clover.delete_attributeDelete Attribute
- clover.delete_categoriesDelete Categories
- clover.delete_item_groupDelete Item Group
- clover.delete_item_stockDelete Item Stock
- clover.delete_order_typeDelete Order Type
Clover in three steps.
- 01Your users connect CloverThey sign in to Clover on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, writes like “create Tag” can wait for the user, and “delete Tag” can be denied outright.
- 03Any agent can actYour agent calls Clover through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('clover', { read: 'allow', write: 'ask', // create_tag destructive: 'deny', // delete_tag }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Clover connects.
Users sign in to Clover on Arc0 Connect and approve the scopes you request. Build with Arc0’s Clover OAuth app, or bring your own so the Clover consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
The same Clover connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Clover from any agent.
Clover and Arc0, answered.
Can I use Clover with Claude, ChatGPT or Cursor?
Yes. Connect Clover to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Clover actions you allow.
How do users connect Clover?
Users sign in to Clover on Arc0 Connect and approve the scopes you request. Build with Arc0’s Clover OAuth app, or bring your own so the Clover consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
Which Clover actions can my agent take?
209 in total: 85 read, 81 write and 43 destructive, such as “create Tag”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Clover?
Yes. Actions like “delete Tag” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Clover too?
Yes. The same Clover connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Clover into your agent.
Your users connect Clover once, under your brand. Your agent gets 209 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan