MioCommerce API and MCP server Let your AI agent book, quote and invoice the job.

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
MioCommerce logo MioCommerce Cloud Browser

22 tools Read and write

Home service office work

What can your AI agent do in MioCommerce? The office work between a customer's call and a paid invoice.

  • 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

No public API, no MCP

Does MioCommerce have an MCP server or an API? The official MioCommerce routes, checked 14 November 2026.

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.

  • 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.
MioCommerce on its own, MioAssistant and Cotlet compared
What you need MioCommerce aloneMioAssistantCotlet
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

Set up once

How does the MioCommerce MCP server work? The MioCommerce MCP server by Cotlet: your agent works in your own MioCommerce account.

  1. 1Sign in to MioCommerce

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand 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. Who can see your session

Any MCP client

How to connect MioCommerce to your AI agent

  1. 1

    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.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    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
2 read, 20 write

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 requests3

Customer profiles, CSV imports and exports, and the service requests that come before a quote.

  • manage_customers List, read, create or edit a customer profile under Customers. writeAsks first

    Follows Customers > Create Customer. Add the customer first, then create_booking, generate_invoice or charge_customer can use the profile. Run `list` first so the same household is not added twice. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → manage_customers

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/customers/manage

    Parameters

    Parameters: manage_customers
    NameTypeDescription
    action string required string One of `list`, `get`, `create`, `update`. `list`, `get` and `export` only read.
    customer string string Customer name or email, for `get` and `update`.
    fields object object For `create` and `update`: email, first_name, last_name and address (required to create), plus billing_email, language, notify_by (`email`, `sms` or both) and payment_option (cash, check, credit card, debit card, e-check and the other options MioCommerce lists).

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "customer": "Example Homeowner",
      "email": "homeowner@example.com",
      "notify_by": [
        "email",
        "sms"
      ],
      "payment_option": "credit card",
      "saved": true
    }
  • import_export_customers Export the customer list, or import customers from a CSV file. writeAsks first

    Leave Customer No empty for new customers and MioCommerce generates one. State and country must be written out (New York, United States), as the Help Center asks. `export` only reads. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → import_export_customers

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/export-customers

    Parameters

    Parameters: import_export_customers
    NameTypeDescription
    action string required string One of `export`, `import`. `list`, `get` and `export` only read.
    format string string For `export`: one of the formats MioCommerce offers, for example `csv`.
    file_url string string For `import`: a link to a CSV file in the MioCommerce customer layout. Email address, first name and last name are required columns.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "action": "import",
      "rows": 3,
      "imported": 3
    }
  • manage_service_requests Create or edit a service request for a customer or a new prospect. writeAsks first

    Once saved, a request can be edited except for its email and service type. Turn it into a quote with create_quick_quote or create_advanced_quote. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → manage_service_requests

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/service-requests/manage

    Parameters

    Parameters: manage_service_requests
    NameTypeDescription
    action string required string One of `list`, `get`, `create`, `update`. `list`, `get` and `export` only read.
    request string string Service request number, for `get` and `update`.
    contact object object For a new prospect: email, first_name, last_name, phone. For an existing customer, email is enough.
    service_page string string A Service Request Page to start from, or leave empty for a custom request.
    details object object Service location, service options, extras, notes.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "request": "SR-311",
      "contact": "prospect@example.com",
      "service": "Home cleaning",
      "status": "new",
      "saved": true
    }

Bookings and dispatching5

