Local services & SaaS
ZenMaid
Appointments, cleaners and customers for your ZenMaid business.
13 endpoints
CleanManager publishes no API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted CleanManager MCP server with 29 tools that ChatGPT and Claude use in your own administrator or supervisor login. Calendar changes, messages and anything that touches wages wait for your OK.
29 tools Read and write
CleanManager publishes no developer API: its guide articles document integrations with accounting systems and CSV file import, and cleanmanager.com/api returns only a backend error. No CleanManager MCP server and no official ChatGPT or Claude connector was found.
| What you need | CleanManager integrations | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about today's rounds | No API or MCP server | Copy and paste | Hosted MCP server |
| Customers, employees and invoices | Synced with accounting | In the web system | 29 tools, writes after your OK |
| Calendar, check-in, plans, reports, storage | Not covered | One screen at a time | Same tools, same key |
| Run from n8n or a script | Nothing to call | Manual only | REST, same key |
Checked 15 Nov 2026. Sources: CleanManager integrations · CleanManager pricing · Guide: Creating a task in the base calendar · Guide: Cancelling a task · Guide: Creating closing days · Guide: Converting tasks to absence hours · Guide: Daily tasks in Check-in · Guide: Check-ins and check-outs · Guide: Active alarms · Guide: Photo documentation · Guide: Creating a customer · Guide: Creating locations · Guide: Customer resources · Guide: Scheduled or used time · Guide: Sorting the view in Invoicing · Guide: Creating an employee · Guide: Employee workplaces · Guide: Wage profiles and hourly wages · Guide: Creating a cleaning plan · Guide: Setting up a report template · Guide: Filling out a report · Guide: Report statistics · Guide: Sending messages · Guide: Ordering and transferring products · Guide: Product requests · Guide: Setting up products
Once, in a browser we host for you.
One address in its settings.
Read the alarms, then approve each change.
Your agent works in your own signed-in Cloud Browser. Calendar changes, messages and wages wait for your OK. Who can see your session
Sign in to CleanManager in a Cloud Browser. Open cleanmanager.com/login in your Cotlet Cloud Browser and sign in with your CleanManager username and password, or with SSO.
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.
CleanManager sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned CleanManager on after connecting? Refresh the connector and the 29 CleanManager tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth 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/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: cleanmanager_read One tool per administrator or supervisor workflow in the CleanManager guide articles. Reads run at once; every write asks first. A supervisor login covers only its customer areas.
Tasks are the basis for wages and invoicing, so the calendar comes first: tasks, cancellations, closing days and absence cover.
Reads Scheduling > Calendar. Cancelled tasks stay in the calendar, faded, and are marked so. Supervisors see only the customers in their assigned customer areas. Read only.
MCP callcleanmanager_read → get_calendar
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/calendar
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to the start date. |
| customer string | string | One customer only. |
| employee string | string | One employee only. |
{
"date": "2026-11-17",
"tasks": [
{
"customer": "Example Offices Ltd",
"location": "Head office",
"employees": [
"Employee A"
],
"start": "06:00",
"end": "08:30",
"status": "scheduled"
}
]
} Tasks are the basis for time registration, wages and invoicing in CleanManager, and they appear in the employee's workday in the app. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → create_task
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/tasks
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as list_customers returns it. |
| location string required | string | A location of the customer. |
| service_agreement string | string | The customer's service agreement, where agreements are in use. |
| employees array | array | Employees to assign. |
| date string required | string | ISO date. |
| start string | string | HH:MM. |
| end string | string | HH:MM. |
{
"customer": "customer",
"location": "location",
"date": "date"
} {
"customer": "Example Offices Ltd",
"location": "Head office",
"date": "2026-11-24",
"start": "06:00",
"end": "08:30",
"employees": [
"Employee A"
],
"created": true
} A cancelled task stays in the calendar, faded out, but leaves payroll, invoicing and the employee's workday. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → cancel_task
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/task/cancel
| Name | Type | Description |
|---|---|---|
| task string required | string | The task, by customer, location and date. |
| which string | string | `just_this_task` (default) or the wider choices the calendar offers. |
| notify string | string | `email` to tell the assigned employees, or leave empty. |
{
"task": "task"
} {
"task": "Example School, Gym hall, 2026-11-20",
"cancelled": true,
"notified": [
"Employee C"
]
} Used for school holidays and office closures. With `cancel_tasks` every task in the period leaves wages and invoicing. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → create_closing_days
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/closing-days
| Name | Type | Description |
|---|---|---|
| customers array required | array | Customers to close. |
| skip_locations array | array | Locations that stay open. |
| from string required | string | ISO date. |
| to string required | string | ISO date. |
| cancel_tasks boolean | boolean | Cancel every task in the period. |
| notify boolean | boolean | Tell the employees about the cancellation. |
{
"customers": "customers",
"from": "from",
"to": "to"
} {
"customers": [
"Example School"
],
"from": "2026-12-21",
"to": "2027-01-01",
"tasks_cancelled": 18,
"notified": true
} Removing the employee from their tasks converts the planned working hours to absence hours, so wages stay right. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → register_absence
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/absences
| Name | Type | Description |
|---|---|---|
| employee string required | string | Who is absent. |
| absence_type string required | string | One of your absence types, for example Sick. |
| from string required | string | ISO date. |
| to string required | string | ISO date. |
| days number | number | Number of absence days; without it the absence shows only in the calendar, not in wages. |
| transfer_to string | string | Employee who takes over the tasks. |
{
"employee": "Employee B",
"absence_type": "Sick",
"from": "2026-11-17",
"to": "2026-11-18",
"days": 2,
"transfer_to": "Employee D"
} {
"employee": "Employee B",
"absence_type": "Sick",
"from": "2026-11-17",
"to": "2026-11-18",
"days": 2,
"tasks_moved": 4,
"transfer_to": "Employee D"
} What happened on site: daily tasks, check-ins by NFC tag or by hand, alarms and photos from the app.
Check-in > Daily tasks shows which tasks employees have started and ended in the app. Supervisors see only the customers in their assigned customer areas. Read only.
MCP callcleanmanager_read → list_daily_tasks
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/daily-tasks
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
{
"date": "2026-11-17",
"not_started": 4,
"in_progress": 3,
"ended": 11,
"comments": [
{
"task": "Example Offices Ltd, Head office",
"text": "Kitchen bin bags running low."
}
]
} Approved hours feed wages and invoicing. A deleted task leaves both. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_daily_task
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/daily-task/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `approve_hours`, `edit`, `delete`. |
| task string required | string | The task, from list_daily_tasks. |
| changes object | object | For `edit`: the new times or employees. |
{
"action": "action",
"task": "task"
} {
"task": "Example Offices Ltd, Head office, 2026-11-17",
"approved_hours": 2.6,
"approved": true
} Shows each check-in and check-out as the employee registered it in the app: manually, with an NFC tag on the server, or offline and synced later. Read only.
MCP callcleanmanager_read → list_check_ins
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/check-ins
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to the start date. |
| employee string | string | One employee only. |
{
"check_ins": [
{
"employee": "Employee A",
"location": "Head office",
"arrival": "05:58",
"departure": "08:34",
"method": "nfc"
},
{
"employee": "Employee B",
"location": "Clinic wing",
"arrival": "06:12",
"method": "manual"
}
]
} Check-in > Active alarms lists every triggered alarm for no check-in or no check-out, so a supervisor sees a missed job before the customer calls. Read only.
MCP callcleanmanager_read → list_active_alarms
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/active-alarms
| Name | Type | Description |
|---|---|---|
| sort_by string | string | One of `customer`, `employee`, `area`, `employee_group`, with `show` naming which one. |
| show string | string | The customer, employee, area or employee group to show. |
{
"alarms": [
{
"type": "no check-in",
"employee": "Employee C",
"customer": "Example School",
"planned_start": "15:00"
}
]
} Photos sync as soon as the employee's phone is online, so they can appear before the task is ended. Supervisors see only the customers in their assigned customer areas. Read only.
MCP callcleanmanager_read → get_photo_documentation
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/photo-documentation
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to the start date. |
| customer string | string | One customer only. |
{
"tasks": [
{
"customer": "Example School",
"location": "Gym hall",
"date": "2026-11-16",
"photos": 3,
"comments": [
"Floor finished, mats stacked."
]
}
]
} Customers, locations, resources and service agreements, and the invoicing view. No tool sends an invoice.
Only the administrator can export CSV; a supervisor gets the list. Supervisors see only the customers in their assigned customer areas. Read only.
MCP callcleanmanager_read → list_customers
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/customers
| Name | Type | Description |
|---|---|---|
| search string | string | Part of a customer name. |
| export string | string | `customers` or `locations` to get the administrator CSV export instead. |
{
"customers": [
{
"name": "Example Offices Ltd",
"type": "Business",
"area": "North",
"locations": 2,
"service_agreements": [
"Weekly office cleaning"
]
}
]
} A location address turns on navigation in the employee app. Supervisors see only the customers in their assigned customer areas. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_customer
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/customer/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `add_location`, `set_products`. |
| customer string required | string | Customer name. |
| fields object | object | For `create` and `update`: type (Business or Private), CI no., area, calendar colour, contact person. |
| location object | object | For `add_location`: name, address, ZIP code, city, country, floor space, name on invoices. |
| products array | array | For `set_products`: the products allowed; empty means all. |
{
"action": "action",
"customer": "customer"
} {
"customer": "Example Offices Ltd",
"location": {
"name": "Warehouse",
"address": "4 Example Road",
"floor_space": 650
},
"saved": true
} Instructions and site documents for a customer live here. Employees see a resource only when you say so. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → add_customer_resource
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/customer-resources
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as list_customers returns it. |
| file_url string | string | A link the Cloud Browser can download: pdf, doc, docx, xls, xlsx, odt, ods, txt, png, gif or jpg. |
| hyperlink string | string | A link to attach instead of a file. |
| name string required | string | Name shown in CleanManager. |
| category string | string | A resource category. |
| employees_can_see boolean | boolean | Show it to employees in the app. |
{
"customer": "customer",
"name": "Jane Doe"
} {
"customer": "Example Offices Ltd",
"resource": "Site map",
"category": "Instructions",
"employees_can_see": true,
"saved": true
} Scheduled time bills the planned hours; used time bills the hours employees actually spent. It changes what the customer pays from then on. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → set_service_agreement_billing
REST endpointPUT https://cotlet.dev/api/v1/cleanmanager/service-agreement-billing
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as list_customers returns it. |
| agreement string required | string | The service agreement. |
| basis string required | string | One of `scheduled_time`, `used_time`. |
{
"customer": "customer",
"agreement": "agreement",
"basis": "basis"
} {
"customer": "Example Offices Ltd",
"agreement": "Weekly office cleaning",
"basis": "used_time",
"saved": true
} Filtering by billing interval keeps an agreement from being invoiced twice. Supervisors see only the customers in their assigned customer areas. Read only: the agent does not send invoices or export them to accounting.
MCP callcleanmanager_read → get_invoicing
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/invoicing
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO date, included. |
| to string required | string | ISO date, included. |
| billing_interval string | string | For example Monthly, so only those agreements show. |
| show string | string | The customer, employee, area or employee group to show. |
{
"from": "from",
"to": "to"
} {
"period": "2026-11-01/2026-11-30",
"billing_interval": "Monthly",
"customers": [
{
"customer": "Example Offices Ltd",
"agreement": "Weekly office cleaning",
"lines": 5,
"amount": 1840
}
]
} Employees, groups, workplaces and wage profiles.
Workplaces are direct (set by hand) or indirect (from tasks in the calendar). Read only.
MCP callcleanmanager_read → list_employees
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/employees
| Name | Type | Description |
|---|---|---|
| search string | string | Part of an employee name. |
| export boolean | boolean | True for the administrator CSV export. |
{
"employees": [
{
"name": "Employee A",
"job_title": "Cleaner",
"group": "Morning team",
"workplaces": {
"direct": [
"Example Offices Ltd"
],
"indirect": [
"Example School"
]
}
}
]
} Giving an employee access sends them into CleanManager with the user type you choose, so the agent shows you the fields first. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_employee
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/employee/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `set_workplaces`, `create_group`. |
| employee string | string | Employee name. |
| fields object | object | Job title, employee group, user type, app access, wage profile and contracted hours. |
| workplaces array | array | For `set_workplaces`: customers the employee is linked to directly. |
| group object | object | For `create_group`: group number and name. Administrator only. |
{
"action": "action"
} {
"employee": "Employee D",
"job_title": "Cleaner",
"group": "Morning team",
"workplaces": [
"Example Offices Ltd"
],
"saved": true
} Every account starts with the profile Hourly wage 1. A profile can step up its rates by months of employment. Wages are money, so every change waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_wage_profiles
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/wage-profiles/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `assign`. `list` only read. |
| profile string | string | Wage profile name. |
| rates array | array | Hourly wages by name and wage type. |
| employees array | array | For `assign`. |
{
"action": "action"
} {
"profile": "Cleaner, year two",
"rates": [
{
"name": "Regular hours",
"amount": 160
}
],
"assigned": [
"Employee A"
]
} Plans shared with customers and employees, and the Audits add-on: templates, reports and statistics.
Plans are shared with administrators, supervisors, customers and employees in the app and the web system. Supervisors see only the customers in their assigned customer areas. Read only.
MCP callcleanmanager_read → list_cleaning_plans
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/cleaning-plans
| Name | Type | Description |
|---|---|---|
| customer string | string | One customer only. |
{
"plans": [
{
"name": "Head office, weekly",
"customer": "Example Offices Ltd",
"template": "Weekly plan",
"language": "English"
}
]
} A finished plan is shared with the customer and the employees in the app, so the agent shows you the rows first. `copy` turns a standard plan into one for another customer. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_cleaning_plan
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/cleaning-plan/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `copy`. |
| plan string required | string | Cleaning plan name. |
| customer string | string | The workplace the plan belongs to. |
| template string | string | One of `frequency`, `area`, `weekly`, `empty`. Changing it later clears the plan. |
| language string | string | Plan language, if not the system language. |
| rows array | array | Headings and tasks in order. |
{
"action": "action",
"plan": "plan"
} {
"plan": "Warehouse, weekly",
"customer": "Example Offices Ltd",
"template": "weekly",
"rows": 14,
"saved": true
} Part of the Audits add-on. Once a template has been used it is locked so its statistics stay true; `copy` makes an editable copy. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_report_template
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/report-template/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `copy`. `list` only read. |
| template string | string | Template name. |
| customer string | string | All customers (administrator) or one customer. |
| base string | string | Base template, for example Empty report or Quality report (compact). |
| groups array | array | Parameter groups with their parameters and rating type: dropdown, checkbox or buttons. |
{
"action": "action"
} {
"template": "Office audit",
"customer": "All customers",
"groups": 3,
"locked": false,
"saved": true
} The agent records the ratings you give it; it does not inspect anything. The report counts in statistics and may be shared with the customer. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → fill_out_report
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/out-report/fill
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as list_customers returns it. |
| location string required | string | Customer location. |
| template string required | string | Report template. |
| employee string | string | The employee the report assesses. |
| answers array required | array | Rating and comment per parameter, as given by you or the inspector. |
{
"customer": "customer",
"location": "location",
"template": "template",
"answers": "answers"
} {
"report": "Office audit",
"customer": "Example Offices Ltd",
"location": "Head office",
"score": 88,
"saved": true
} Reports come from the Audits add-on module. Returns each report with its score, customer, location and date. Read only.
MCP callcleanmanager_read → list_completed_reports
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/completed-reports
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to the start date. |
| sort_by string | string | One of `customer`, `employee`, `area`, `employee_group`, with `show` naming which one. |
| show string | string | The customer, employee, area or employee group to show. |
| report_type string | string | A report type, or all. |
| export boolean | boolean | True for a CSV export. |
{
"reports": [
{
"report": "Quality report (compact)",
"customer": "Example Offices Ltd",
"location": "Head office",
"date": "2026-11-12",
"score": 92
}
]
} The numbers behind the Reports > Statistics graph. Read only.
MCP callcleanmanager_read → get_report_statistics
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/report-statistics
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO date. |
| to string required | string | ISO date. |
| sort_by string | string | One of `customer`, `employee`, `area`, `employee_group`, with `show` naming which one. |
| show string | string | The customer, employee, area or employee group to show. |
{
"from": "from",
"to": "to"
} {
"period": "2026-10-01/2026-10-31",
"by": "customer",
"scores": [
{
"customer": "Example Offices Ltd",
"average": 91
},
{
"customer": "Example School",
"average": 78
}
]
} Stock, product requests, orders and transfers to sites, plus e-mails and SMS to employees and customer contacts.
Product numbers are your internal numbers, not the supplier's. Read only.
MCP callcleanmanager_read → get_inventory
REST endpointGET https://cotlet.dev/api/v1/cleanmanager/inventory
| Name | Type | Description |
|---|---|---|
| storage string | string | Storage name. Defaults to the main storage. |
| search string | string | Product number or name. |
{
"storage": "Main storage",
"products": [
{
"number": "1001",
"name": "Microfibre cloths",
"quantity": 40,
"critical_minimum": 50,
"below_minimum": true
}
]
} A request shows order no., customer and location, who ordered, date, comment and products. Deleting a request removes it for good. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → handle_product_request
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/product-request/handle
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `approve`, `delete`. `list` only read. |
| request string | string | Order no. of the request. |
| customer string | string | Filter by customer or area. |
{
"action": "action"
} {
"requests": [
{
"order_no": "R-118",
"customer": "Example School",
"ordered_by": "Employee C",
"products": [
{
"name": "Floor cleaner 5 L",
"quantity": 2
}
]
}
]
} An order can be transferred later; a transfer moves stock at once. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → order_or_transfer_products
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/or-transfer-products/order
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `order`, `transfer`. |
| customer string required | string | Customer name, as list_customers returns it. |
| location string required | string | Customer location. |
| storage string | string | For `transfer`: the storage they leave. |
| products array required | array | Product and quantity. |
| comment string | string | Optional comment. |
{
"action": "action",
"customer": "customer",
"location": "location",
"products": "products"
} {
"action": "transfer",
"customer": "Example Offices Ltd",
"location": "Head office",
"products": [
{
"name": "Microfibre cloths",
"quantity": 20
}
],
"done": true
} Supervisors can manage storage only when the administrator allows it. A supplier with products cannot be deleted. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → manage_storage_items
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/storage-items/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create_product`, `update_product`, `delete_product`, `create_supplier`, `update_supplier`, `delete_supplier`, `set_quantity`. |
| item string required | string | Product or supplier name. |
| fields object | object | Product: product no., name, supplier, supplier product no., type, price. Supplier: name, address, CI/EAN no., phone, e-mail. |
| quantity number | number | For `set_quantity`. |
| critical_minimum number | number | For `set_quantity`. |
{
"action": "action",
"item": "item"
} {
"item": "Microfibre cloths",
"quantity": 60,
"critical_minimum": 50,
"saved": true
} Messages go out only from the web version. CleanManager signs e-mails "With kind regards" and your name. They reach people at once. By default you confirm each call; you can switch that off for this tool.
MCP callcleanmanager_write → send_message
REST endpointPOST https://cotlet.dev/api/v1/cleanmanager/messages
| Name | Type | Description |
|---|---|---|
| type string required | string | `email` or `sms`. |
| recipients array required | array | Employees and customer contact persons. |
| subject string | string | For e-mail. |
| text string required | string | The message. |
| copy_to_me boolean | boolean | Send a copy to your own e-mail. |
{
"type": "type",
"recipients": "recipients",
"text": "text"
} {
"type": "email",
"recipients": 6,
"subject": "Holiday closing days",
"sent": true
} Your signed-in CleanManager browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 29 CleanManager tools. The session cookie stays in the Cloud Browser.
What your user type sees: everything for an administrator, the assigned customer areas for a supervisor.
Your subscription and add-on modules, the accounting integrations, company structure settings and NFC tag setup.
You sign in again yourself, in the same Cloud Browser.
Disable CleanManager for agents, reset the browser, or change your CleanManager password.
Cotlet never sees or stores your password. You type it yourself, or sign in with SSO, and 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).
CleanManager offers two calendar views, the calendar and the base calendar, and its guides cover both. Cotlet watches the apps it serves and updates the CleanManager server when screens like these change, so your agent keeps working without a change on your side.
Add-on modules appear to the agent when your subscription has them: Audits for quality reports, Text Messaging for SMS.
If CleanManager signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Customer, location, employee or plan details | Call the same tool again with the earlier values |
| Cancelled task or closing day | The task stays in the calendar; create it again with create_task |
| Deleted product request | Gone for good: ask the employee to request again |
| E-mail or SMS | Already sent: send a correction |
All 17 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 12 read tools run at once.
{
"name": "register_absence",
"arguments": {
"employee": "Employee B",
"absence_type": "Sick",
"from": "2026-11-17",
"to": "2026-11-18",
"days": 2,
"transfer_to": "Employee D"
}
} curl -X POST https://cotlet.dev/api/v1/cleanmanager/absences \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"employee":"Employee B","absence_type":"Sick","from":"2026-11-17","to":"2026-11-18","days":2,"transfer_to":"Employee D"}' {
"employee": "Employee B",
"absence_type": "Sick",
"from": "2026-11-17",
"to": "2026-11-18",
"days": 2,
"tasks_moved": 4,
"transfer_to": "Employee D"
} The example registers two sick days and moves four tasks to another employee as absence hours, so wages stay right. A cron job or n8n flow can make the same call over REST at /api/v1/cleanmanager with the same key and price, in JSON. Failed calls are free.
About $25 a monthfor a cleaning company with about 25 employees and 30 customers, 4,300 credits. Your CleanManager subscription stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning alarms and tasks not started | 2 × 26 | 520 |
| Afternoon check-in review | 1 × 26 | 260 |
| Approve hours on daily tasks | 1 × 120 | 1,200 |
| Absence cover | 2 × 8 | 160 |
| Product requests and restocking | 2 × 14 | 280 |
| Quality reports from inspection notes | 1 × 20 | 200 |
| E-mails to employees and customers | 1 × 15 | 150 |
| Month-end statistics and invoicing check | 3 × 1 | 30 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 280 calls | 4,300 |
The smallest pack, 5,000 credits for $29, covers this month. More sites and more approvals use more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| 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.
| Option | What it does | Where it stops |
|---|---|---|
| Accounting integrations | Sync customers and employees, and export invoicing to FreeAgent, Business Central, QuickBooks, Sage, Uniconta or Xero. | Accounting data only; no calendar, check-in or storage. |
| File import | Loads customers and employees from a CSV file. | One-way, at setup or in batches. |
| CSV exports | Customer, employee and report data for a spreadsheet, for the administrator. | A snapshot; nothing flows back. |
| By hand | A supervisor works through the web system. | One screen at a time, between site visits. |
For bookkeeping, use the CleanManager integrations: they are the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script to watch check-ins, rearrange the calendar and handle storage in CleanManager itself, from your own login, with nothing to host.
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 CleanManager tools.
Sign up free at https://cotlet.dev/signup?app=cleanmanager, turn on CleanManager under Integrations in the console and sign in at https://cleanmanager.com/login in your Cloud Browser. Then connect your AI agent and ask about today's tasks. The trial needs no card.
CleanManager publishes no developer API: its guide articles document accounting and payroll integrations and CSV file import, and cleanmanager.com/api returns only a backend error, not documentation (checked 15 Nov 2026). No CleanManager MCP server and no official ChatGPT or Claude connector was found. Cotlet does not need one: it works in your own signed-in CleanManager account.
No. Calendar, check-in, customers, cleaning plans and storage are in the Base module. Quality reports need the Audits add-on and SMS needs Text Messaging; those tools work when your subscription has them.
Yes, within the supervisor's customer areas, as in CleanManager itself. Some actions, such as CSV exports, employee groups and storage administration without permission, are for the administrator only.
An administrator for the whole company, or a supervisor for their customer areas. Your CleanManager username is generated from your company name and your client or staff number.
Only in how it is called. Both carry the same 29 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with CleanManager.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy