Skip to main content
Glama
README.md
# MioCommerce MCP server

Connect MioCommerce to ChatGPT, Claude and any AI agent through Cotlet.dev. Manage customers, bookings, quotes, invoices and feedback in your own signed-in MioCommerce account. Write actions ask for approval by default.

## What you can ask

> List today's bookings and their assigned service providers.

> Draft a quote for a three-bedroom deep clean and show me before sending.

> Read customer feedback for last week.

## Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.

### ChatGPT

Settings → Apps & Connectors → Create, with connector URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev. No API key needed.

### Claude

Settings → Connectors → Add custom connector, with URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev.

### Claude Code

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

### Cursor

Copy `.cursor/mcp.json` from this repo into your project:

```json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

## Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its MioCommerce tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

Run the included Python module with Python 3.10 or later:

```bash
python3 miocommerce_agent.py serve
```

Or with Docker:

```bash
docker build -t miocommerce-mcp .
docker run -i --rm -e COTLET_API_KEY miocommerce-mcp
```

Tools: `miocommerce_guide`, `miocommerce_status`, `miocommerce_open`, `miocommerce_read`, `miocommerce_click`, `miocommerce_type`, `miocommerce_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

## Command line

Python 3.10+, with no third-party runtime dependencies. Clone this repository and run:

```bash
export COTLET_API_KEY="your-key"
python3 miocommerce_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 miocommerce_agent.py status    # is MioCommerce ready in your Cotlet.dev account
python3 miocommerce_agent.py guide     # MioCommerce screens and sign-in link
python3 miocommerce_agent.py read      # open MioCommerce, read the page, close the browser
python3 miocommerce_agent.py tools     # list Cotlet.dev tools
python3 miocommerce_agent.py serve     # start the stdio MCP server (same as no argument)
```

## Questions from MioCommerce users

**Which MioCommerce user should I connect?**

Sign in with an administrator whose work the agent should do. The agent sees what that user can see in MioCommerce.

**Do I need Stripe connected?**

Card charges, refunds and invoice payment links need MioPay connected to Stripe in MioCommerce. Cash and cheque collections use record_collection.

**Is Cotlet affiliated with MioCommerce?**

No. Cotlet.dev is independent and not affiliated with MioCommerce.

## Learn more

- [MioCommerce integration and hosted tools](https://cotlet.dev/integrations/miocommerce-api-mcp-server)

---

More: https://cotlet.dev/integrations/miocommerce-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=miocommerce

Request access: https://cotlet.dev/signup?app=miocommerce&utm_source=github&utm_medium=readme&utm_campaign=miocommerce

## Workflows on the hosted integration

The live integration page documents these 22 operations:

- `manage_customers`
- `import_export_customers`
- `manage_service_requests`
- `list_bookings`
- `create_booking`
- `reschedule_booking`
- `assign_service_provider`
- `cancel_booking`
- `create_quick_quote`
- `create_advanced_quote`
- `edit_quote`
- `generate_invoice`
- `edit_invoice`
- `add_invoice_payment_link`
- `charge_customer`
- `record_collection`
- `refund_card_payment`
- `request_service_feedback`
- `view_customer_feedback`
- `manage_booking_pages`
- `send_provider_schedule`
- `add_non_working_hours`

The local stdio adapter exposes seven browser helpers listed above. These helpers forward to Cotlet.dev; the workflow operations are documented on the hosted integration page.

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct role: status checks readiness, guide explains the workflow, open/read/click/type/close are standard browser primitives. The only mild overlap is status vs guide, both being 'orientation' tools with 'call this first' style guidance, but their descriptions distinguish them adequately.

Naming Consistency5/5

Every tool uses the same miocommerce_ prefix followed by a single, action-oriented verb (status, guide, open, read, click, type, close). The pattern is uniform and immediately readable.

Tool Count5/5

Seven tools is well-scoped for a browser-bridge server: two setup/orientation tools plus five minimal interaction primitives. No tool feels redundant or extraneous.

Completeness3/5

The surface covers open/read/click/type/close but lacks common browser operations: scrolling on long pages, navigating to a specific URL or going back, and selecting from dropdowns. These gaps will likely cause dead ends on real booking/invoice workflows that require scrolling or form selection.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues