MioCommerce MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MioCommerce MCP Server List today's bookings and their assigned service providers."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: Zenoti MCP Server
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
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:
{
"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:
python3 miocommerce_agent.py serveOr with Docker:
docker build -t miocommerce-mcp .
docker run -i --rm -e COTLET_API_KEY miocommerce-mcpTools: 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:
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
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_customersimport_export_customersmanage_service_requestslist_bookingscreate_bookingreschedule_bookingassign_service_providercancel_bookingcreate_quick_quotecreate_advanced_quoteedit_quotegenerate_invoiceedit_invoiceadd_invoice_payment_linkcharge_customerrecord_collectionrefund_card_paymentrequest_service_feedbackview_customer_feedbackmanage_booking_pagessend_provider_scheduleadd_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.
Available Tools
7 toolsmiocommerce_clickB
Click a numbered element on the current MioCommerce page.
Inputs: element (required).
miocommerce_closeA
Close the MioCommerce browser session when the work is done, so credits stop running.
Inputs: no named parameters.
miocommerce_guideA
How to work in MioCommerce (customers, bookings, quotes, invoices and service provider schedules): its screens and the sign-in link. Call this first.
Inputs: task.
miocommerce_openA
Open a MioCommerce page in your signed-in Cloud Browser (default https://signin.miocommerce.com) to work with customers, bookings, quotes, invoices and service provider schedules.
Inputs: url.
miocommerce_readA
Read the current MioCommerce page: its text and numbered buttons, links and fields.
Inputs: element.
miocommerce_statusB
Check that your Cotlet.dev account and MioCommerce are ready: account, credits and MioCommerce connection.
Inputs: no named parameters.
miocommerce_typeC
Type text into a numbered field on the current MioCommerce page.
Inputs: text (required), element (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
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.
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.
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.
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
Related MCP Connectors
Connect AI to store orders, products and inventory with scoped access and human approvals.
Connect ChatGPT and Claude to Fortnox: invoices, customers, reports. Every write needs your OK.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect your First AI Employee workspace to review authorized business records, including contacts, tasks, calls, bookings, forms and reports. Prepare supported changes as an exact preview for approval before applying them. OAuth sign-in is required; available tools depend on account permissions, enabled products and access. Website: https://firstaiemployee.com/ . Setup: https://developer.firstaiemployee.com/mcp/
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to draft estimates, schedule jobs, assign crew members, and review receivables in a user's signed-in business account, requiring approval before actions reach other people.7Elastic 2.0
- AlicenseAqualityBmaintenanceConnects ChatGPT, Claude, and other AI agents to a signed-in Zenoti account so they can work with appointments, guest conversations, reviews, and reports. Write operations require approval by default.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceConnects a signed-in Trusso account to ChatGPT, Claude, and other AI agents so users can read jobs and crews, draft estimates, schedule work, and manage invoices, with write actions requiring approval by default.Elastic 2.0
- AlicenseAqualityCmaintenanceConnects a signed-in Treatwell Connect account to ChatGPT, Claude, and other AI agents so users can review bookings, fill rate, offers, salon diary, and reports, with write actions requiring approval by default.7Elastic 2.0