Call-in bookings, new times, provider assignments and cancellations. A cancelled booking cannot be restored.

  • list_bookings List bookings from the Bookings page, or open one Booking Profile. read

    Returns the bookings your user can see with customer, service, date, status and amount. Most other tools take a booking, so this is usually the first call. Nothing is changed, so it runs without asking.

    MCP callmiocommerce_read → list_bookings

    REST endpointGET https://cotlet.dev/api/v1/miocommerce/bookings

    Parameters

    Parameters: list_bookings
    NameTypeDescription
    status string string Filter by the status MioCommerce shows, for example `call-in`, `unscheduled`, `scheduled`, `dispatched` or `complete`. Leave empty for all.
    from string string ISO date, first day to include.
    to string string ISO date, last day to include.
    booking string string Booking number, to open one Booking Profile instead of the list.

    Example response

    {
      "bookings": [
        {
          "booking": "B-1042",
          "customer": "Example Homeowner",
          "service": "Deep clean",
          "date": "2026-11-18",
          "status": "complete",
          "amount": 285
        },
        {
          "booking": "B-1043",
          "customer": "Sample Rentals",
          "service": "Move out clean",
          "date": "2026-11-19",
          "status": "scheduled",
          "amount": 410
        }
      ]
    }
  • create_booking Create an internal (call-in) booking on the Calendar. writeAsks first

    The booking follows your operating hours, service availability and provider capacity. If it overlaps another booking, MioCommerce flags the double booking in red, and the agent reports it to you. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → create_booking

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/bookings

    Parameters

    Parameters: create_booking
    NameTypeDescription
    customer string required string Customer from manage_customers.
    service string required string The service as named in your account.
    start string required string ISO date and time.
    end string string ISO date and time. Defaults to the service length.
    price number number Price, if it differs from the service price.

    Example input

    {
      "customer": "customer",
      "service": "service",
      "start": "start"
    }

    Example response

    {
      "booking": "B-1044",
      "customer": "Example Homeowner",
      "service": "Standard clean",
      "start": "2026-11-21T09:00",
      "end": "2026-11-21T11:00",
      "status": "call-in",
      "double_booked": false
    }
  • reschedule_booking Move a booking to a new date or time, with an optional notification. writeAsks first

    Rescheduling does not change the assigned service provider. For a recurring booking the agent asks whether to move only this visit or all future ones. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → reschedule_booking

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/booking/reschedule

    Parameters

    Parameters: reschedule_booking
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.
    start string required string New ISO date and time.
    recurring_scope string string For a recurring booking: `this` or `all_future`.
    notify boolean boolean Send the customer and service provider a notification (accounts with Dispatching).

    Example input

    {
      "booking": "booking",
      "start": "start"
    }

    Example response

    {
      "booking": "B-1043",
      "start": "2026-11-20T13:00",
      "recurring_scope": "this",
      "notified": true
    }
  • assign_service_provider Assign a service provider to a booking on the Dispatcher. writeAsks first

    Moving a booking from another provider keeps that provider on it too, as the Dispatcher does; the agent says so before saving. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → assign_service_provider

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/service-provider/assign

    Parameters

    Parameters: assign_service_provider
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.
    provider string required string Service provider as named in your account.
    notify boolean boolean Tell the provider about the new assignment.
    future_recurrences boolean boolean Also assign the provider to all future recurrences of this booking.

    Example input

    {
      "booking": "booking",
      "provider": "provider"
    }

    Example response

    {
      "booking": "B-1044",
      "providers": [
        "Cleaner A"
      ],
      "notified": true,
      "future_recurrences": false
    }
  • cancel_booking Cancel a booking from its Booking Profile. writeAsks first

    A cancelled booking cannot be restored. MioCommerce can clone it to recreate the details, so the agent offers reschedule_booking first when you only need a new time. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → cancel_booking

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/booking/cancel

    Parameters

    Parameters: cancel_booking
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.

    Example input

    {
      "booking": "booking"
    }

    Example response

    {
      "booking": "B-1043",
      "status": "cancelled"
    }

Quotes3

