Productivity · Local MCP server
Clover POS
Clover POS for a single merchant: sales, inventory, orders, customers (reads + safe writes).
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SBolivarLoL/clover-mcp- Version
- 0.7.0
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-07-02
- Updated
- 2026-07-02
- Publisher
- SBolivarLoL (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SBolivarLoL) · how
- Repository
- github.com/SBolivarLoL/clover-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | clover-mcp | 0.7.0 | stdio |
How to connect Clover POS
Clover POS runs locally from a Python package published to PyPI: clover-mcp version 0.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx clover-mcp. It reads these environment variables: CLOVER_MERCHANT_ID (required), CLOVER_ACCESS_TOKEN (required, secret), CLOVER_REGION, CLOVER_SANDBOX, CLOVER_AUTH_MODE, CLOVER_REFRESH_TOKEN (secret), CLOVER_OAUTH_CLIENT_ID and CLOVER_OAUTH_CLIENT_SECRET (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"clover-mcp": {
"command": "uvx",
"args": [
"clover-mcp"
],
"env": {
"CLOVER_MERCHANT_ID": "<value>",
"CLOVER_ACCESS_TOKEN": "<secret>",
"CLOVER_REGION": "<value>",
"CLOVER_SANDBOX": "<value>",
"CLOVER_AUTH_MODE": "<value>",
"CLOVER_REFRESH_TOKEN": "<secret>",
"CLOVER_OAUTH_CLIENT_ID": "<value>",
"CLOVER_OAUTH_CLIENT_SECRET": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| CLIO WebProvider-fixed web search plus transparent URL, DOI, and document fetching. | Local · stdio |
| ClipformInteractive video forms that capture authentic responses. Build engaging forms in minutes. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ClippyCopy AI-generated content to the macOS clipboard: rich Gmail-ready email drafts, text, and files. | Local · stdio |
| CloudresumeResume builder with native MCP - create and edit resumes from your AI assistant. | Remote · HTTPLive check: sign-in required |
| Clover PublicJob search and interview prep MCP. 15 tools, OAuth 2.1, cross-LLM. four-leaf.ai. | Remote · HTTPLive check: sign-in required |
| ClutterGenerate synthetic companies, documents & data via the Clutter API (e.g. to fill SharePoint). | Local · stdio |
| CobblesThe shared task board for teams and their AI agents - connect over OAuth, every action signed. | Remote · HTTPLive check: ✗ no handshake |
| CodaInteract with Coda.io documents, tables, and rows via the Coda API. | Local · stdio |