Clover POS for a single merchant: sales, inventory, orders, customers (reads + safe writes).
Clover POS MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Clover POS for a single merchant: sales, inventory, orders, customers (reads + safe writes).
MCP server for the Clover POS REST API — gives AI assistants (Claude, Cursor, etc.) read and safe-write access to a Clover merchant's sales, inventory, orders, and customers.
Once Clover POS is connected, these are the calls the assistant has available:
get_sales_summary — readget_top_items — readwhoami — readapply_order_discount — writeBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: CLOVER_MERCHANT_ID, CLOVER_ACCESS_TOKEN, CLOVER_REGION, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, CLOVER_OAUTH_CLIENT_ID, CLOVER_OAUTH_CLIENT_SECRET, CLOVER_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Clover POS's toolset — get_sales_summary, get_top_items, whoami and 1 more — is a fair guide to whether it matches your workflow. It is maintained by SBolivarLoL; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_sales_summary | read |
| get_top_items | read |
| whoami | read |
| apply_order_discount | write |
{
"mcpServers": {
"clover": {
"command": "uvx",
"args": ["clover-mcp"],
"env": {
"CLOVER_MERCHANT_ID": "your_merchant_id",
"CLOVER_ACCESS_TOKEN": "your_token",
"CLOVER_REGION": "na"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CLOVER_MERCHANT_ID | Configuration value read at startup. | Optional |
| CLOVER_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| CLOVER_REGION | Configuration value read at startup. | Optional |
| OTEL_EXPORTER_OTLP_ENDPOINT | Configuration value read at startup. | Optional |
| OTEL_SERVICE_NAME | Configuration value read at startup. | Optional |
| CLOVER_OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| CLOVER_OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| CLOVER_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.