Quick Quotes for a known price, Advanced Quotes from your own pricing pages, and edits before or after sending.

  • create_quick_quote Create a Quick Quote with typed services and prices, and send it or keep it as a draft. writeAsks first

    For a known price. When pricing needs the questions, options and frequencies of a booking page, use create_advanced_quote. The agent shows you lines and total before it sends. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → create_quick_quote

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/quick-quotes

    Parameters

    Parameters: create_quick_quote
    NameTypeDescription
    contact string required string Customer or prospect email.
    service string required string The service the quote is for.
    lines array required array Description and amount per line.
    issued_date string string ISO date. Defaults to today.
    expiration_date string string ISO date the quote is valid until (optional).
    send boolean boolean Send it now. False keeps a draft.

    Example input

    {
      "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
    }

    Example response

    {
      "quote": "Q-208",
      "contact": "prospect@example.com",
      "service": "Deep clean",
      "lines": [
        {
          "description": "Deep clean, three bedrooms",
          "amount": 240
        },
        {
          "description": "Inside oven",
          "amount": 45
        }
      ],
      "total": 285,
      "status": "draft"
    }
  • create_advanced_quote Create an Advanced Quote from a Live Pricing or Interactive Quoting Page. writeAsks first

    Reuses the pricing, options and add-ons you already set up, so the total comes from your own page. Existing customers get their details filled in automatically. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → create_advanced_quote

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/advanced-quotes

    Parameters

    Parameters: create_advanced_quote
    NameTypeDescription
    contact string required string Customer or prospect email; only the email is required for a prospect.
    page string string Live Pricing & Real-Time Booking Page or Interactive Quoting Page to reuse.
    answers object object Options, extras and frequency, as the page asks for them.
    notes string string Notes for the customer.

    Example input

    {
      "contact": "contact"
    }

    Example response

    {
      "quote": "Q-209",
      "contact": "homeowner@example.com",
      "page": "Home cleaning",
      "frequency": "every two weeks",
      "total": 160,
      "status": "draft"
    }
  • edit_quote Edit a draft or sent quote: lines, extras, discounts, frequency or terms. writeAsks first

    An existing customer's contact details change on the customer profile, not on the quote. A quote that was already sent has to be sent again to reach the customer. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → edit_quote

    REST endpointPATCH https://cotlet.dev/api/v1/miocommerce/quote

    Parameters

    Parameters: edit_quote
    NameTypeDescription
    quote string required string Quote number.
    changes object required object Prospect contact details, service location, custom lines, extras, discounts, frequency options or terms.

    Example input

    {
      "quote": "quote",
      "changes": "changes"
    }

    Example response

    {
      "quote": "Q-208",
      "total": 265,
      "discount": 20,
      "status": "draft",
      "saved": true
    }

Invoices and payments6

