MioCommerce MCP Server
Bookings, quotes, invoices, payments and feedback in MioCommerce.
ホスト型 MCP サーバー
npx add-mcp 'https://cotlet.dev/mcp/v1/miocommerce'Claude Code、Codex、Cursor などにインストールできます
ドキュメント
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
MioCommerce API and MCP server: Let your AI agent book, quote and invoice the job.
MioCommerce publishes no public API: its website, integrations page and Help Center document no developer API or self-serve key. No MioCommerce MCP server and no official ChatGPT or Claude connector was verified.
MioCommerce publishes no public API and no MCP server (checked 14 Nov 2026). Cotlet runs a hosted MioCommerce MCP server with 22 tools that ChatGPT and Claude use in your own MioCommerce account. Charges, refunds and anything that reaches a customer or a provider wait for your OK.
- Free 7-day trial, no card
- Unofficial, not affiliated with MioCommerce
- Page: https://cotlet.dev/integrations/miocommerce-api-mcp-server
What can your AI agent do in MioCommerce?
- Book a call-in and assign a provider
- Turn a service request into a quote
- Invoice completed bookings with a payment link
- Mark cash and cheque bookings as paid
- Ask for feedback after each service
- Block time off and move the bookings in it
Does MioCommerce have an MCP server or an API?
- MioAssistant is MioCommerce's own automation feature, for example Service Feedback Automation.
- Card charges, refunds and invoice payment links run through MioPay, which needs Stripe connected in MioCommerce.
- Service providers get their daily schedule by email at 5 AM in your company time zone.
| What you need | MioCommerce alone | MioAssistant | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No API or MCP server | Inside MioCommerce only | Hosted MCP server |
| Bookings, quotes and invoices on request | By hand, screen by screen | Its own automations | 22 tools, writes after your OK |
| Collections and refunds | By hand | Not documented | Asks before money moves |
| Run from n8n or a script | No public API | No | REST, same key |
Checked 14 Nov 2026. Sources: MioCommerce website, MioCommerce integrations, MioCommerce Help Center, Help: MioAssistant Automations Overview, Help: How to add a new Customer, Help: Import and export customers, Help: Create a Booking from the Calendar, Help: Reschedule a booking, Help: Assign a service provider, Help: Cancel a booking, Help: Create a Service Request, Help: Edit a Service Request, Help: Create a Quick Quote, Help: Create an Advanced Quote, Help: Edit a Quote, Help: Generate and send an invoice, Help: Edit the invoice, Help: Add a Payment Link to an Invoice, Help: Charge a customer for a booking, Help: Mark a booking as paid, Help: Refund a card payment, Help: Request feedback, Help: See customer feedback, Help: Create a booking page, Help: Edit a booking page, Help: Send a provider their schedule, Help: Add non-working hours
How does the MioCommerce MCP server work?
- Sign in to MioCommerce. Once, in a browser we host for you.
- Connect your AI agent. One address in its settings.
- Hand it the front desk. Draft a quote, then approve it before it goes out.
Your agent works in your own signed-in Cloud Browser. Charges, refunds and messages to customers or providers wait for your OK.
How to connect MioCommerce to your AI agent
- Sign in to MioCommerce in a Cloud Browser. Open signin.miocommerce.com in your Cotlet Cloud Browser and sign in with your own MioCommerce admin user.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
- Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
MioCommerce uses the shared address https://cotlet.dev/mcp/v1 together with every other app you enable, so one connector serves them all. Switched MioCommerce on after connecting? Refresh the connector and the 22 MioCommerce tools show up.
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: miocommerce_read
All 22 MioCommerce MCP tools
One tool per workflow in the MioCommerce Help Center. Bookings and feedback read at once; every tool that saves, sends or moves money asks first.
Customers and service requests
Customer profiles, CSV imports and exports, and the service requests that come before a quote.
- Add customers (
manage_customers, write, asks first): List, read, create or edit a customer profile under Customers. - Import and export customers (
import_export_customers, write, asks first): Export the customer list, or import customers from a CSV file. - Create service requests (
manage_service_requests, write, asks first): Create or edit a service request for a customer or a new prospect.
Bookings and dispatching
Call-in bookings, new times, provider assignments and cancellations. A cancelled booking cannot be restored.
- List bookings (
list_bookings, read): List bookings from the Bookings page, or open one Booking Profile. - Create bookings (
create_booking, write, asks first): Create an internal (call-in) booking on the Calendar. - Reschedule bookings (
reschedule_booking, write, asks first): Move a booking to a new date or time, with an optional notification. - Assign service providers (
assign_service_provider, write, asks first): Assign a service provider to a booking on the Dispatcher. - Cancel bookings (
cancel_booking, write, asks first): Cancel a booking from its Booking Profile.
Quotes
Quick Quotes for a known price, Advanced Quotes from your own pricing pages, and edits before or after sending.
- Create quick quotes (
create_quick_quote, write, asks first): Create a Quick Quote with typed services and prices, and send it or keep it as a draft. - Create advanced quotes (
create_advanced_quote, write, asks first): Create an Advanced Quote from a Live Pricing or Interactive Quoting Page. - Edit quotes (
edit_quote, write, asks first): Edit a draft or sent quote: lines, extras, discounts, frequency or terms.
Invoices and payments
Invoices from bookings, Stripe payment links, MioPay charges, cash and cheque collections, and card refunds.
- Generate and send invoices (
generate_invoice, write, asks first): Generate an invoice from a booking, then send it or save a draft. - Edit invoices (
edit_invoice, write, asks first): Change an invoice's email recipients or personal note. - Add payment links to invoices (
add_invoice_payment_link, write, asks first): Add a Stripe payment link to a saved invoice. - Charge customers (
charge_customer, write, asks first): Charge a booking with MioPay: the full amount, part of it, or a pre-authorized amount. - Record cash and cheque payments (
record_collection, write, asks first): Mark a booking as paid when the customer paid outside MioCommerce. - Refund card payments (
refund_card_payment, write, asks first): Refund all or part of a MioPay card payment from Payments.
Feedback
Request service feedback for a booking and read what customers answered. Feedback stays private in MioCommerce.
- Request service feedback (
request_service_feedback, write, asks first): Send a customer the service feedback request for one booking. - View customer feedback (
view_customer_feedback, read): Read service feedback from CRM > Feedback, one customer or one booking.
Booking pages and your team
Live Pricing & Real-Time Booking Pages, extra schedule emails for providers, and non-working hours.
- Create and edit booking pages (
manage_booking_pages, write, asks first): List, create or edit a Live Pricing & Real-Time Booking Page. - Send service provider schedules (
send_provider_schedule, write, asks first): Email a service provider today's, this week's or next week's schedule. - Add non-working hours (
add_non_working_hours, write, asks first): Block time on a service provider's Work Calendar.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/miocommerce-api-mcp-server#tools
Who can see my MioCommerce session, and how do I revoke it?
- What we store. Your signed-in MioCommerce browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- What your agent gets. The 22 MioCommerce tools. The session cookie stays in the Cloud Browser.
- What the session sees. The customers, bookings, quotes and payments your MioCommerce user can open, and nothing more.
- What no tool touches. Your Stripe connection, MioAssistant automations, Terms & Conditions under Settings and your MioCommerce plan.
- If MioCommerce signs you out. You sign in again yourself, in the same Cloud Browser.
- How to cut access. Disable MioCommerce for agents, reset the browser, or change your MioCommerce password.
You type your MioCommerce password yourself; the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
What happens when MioCommerce changes?
Cotlet watches the apps it serves and updates the MioCommerce server when MioCommerce changes its screens, so your agent keeps booking and invoicing without a change on your side.
New MioCommerce features become available to the agent. It still sees only what your own MioCommerce user can see.
Cotlet never sees or stores your password. If MioCommerce signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
Approvals, undo and mistakes
- Read the request. manage_service_requests opens what the prospect asked for.
- Draft the quote. Lines and total, shown to you first.
- Save after your OK. create_quick_quote keeps it as a draft.
- Send when you say. A second OK sends it to the prospect.
| Action | How to put it right |
|---|---|
| Booking time or provider | Call reschedule_booking or assign_service_provider again with the earlier values |
| Quote or invoice details | Edit with edit_quote or edit_invoice; a sent one must be sent again |
| Cancelled booking | Cannot be restored; clone it in MioCommerce to recreate the details |
| Card charge | refund_card_payment, full or partial; the customer sees it in 5 to 10 business days |
All 20 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 2 read tools, bookings and feedback, run at once.
MCP call:
{
"name": "create_quick_quote",
"arguments": {
"contact": "prospect@example.com",
"service": "Deep clean",
"lines": [
{
"description": "Deep clean, three bedrooms",
"amount": 240
},
{
"description": "Inside oven",
"amount": 45
}
],
"expiration_date": "2026-11-28",
"send": false
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/miocommerce/quick-quotes \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"contact":"prospect@example.com","service":"Deep clean","lines":[{"description":"Deep clean, three bedrooms","amount":240},{"description":"Inside oven","amount":45}],"expiration_date":"2026-11-28","send":false}'
Response:
{
"quote": "Q-208",
"contact": "prospect@example.com",
"service": "Deep clean",
"lines": 2,
"total": 285,
"expiration_date": "2026-11-28",
"status": "draft"
}
The example drafts a $285 quote, $240 for a three-bedroom deep clean and $45 inside the oven, and keeps it unsent. A cron job or n8n flow can make the same call over REST at /api/v1/miocommerce with the same key and price, in JSON. Failed calls are free.
How much does the MioCommerce MCP server cost?
About $28 a month for a cleaning company with a small crew, 4,780 credits. Your MioCommerce plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Call-in bookings with a provider assigned | 3 × 40 | 1,200 |
| Quotes for new service requests | 2 × 20 | 400 |
| Evening invoices with payment links | 3 × 20 | 600 |
| Cash and cheque collections | 2 × 20 | 400 |
| Feedback requests after each service | 1 × 40 | 400 |
| Reschedules and provider schedules | 2 × 12 | 240 |
| Friday feedback review | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 328 calls | 4,780 |
The smallest pack, 5,000 credits for $29, covers this month. More crews and more bookings use more calls.
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your MioCommerce plan and Stripe fees apply as they are
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
MioCommerce MCP server: other ways to connect
| Option | What it does | Where it stops |
|---|---|---|
| MioAssistant | MioCommerce's own automations, such as Service Feedback Automation. | Runs inside MioCommerce; no ChatGPT or Claude connector was verified. |
| MioCommerce integrations | The connections MioCommerce lists on its integrations page, and MioPay on Stripe for card payments. | No public API or developer key for your own code. |
| By hand | Open each booking, quote and invoice in the Ops Console. | One screen at a time, only while you are at the desk. |
If MioAssistant already runs the job you need, keep it: it is MioCommerce's own tool. Cotlet fits when you want ChatGPT, Claude or a script doing MioCommerce work on request or on a schedule, from your own login, with nothing to host.
Who runs Cotlet
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the MioCommerce tools.
MioCommerce MCP server: questions
How do I get access?
Sign up free at https://cotlet.dev/signup?app=miocommerce, turn on MioCommerce under Integrations in the console and sign in at https://signin.miocommerce.com/signin in your Cloud Browser. Then connect your AI agent and ask it to check today's bookings. The trial needs no card.
Does MioCommerce have an API?
MioCommerce publishes no public API: its website, integrations page and Help Center document no developer API or self-serve key (checked 14 Nov 2026). No MioCommerce MCP server and no official ChatGPT or Claude connector was verified; MioAssistant is MioCommerce's own automation feature. Cotlet does not need one: it works in your own signed-in MioCommerce account.
How is this different from MioAssistant?
MioAssistant is MioCommerce's own automation feature, for example Service Feedback Automation, documented in its Help Center. Cotlet is separate: it lets ChatGPT, Claude or a script you choose do MioCommerce work over MCP or REST.
Do I need Stripe connected?
Only for card work. charge_customer, refund_card_payment and add_invoice_payment_link need MioPay, which runs on Stripe and is connected in MioCommerce itself. Cash, cheque and other collections work without it through record_collection. No Cotlet tool changes your Stripe connection.
Which MioCommerce user should I sign in with?
An administrator whose work the agent should do. Tools such as add_non_working_hours and assign_service_provider follow the Help Center steps written for administrators, and the agent sees only what that user can see.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 22 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
Is Cotlet affiliated with MioCommerce?
No. Cotlet is independent and not affiliated with MioCommerce.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.