Jake Shore 33b4fdabf1 Rebrand to MCPEngage and add Clover-specific content
- Fixed all MCPEngine → MCPEngage references
- Added 8 Clover-specific power moves for restaurant/retail POS
- Updated README with accurate tool count and real Clover REST API details
- Added proper OAuth + merchant ID authentication documentation
- Updated package.json author
- Enhanced .env.example with detailed credential instructions
2026-02-02 07:01:17 -05:00

7.3 KiB

🚀 Don't want to self-host? Join the waitlist for our fully managed solution →

Zero setup. Zero maintenance. Just connect and automate.


🍽️ Clover MCP Server — 2026 Complete Version

💡 What This Unlocks

This MCP server gives AI direct access to your Clover POS system. Instead of manually managing orders, inventory, and payments, you just tell the AI what you need.

🎯 Restaurant & Retail Power Moves

The AI can directly control your Clover POS with natural language:

  1. Real-Time Order Intelligence — "Show me all open orders from the last hour" or "Get full details on order #12345 including line items and payments"
  2. Smart Inventory Management — "Check stock levels for all items" or "List all menu items and their current inventory status"
  3. Customer Data Access — "Find customers who've ordered in the past 30 days" or "Get customer contact info for email campaigns"
  4. Payment Reconciliation — "Show me all successful payments from yesterday" or "List declined payments that need follow-up"
  5. Merchant Operations — "Get my merchant settings and business hours" or "Check current timezone and location settings"

🔗 The Real Power: Combining Tools

AI can chain multiple Clover operations together:

  • Query orders → Filter by status → Generate daily sales summary
  • Check inventory → Identify low stock → Create purchase order list
  • Pull customer data → Analyze order history → Send targeted promotions
  • Review payments → Flag anomalies → Export for accounting

📦 What's Inside

8 powerful API tools covering core Clover POS operations:

  • Orders: list_orders, get_order, create_order
  • Inventory: list_items, get_inventory
  • Customers: list_customers
  • Payments: list_payments
  • Merchant: get_merchant

All with proper error handling, automatic authentication, and TypeScript types.

🚀 Quick Start

Option 1: Claude Desktop (Local)

  1. Clone and build:

    git clone https://github.com/BusyBee3333/Clover-MCP-2026-Complete.git
    cd clover-mcp-2026-complete
    npm install
    npm run build
    
  2. Get your Clover API credentials:

    • Go to Clover Developer Dashboard
    • Create an app (or use existing)
    • Generate an API token (OAuth 2.0)
    • Get your Merchant ID from your Clover dashboard
  3. Configure Claude Desktop:

    On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    On Windows: %APPDATA%\Claude\claude_desktop_config.json

    {
      "mcpServers": {
        "clover": {
          "command": "node",
          "args": ["/ABSOLUTE/PATH/TO/clover-mcp-2026-complete/dist/index.js"],
          "env": {
            "CLOVER_API_KEY": "your-oauth-token-here",
            "CLOVER_MERCHANT_ID": "your-merchant-id-here",
            "CLOVER_REGION": "US"
          }
        }
      }
    }
    
  4. Restart Claude Desktop

Option 2: Deploy to Railway

Deploy on Railway

  1. Click the button above
  2. Set CLOVER_API_KEY, CLOVER_MERCHANT_ID, and CLOVER_REGION in Railway dashboard
  3. Use the Railway URL as your MCP server endpoint

Option 3: Docker

docker build -t clover-mcp .
docker run -p 3000:3000 \
  -e CLOVER_API_KEY=your-token \
  -e CLOVER_MERCHANT_ID=your-merchant-id \
  -e CLOVER_REGION=US \
  clover-mcp

🔐 Authentication

Clover uses OAuth 2.0 authentication with merchant-specific API keys.

Required credentials:

  • CLOVER_API_KEY — OAuth access token from Clover Developer Dashboard
  • CLOVER_MERCHANT_ID — Your unique merchant identifier (find in Clover Setup → Business Information)
  • CLOVER_REGION — API region: US (default), EU, or LA (Latin America)

Sandbox testing:

  • Set CLOVER_SANDBOX=true to use the sandbox environment (apisandbox.dev.clover.com)

Official docs: Clover REST API Authentication

The MCP server handles API routing and authentication headers automatically.

🎯 Example Prompts for Claude

Once connected, you can use natural language to control your Clover POS:

Order Management:

  • "Show me all open orders from today"
  • "Get full details for order ID abc123 including line items and payments"
  • "Create a new order for table 5 with two burgers and a soda"

Inventory Operations:

  • "List all menu items in my inventory"
  • "Check current stock levels for item xyz789"
  • "Show me all items that are running low on inventory"

Customer Intelligence:

  • "List all customers with email addresses for marketing"
  • "Find customers who haven't ordered in 60 days"
  • "Get contact info for customers who ordered yesterday"

Payment Reconciliation:

  • "Show all successful payments from last week"
  • "List declined transactions that need follow-up"
  • "Get payment details for order #12345"

Business Analytics:

  • "Get my merchant settings and business hours"
  • "Combine order data with inventory to show top sellers this month"

🛠️ Development

Prerequisites

  • Node.js 18+
  • npm or yarn
  • Clover merchant account with API access

Setup

git clone https://github.com/BusyBee3333/Clover-MCP-2026-Complete.git
cd clover-mcp-2026-complete
npm install
cp .env.example .env
# Edit .env with your Clover credentials
npm run build
npm start

Testing

npm test                  # Run all tests
npm run test:watch        # Watch mode
npm run test:coverage     # Coverage report

🐛 Troubleshooting

"Authentication failed"

  • Verify your API token is valid and not expired
  • Ensure your Merchant ID is correct (check Clover dashboard)
  • Confirm your API token has the necessary permissions (read/write orders, inventory, etc.)

"Wrong region error"

  • Check your CLOVER_REGION setting matches your account region
  • US accounts use https://api.clover.com
  • EU accounts use https://api.eu.clover.com
  • LATAM accounts use https://api.la.clover.com

"Tools not appearing in Claude"

  • Restart Claude Desktop after updating config
  • Check that the path in claude_desktop_config.json is absolute
  • Verify the build completed successfully (dist/index.js exists)

📖 Resources

🤝 Contributing

Contributions are welcome! Please:

  1. Fork the repo
  2. Create a feature branch (git checkout -b feature/amazing-tool)
  3. Commit your changes (git commit -m 'Add amazing tool')
  4. Push to the branch (git push origin feature/amazing-tool)
  5. Open a Pull Request

📄 License

MIT License - see LICENSE for details

🙏 Credits

Built by MCPEngage — AI infrastructure for business software.

Want more MCP servers? Check out our full catalog covering 30+ business platforms.


Questions? Open an issue or join our Discord community.