Invoices from bookings, Stripe payment links, MioPay charges, cash and cheque collections, and card refunds.

  • generate_invoice Generate an invoice from a booking, then send it or save a draft. writeAsks first

    The invoice takes booking number, service, billing address, date, amount and taxes from the booking, and your company Terms & Conditions from Settings > Invoicing. Fix the booking first if a price is wrong. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → generate_invoice

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/invoice/generate

    Parameters

    Parameters: generate_invoice
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.
    extra_recipients array array More email addresses to send the invoice to.
    note string string Personal note, for example "Thank you for your business."
    send boolean boolean Send it now. False saves a draft under Payments > Invoices.

    Example input

    {
      "booking": "booking"
    }

    Example response

    {
      "invoice": "INV-5521",
      "booking": "B-1042",
      "customer": "Example Homeowner",
      "total": 285,
      "status": "draft"
    }
  • edit_invoice Change an invoice's email recipients or personal note. writeAsks first

    Service, price and taxes change on the booking; billing address on the customer profile. Editing does not collect or refund money, and an invoice that was already sent must be sent again. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → edit_invoice

    REST endpointPATCH https://cotlet.dev/api/v1/miocommerce/invoice

    Parameters

    Parameters: edit_invoice
    NameTypeDescription
    invoice string required string Invoice number.
    recipients array array Email addresses to send to.
    note string string Personal note on the invoice.

    Example input

    {
      "invoice": "invoice"
    }

    Example response

    {
      "invoice": "INV-5521",
      "recipients": [
        "homeowner@example.com",
        "accounts@example.com"
      ],
      "saved": true
    }
  • charge_customer Charge a booking with MioPay: the full amount, part of it, or a pre-authorized amount. writeAsks first

    For accounts connected to Stripe through MioPay. This moves the customer's money, so the agent shows booking, card and amount before charging. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → charge_customer

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/customer/charge

    Parameters

    Parameters: charge_customer
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.
    amount number required number Amount to charge.
    capture boolean boolean Capture the pre-authorized amount instead of a new charge.

    Example input

    {
      "booking": "booking",
      "amount": 1
    }

    Example response

    {
      "booking": "B-1042",
      "amount": 285,
      "method": "MioPay",
      "status": "paid"
    }
  • record_collection Mark a booking as paid when the customer paid outside MioCommerce. writeAsks first

    Records the payment so the balance shows zero. No card is charged and Stripe handles no money. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → record_collection

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/collections

    Parameters

    Parameters: record_collection
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.
    method string required string One of the collection methods MioCommerce lists: Cash, Cheque, Interac e-Transfer, eCheck, PAD, PayPal (External), Square (External), Venmo, Zelle (External), Coupon, IMS, ITEX or None.
    amount number required number Amount received.

    Example input

    {
      "booking": "booking",
      "method": "method",
      "amount": 1
    }

    Example response

    {
      "booking": "B-1045",
      "method": "Cash",
      "amount": 160,
      "balance": 0
    }
  • refund_card_payment Refund all or part of a MioPay card payment from Payments. writeAsks first

    Only for card payments through MioPay (Stripe). The status turns Refunded at once; customers usually see the money in 5 to 10 business days. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → refund_card_payment

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/card-payment/refund

    Parameters

    Parameters: refund_card_payment
    NameTypeDescription
    payment string required string Payment as listed under Payments.
    amount number required number Refund amount, full or partial.

    Example input

    {
      "payment": "payment",
      "amount": 1
    }

    Example response

    {
      "payment": "P-9031",
      "amount": 45,
      "status": "Refunded"
    }

Feedback2

Request service feedback for a booking and read what customers answered. Feedback stays private in MioCommerce.

  • request_service_feedback Send a customer the service feedback request for one booking. writeAsks first

    Goes by email, SMS or both, following the customer's notification settings. It works at any booking status. Answers stay private in MioCommerce; read them with view_customer_feedback. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → request_service_feedback

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/service-feedback/request

    Parameters

    Parameters: request_service_feedback
    NameTypeDescription
    booking string required string Booking number or customer name, as list_bookings returns it.

    Example input

    {
      "booking": "booking"
    }

    Example response

    {
      "booking": "B-1042",
      "sent_by": [
        "email"
      ],
      "sent": true
    }
  • view_customer_feedback Read service feedback from CRM > Feedback, one customer or one booking. read

    Returns the feedback with its date and booking. MioCommerce keeps it inside your account and does not publish it. Read only, it runs without asking.

    MCP callmiocommerce_read → view_customer_feedback

    REST endpointGET https://cotlet.dev/api/v1/miocommerce/customer-feedbacks/view

    Parameters

    Parameters: view_customer_feedback
    NameTypeDescription
    customer string string Customer name or email. Leave empty for all customers.
    booking string string Booking number, for the feedback on one service.

    Example response

    {
      "feedback": [
        {
          "customer": "Example Homeowner",
          "booking": "B-1042",
          "date": "2026-11-19",
          "comment": "Kitchen looked brand new, thank you."
        }
      ]
    }

Booking pages and your team3

