Clover
Manage Clover merchant, inventory, customer, employee, order, payment, cash, notification, app, and print data through the regional Platform REST API.
Verdict
Common use cases
- Create orders from chat or email requests
- Reconcile daily sales and payment totals
- Sync customer records across CRM and POS
- Apply discounts or service charges programmatically
- Track inventory changes after restocking
Integration
- Vendor
- Clover
- Category
- other
- Auth
- OAUTH2
- Tools
- 50
- Composio slug
clover
Tools
- Apply Modification To Line Item
Applies a modifier to an order line item and snapshots the modifier's current name and price as a modification record.
- Apply Order Service Charge
Applies a configured merchant service charge or creates an ad-hoc order-fee line item on an order. Choose `mode` explicitly so Clover receives the matching body and route.
- Checkout Atomic Order
Calculates and previews an order cart, including totals, taxes, discounts, and service charges, without persisting an order.
- Create Address For Customer
Adds a postal address to an existing customer record; it does not create the customer.
- Create App Billing Metered Event
Records metered app usage and bills the merchant at the configured price; `count` defaults to 1. This is irreversible, so verify an uncertain result before retrying to avoid billing twice.
- Create Atomic Order
Creates an order with line items, modifiers, discounts, and service charges while Clover calculates inventory-based totals and taxes. Maximum 3,000 line items.
- Create Attribute
Creates an inventory variant attribute within an item group, optionally with its initial options.
- Create Authorization On Payment
Create an authorization for a payment. This has financial consequences and is not safely retryable without first checking whether Clover created the authorization.
- Create Customer
Creates a customer record for the connected merchant with the supplied identity and contact details.
- Create Customer Card
Creates a vaulted credit or debit card record for a customer. `first6` and `last4` are required.
- Create Discount
Creates a merchant inventory discount with a fixed amount or percentage for later application.
- Create Discount On Line Item
Applies a named fixed-amount or percentage discount to one order line item.
- Create Discount On Order
Applies a named fixed-amount or percentage discount to an order subtotal, not a specific line item.
- Create Email Address For Customer
Adds an email address to an existing customer record; it does not create the customer.
- Create Employee
Creates a merchant employee profile with a required name and optional login, contact, and role details.
- Create Inventory Item
Creates an inventory item. Clover ignores `available=false` during creation and creates the item as available; call Update Inventory Item afterward to make it unavailable.
- Create Item Category
Creates an inventory category used to organize items in Clover Register.
- Create Item Category Associations
Creates one or more associations between inventory items and categories or subcategories. Every tuple requires both `category.id` and `item.id`.
- Create Item Group
Creates an item group for related inventory variants and their attributes.
- Create Item Modifier Group Associations
Creates an association between an inventory item and a modifier group so the group's modifiers can be applied to that item. Provide both `modifierGroup.id` and `item.id`.
- Create Item Option Associations
Creates one or more associations between Clover options and inventory items. Every tuple requires both `option.id` and `item.id`.
- Create Item Stock
Creates the stock quantity and optional low-stock alert threshold for one inventory item.
- Create Item Tax Rate Associations
Creates one or more associations between inventory items and tax rates. Every tuple requires both `item.id` and `taxRate.id`.
- Create Merchant Opening Hours
Creates merchant opening hours. Supply all seven weekday arrays and use an empty array for every closed day; for example, `{'sunday': [], 'monday': [{'start': 900, 'end': 1700}], 'tuesday': [], 'wednesday': [], 'thursday': [], 'friday': [],
- Create Modifier
Creates a named modifier with a price adjustment inside a specific modifier group.
- Create Modifier Group
Creates a new modifier group. After you create a modifier group, you can associate modifiers with the group.
- Create Multiple Inventory Items
Creates multiple inventory items in one request; use Update Inventory Items to patch existing items instead.
- Create Notification For App
Send a message to devices that have the connected Clover app installed and are listening for notifications. Delivery is irreversible and cannot be recalled; verify an uncertain result before retrying to avoid duplicate delivery.
- Create Notification For Device
Push a message to a device that has the connected Clover app installed and is listening for notifications. Delivery is irreversible and cannot be recalled; verify an uncertain result before retrying to avoid duplicate delivery.
- Create Option
Creates a named option within an inventory attribute, such as `Small` for a `Size` attribute.
- Create Order Line Item
Creates one line item for a standard or Multiple Service Charges order; provide `price` or `item.id`. Orders allow 2,500 line items with Multiple Service Charges and 3,000 otherwise.
- Create Order Line Items Bulk
Creates up to 100 priced line items for either a standard or Multiple Service Charges order. The order limit is 2,500 line items with Multiple Service Charges and 3,000 otherwise.
- Create Order Type Category Associations
Creates associations that limit an order type to specific merchant categories. Every tuple requires both resource IDs.
- Create Order Type For Merchant
Creates a custom order type for the merchant, such as dine-in, delivery, or takeout.
- Create Payment Record On Order
Records an externally processed payment on an order for bookkeeping; it does not process a Clover credit or debit payment. Requires a positive amount and merchant tender ID.
- Create Phone Number For Customer
Adds a phone number to an existing customer record; it does not create the customer.
- Create Role
Creates a merchant employee role based on a Clover system role.
- Create Shift For Employee
Creates a time-clock shift for one employee, including clock-in/out times, cash tips, or override details.
- Create Subcategory
Creates a subcategory within a parent inventory category; it inherits the parent's color when one is set.
- Create Tag
Creates an inventory tag for reporting, with optional item and printer associations.
- Create Tag Item Associations
Creates one or more associations between Clover tags and inventory items. Every tuple requires both `tag.id` and `item.id`.
- Create Tax Rate
Creates a merchant tax rate as a percentage or flat amount, optionally making it the default or associating items.
- Create Tender
Creates a merchant-level custom tender and returns its generated identifier.
- Delete All Line Items In Orderdestructive
Deletes every line item from an order. This is destructive; verify the order before calling.
- Delete App Billing Metered Eventdestructive
Deletes an unbilled app metered event. Billed events cannot be deleted; verify the event before calling.
- Delete Attributedestructive
Deletes an inventory variant attribute. This is destructive; verify the attribute identifier before calling.
- Delete Authorizationdestructive
Permanently delete a payment authorization. Only target an authorization the caller intends to remove; repeat only after confirming whether the first request succeeded.
- Delete Categoriesdestructive
Permanently deletes the categories identified by a comma-separated list of category IDs. Get IDs from List Categories and target only categories you intend to delete.
- Delete Customerdestructive
Deletes a customer from the connected merchant. This is destructive; verify the customer identifier before calling.
- Delete Customer Addressdestructive
Deletes one address from a customer. This is destructive; verify both identifiers before calling.
Setup
Setup guide
- 1Open a Switchy Project and click the MCP panel on the right. Search for Clover and click Connect. You'll be redirected to Clover's OAuth consent screen where you log in with your merchant account. Grant permissions for orders, inventory, payments, customers, and app billing when prompted. Clover will redirect you back to Switchy with a confirmation message. To test the connection, @mention Clover in a message and ask it to list recent orders or retrieve a customer by phone number. If it returns data, the integration is live. To invoke a tool, address Clover directly in your prompt and describe the task — for example, '@Clover create a new order for table 5 with two lattes and a croissant' or '@Clover pull the last 10 transactions from yesterday'.
What teammates see: by default, memories from Clover are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Walk-In Order
@Clover create an order with one large pepperoni pizza, extra cheese modifier, and one Caesar salad. Mark it for pickup in 20 minutes.
Pull Yesterday's Revenue
@Clover list all orders from yesterday that were marked paid, and calculate the total revenue including tips and service charges.
Add Customer Address
@Clover find the customer with phone number 555-0123 and add the address 789 Elm Street, Unit 4B, Springfield.
Apply Bulk Discount
@Clover apply a 15% loyalty discount to order ID abc123 and recalculate the total with tax.
Check Inventory Levels
@Clover show me the current inventory count for all coffee beans and syrups, and flag any items below 10 units.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@clover show me all open orders from the last 2 hours with totals over $50, grouped by payment status
Found 14 open orders in the last 2 hours exceeding $50. 9 are awaiting payment (totaling $847.32), 3 are partially paid ($201.15 outstanding), and 2 are fully authorized but not captured ($134.88). The largest unpaid order is #4521 at $156.40, placed 47 minutes ago. All orders are dine-in except one pickup. This data reflects your live Clover dashboard as of this query.
This example shows Clover's read-heavy order-filtering capability. The MCP can search orders by time window, amount thresholds, and payment state. Requires merchant read permissions. Be aware that high-volume merchants may hit rate limits if querying frequently across large date ranges.
@clover apply a 15% service charge called 'Large Party Fee' to order #4521 and add a line item for extra guacamole at $2.50
Applied 'Large Party Fee' (15% service charge) to order #4521, adding $23.46 to the subtotal. Added line item 'Extra Guacamole' at $2.50. Order total updated from $156.40 to $182.36 before tax. Changes are live in your Clover system and will appear on the customer's receipt. This action modified a real order and cannot be undone through the MCP.
Demonstrates Clover's write capability for modifying live orders. This example uses two separate tools: Apply Order Service Charge and a line-item creation endpoint. These actions are immediate and irreversible—verify order details before running commands that alter pricing or inventory. Requires order-write permissions.
@clover draft a summary of today's sales performance, breaking down revenue by item category and highlighting any inventory items that sold out
Today's sales total $3,214.67 across 87 transactions. Top category: Entrees ($1,802.30, 54 orders). Beverages contributed $687.15 (41 orders), and Sides $725.22 (38 orders). Three items sold out: 'Seasonal Soup' (12 sold), 'House Salad' (18 sold), and 'Craft IPA' (9 sold). Average ticket size is $36.95, up 8% from yesterday. Peak hour was 12:30–1:30 PM with $892 in revenue. Data current as of this query.
This synthesis example pairs Clover's order and inventory APIs with AI reasoning to produce a business intelligence summary. The MCP fetches raw transaction and stock data; the AI aggregates and interprets it. Useful for end-of-day reports or real-time dashboards. Accuracy depends on Clover's sync state—delayed inventory updates may affect sold-out detection.
Use-case deep-dives
When Clover makes sense for multi-location food service teams
A 12-person restaurant group running three locations needs real-time order data in Slack and a nightly revenue rollup in Google Sheets. Clover's MCP is the right call here because it exposes the full order lifecycle—line items, modifiers, service charges, taxes—through 50+ tools that mirror the POS API. Your team can build a standup dashboard that pulls yesterday's top-selling items or flag orders with custom modifiers that signal kitchen mistakes. The OAuth2 flow means each location manager authenticates once and the integration persists. The threshold: if you only need basic sales totals, Clover's merchant reporting UI is faster than writing MCP queries. But if you're correlating POS data with labor schedules or inventory audits, this MCP saves you from screen-scraping receipts.
Use Clover's metered billing when your app charges per transaction
A two-person dev shop built a Clover marketplace app that auto-applies loyalty discounts at checkout. They need to bill merchants $0.05 per redemption without running their own payment infrastructure. Clover's "Create App Billing Metered Event" tool is purpose-built for this: you fire the event when a discount applies, Clover invoices the merchant monthly, and you get paid through their app marketplace split. The catch is the tool is irreversible—if your logic double-fires, the merchant gets billed twice and you handle the refund manually. So the buying call is narrow: if your app monetizes on Clover transaction volume and you can guarantee idempotent event logic, this MCP is cheaper than Stripe metered billing. If your billing has edge cases or you serve multiple POS platforms, build your own ledger.
When Clover's customer tools beat manual data entry for retail
A five-person boutique clothing brand migrated from Shopify to Clover and needs to import 8,000 customer shipping addresses so in-store staff can look up past orders. The "Create Address For Customer" tool handles this in a batch script: you map your CSV to Clover's customer IDs, loop through rows, and POST each address. OAuth2 means the script runs unattended overnight. The limitation is you must create the customer record first—this tool only adds addresses to existing customers, so your import needs a two-pass strategy. If your address data is clean and you're already on Clover, this MCP is faster than hiring a VA to key in records. If you're evaluating Clover versus Square and address import is a dealbreaker, test the two-pass flow before you commit to the platform.
Frequently asked
What does the Clover MCP do in Switchy?
It lets your AI agents create orders, apply discounts, manage inventory attributes, process payments, and handle customer addresses directly in your Clover point-of-sale system. Agents can preview order totals with taxes and service charges before committing, or execute atomic order creation with up to 3,000 line items. This is useful for automating order entry, billing workflows, or syncing customer data across systems.
Do I need admin access to connect Clover via OAuth2?
You need a Clover merchant account with permission to install apps and authorize OAuth scopes. The integration requests access to orders, payments, inventory, and customer data. If you're not the account owner, confirm with your admin that you can authorize third-party apps. Clover's OAuth flow will show exactly which permissions Switchy requests before you approve.
Can the Clover MCP refund payments or void transactions?
The representative tools show payment authorization creation, not refunds or voids. If your use case requires reversing charges, check Clover's API documentation to confirm those endpoints exist, then ask Switchy support whether the MCP exposes them. Many payment operations are intentionally one-way to prevent accidental financial actions, so refunds may require manual POS access.
Why use this instead of Clover's dashboard or API directly?
The MCP lets AI agents execute Clover operations in natural language as part of multi-step workflows—like creating an order, applying a discount, then notifying a customer via Slack. You avoid writing OAuth boilerplate or parsing Clover's REST responses. If you only need one-off order entry, the Clover dashboard is faster. If you're building custom integrations, the raw API gives you more control.
Who on the team should connect the Clover integration?
Whoever manages your Clover merchant account or has permission to install apps. Once connected, any Switchy workspace member can invoke Clover tools through agents, so limit workspace access if you want to control who can create orders or process payments. The integration doesn't consume Clover user seats, but metered billing events created via the MCP will appear on your Clover invoice.