Lucky

Name: Lucky
Author: dokdosolutions-us

by dokdosolutions-uscommunityv1.0.4

An MCP server that exposes the Clover POS V3 REST API as LLM-callable tools for restaurant operations such as menus, orders, inventory, customers, analytics, employees, financial reporting, reservations, and forecasting. It is designed to let AI agents query and perform Clover merchant actions through MCP instead of using the Clover dashboard directly.

From the registry: 🍀✨ MCP server for Clover POS — restaurant operations, inventory, orders, analytics, and retention

GitHub Repository

Install & configure

Prerequisites

required
Install Node.js 24+
Node.js version 24 or newer is required to run the MCP server via npx.
required
Create a Clover developer account and OAuth app
You need a Clover developer account with an OAuth app to obtain credentials for the server.
https://www.clover.com/developers
required
Obtain Clover API credentials
Get a Clover merchant API token and merchant ID for your sandbox or production store.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `lucky` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 24+** — Node.js version 24 or newer is required to run the MCP server via npx.
- **Create a Clover developer account and OAuth app** — You need a Clover developer account with an OAuth app to obtain credentials for the server. (https://www.clover.com/developers)
- **Obtain Clover API credentials** — Get a Clover merchant API token and merchant ID for your sandbox or production store.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@dokdosolutions/clover-mcp"]
- required environment variables:
  - `CLOVER_ACCESS_TOKEN`: Clover merchant API access token for the target store. (example: `<your-clover-access-token>`)
  - `CLOVER_MERCHANT_ID`: Clover merchant ID for the target store. (example: `<your-clover-merchant-id>`)
- optional environment variables:
  - `CLOVER_SANDBOX`: Set to true to use Clover's sandbox environment instead of production. (example: `<true-or-false>`)

Note: The README recommends the npm/npx path over running from source. For multi-store setups, run one MCP server instance per Clover location with a different CLOVER_ACCESS_TOKEN and CLOVER_MERCHANT_ID for each instance.

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.

Note: The README recommends the npm/npx path over running from source. For multi-store setups, run one MCP server instance per Clover location with a different CLOVER_ACCESS_TOKEN and CLOVER_MERCHANT_ID for each instance.