Live Pricing & Real-Time Booking Pages, extra schedule emails for providers, and non-working hours.

  • manage_booking_pages List, create or edit a Live Pricing & Real-Time Booking Page. writeAsks first

    Every page needs a name, a service and a personal information section. Customers book and pay on these pages, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → manage_booking_pages

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/booking-pages/manage

    Parameters

    Parameters: manage_booking_pages
    NameTypeDescription
    action string required string One of `list`, `get`, `create`, `update`. `list`, `get` and `export` only read.
    page string string Booking page name, for `get` and `update`.
    template string string For `create`: a MioCommerce template by service category, or empty to build from scratch.
    sections object object Service, personal information, location, date, options, extras, frequency and payment sections.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "page": "Home cleaning",
      "template": "Cleaning",
      "sections": [
        "Service",
        "Personal information",
        "Location",
        "Date",
        "Options",
        "Extras",
        "Frequency"
      ],
      "saved": true
    }
  • send_provider_schedule Email a service provider today's, this week's or next week's schedule. writeAsks first

    Providers already get their daily schedule at 5 AM in your company time zone; this sends an extra one on demand. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → send_provider_schedule

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/provider-schedules

    Parameters

    Parameters: send_provider_schedule
    NameTypeDescription
    provider string required string Service provider as named in your account.
    period string required string `today`, `this_week` or `next_week`.

    Example input

    {
      "provider": "provider",
      "period": "period"
    }

    Example response

    {
      "provider": "Cleaner A",
      "period": "next_week",
      "sent": true
    }
  • add_non_working_hours Block time on a service provider's Work Calendar. writeAsks first

    Non-working hours override availability, so customers cannot book that time. Bookings already in the slot stay; list_bookings shows them so you can move them. By default you confirm each call; you can switch that off for this tool.

    MCP callmiocommerce_write → add_non_working_hours

    REST endpointPOST https://cotlet.dev/api/v1/miocommerce/non-working-hours

    Parameters

    Parameters: add_non_working_hours
    NameTypeDescription
    provider string required string Service provider as named in your account.
    start string required string ISO date and time.
    end string required string ISO date and time.

    Example input

    {
      "provider": "provider",
      "start": "start",
      "end": "end"
    }

    Example response

    {
      "provider": "Cleaner A",
      "start": "2026-11-24T00:00",
      "end": "2026-11-28T23:59",
      "saved": true
    }
Encrypted, revocable

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).

We keep it working

What happens when MioCommerce changes? The tools use the same Ops Console screens your office uses.

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.

20 tools ask first

Approvals, undo and mistakes Customers and providers hear nothing, and no card is charged, until you say so.

  1. 01 Read the request manage_service_requests opens what the prospect asked for.
  2. 02 Draft the quote Lines and total, shown to you first.
  3. 03 Save after your OK create_quick_quote keeps it as a draft.
  4. 04 Send when you say A second OK sends it to the prospect.
Fixing a MioCommerce write that went wrong
ActionHow to put it right
Booking time or providerCall reschedule_booking or assign_service_provider again with the earlier values
Quote or invoice detailsEdit with edit_quote or edit_invoice; a sent one must be sent again
Cancelled bookingCannot be restored; clone it in MioCommerce to recreate the details
Card chargerefund_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.

Pay per call

How much does the MioCommerce MCP server cost?

About $28 a monthfor a cleaning company with a small crew, 4,780 credits. Your MioCommerce plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Call-in bookings with a provider assigned3 × 401,200
Quotes for new service requests2 × 20400
Evening invoices with payment links3 × 20600
Cash and cheque collections2 × 20400
Feedback requests after each service1 × 40400
Reschedules and provider schedules2 × 12240
Friday feedback review1 × 440
Cloud Browser, 30 days1,500
Total328 calls4,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.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Other options

MioCommerce MCP server: other ways to connect What each route does for a home service office, and where it stops.

Other ways to work with MioCommerce, checked 14 Nov 2026
OptionWhat it doesWhere it stops
MioAssistantMioCommerce's own automations, such as Service Feedback Automation.Runs inside MioCommerce; no ChatGPT or Claude connector was verified.
MioCommerce integrationsThe 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 handOpen 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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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.

Hand your next MioCommerce quote to your agent.

Free 7-day trial with 2,000 credits, no card needed.