MCP server for the Clover POS REST API that gives AI assistants read access to merchant sales, inventory, orders, customers, and related records, plus a few safe write actions like updating item prices, stock quantities, and creating customers. It runs locally over stdio for a single merchant or remotely over HTTP with OAuth.
From the registry: Clover POS for a single merchant: sales, inventory, orders, customers (reads + safe writes).
Please install the `clover-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install uv** — Install the uv Python package manager/runner so you can launch the server with uvx. (https://docs.astral.sh/uv/)
- **Create Clover API credentials** — Create or obtain Clover credentials for your merchant. In the default token auth mode, you need a merchant ID and access token. Use least-privilege scopes for the tools you plan to use.
Optional prerequisites:
- Optional OAuth refresh setup — If using CLOVER_AUTH_MODE=oauth_refresh instead of the default token mode, also obtain a Clover OAuth client ID and client secret. You may also need initial token material or use the project's helper script to populate the token store.
Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["clover-mcp"]
- required environment variables:
- `CLOVER_MERCHANT_ID`: Your Clover merchant ID. (example: `<your-clover-merchant-id>`)
- `CLOVER_ACCESS_TOKEN`: Your Clover API access token. Required in the default token auth mode. (example: `<your-clover-access-token>`)
- optional environment variables:
- `CLOVER_REGION`: Clover region: na, eu, or la. (example: `<your-clover-region>`)
- `CLOVER_SANDBOX`: Set to true to use the Clover sandbox. (example: `<true-or-false>`)
- `CLOVER_AUTH_MODE`: Authentication mode: token or oauth_refresh. Defaults to token. (example: `<token-or-oauth_refresh>`)
- `CLOVER_OAUTH_CLIENT_ID`: Clover OAuth client ID. Required when using CLOVER_AUTH_MODE=oauth_refresh. (example: `<your-clover-oauth-client-id>`)
- `CLOVER_OAUTH_CLIENT_SECRET`: Clover OAuth client secret. Required when using CLOVER_AUTH_MODE=oauth_refresh. (example: `<your-clover-oauth-client-secret>`)
- `CLOVER_TOKEN_STORE`: Path to the token store file used for rotated OAuth tokens in oauth_refresh mode. (example: `<path-to-token-store>`)
- `CLOVER_REFRESH_TOKEN`: Clover refresh token. Optional alternative for oauth_refresh mode if not using the helper script to populate the token store. (example: `<your-clover-refresh-token>`)
Note: The README recommends the portable stdio launch via uvx. A PyPI publish is noted as 'coming soon', but the documented client configs already use `uvx clover-mcp`. The server also supports remote/hosted HTTP deployment, but the README defers the actual hosted setup details to docs/DEPLOY.md, so the canonical extract uses the clearly documented local stdio configuration.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CLOVER_MERCHANT_IDrequiredClover merchant IDCLOVER_ACCESS_TOKENrequiredClover API access tokenMeta Ads MCP (Facebook + Instagram) - analyze performance, manage budgets, pause campaigns.