Real estate
Breezeway
Create, assign, comment on and approve Breezeway property tasks.
13 endpoints
Turno's External API is for partners Turno grants access to, and it has no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Turno MCP server with 11 tools that ChatGPT and Claude use in your own Turno account, host or cleaner. Payments, bids and messages wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Turno. Turno is a trademark of its owner. If Turno's own integrations cover what you need, use them first.
11 tools Read and write
Turno has an External API v2, documented at apidocs.turnoverbnb.com, and asks you to contact it so it can grant you access as a partner. No Turno MCP server and no official ChatGPT or Claude connector was found.
| What you need | Turno API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your turnovers | No MCP server found | Copy and paste | Hosted MCP server |
| Start today with your own login | Become a partner first | Your login | Your login, once |
| Calendars, cleaners and checklists | In the API | One property at a time | Every property in one call |
| Marketplace bids, payments and chat | Not in the API | In the app | Same tools, after your OK |
Checked 16 Nov 2026. Sources: Turno External API v2 · Turno for Hosts on Google Play · Turno for Cleaners on Google Play · Turno integrations
Once, in a browser we host for you.
One address in its settings.
It reads every property and flags the gaps.
Your agent works in your own signed-in Cloud Browser. Payments, bids, invitations and messages wait for your OK. Who can see your session
Sign in to Turno in a Cloud Browser. Open app.turno.com in your Cotlet Cloud Browser and log in to your host or cleaner account.
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.
Turno shares https://cotlet.dev/mcp/v1 with every other app you switch on, so your channel manager, inbox and Turno can sit behind one connector. Added Turno later? Refresh the connector and the 11 Turno 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: turno_read Host tools and cleaner tools, from the two Turno apps. Write tools with an `action` read on `list`, `get` or `read` and ask first on the rest.
Guest calendars from Airbnb, Vrbo, Booking.com, channel managers, iCal, Google Calendar or Outlook, then the cleaners and backups calendar sync schedules.
Turno reads checkouts from the imported calendar, and calendar sync schedules your cleaners around them. A wrong calendar puts cleans on the wrong days, so the agent shows you the property and source before it saves. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → import_guest_calendar
REST endpointPOST https://cotlet.dev/api/v1/turno/guest-calendars
| Name | Type | Description |
|---|---|---|
| property string required | string | The rental property, by the name it has in Turno. |
| source string required | string | Where the bookings come from: `airbnb`, `vrbo`, `booking_com`, `channel_manager`, `ical`, `google_calendar` or `outlook`. |
| calendar_url string | string | The calendar link, for iCal, Google Calendar and Outlook. |
{
"property": "property",
"source": "source"
} {
"property": "Harbor View loft",
"source": "airbnb",
"connected": true,
"upcoming_checkouts": 6
} `list` returns each turnover with its checkout date and the cleaner on it, so gaps stand out. `assign` makes a cleaner the one calendar sync schedules for a property; it changes their work, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → schedule_cleaners
REST endpointPOST https://cotlet.dev/api/v1/turno/cleaners/schedule
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `assign`. `list` only reads. |
| property string | string | The property. Leave empty with `list` for every property. |
| cleaner string | string | For `assign`: one of your existing cleaners, by name. |
| from string | string | For `list`: ISO start date. Defaults to today. |
{
"action": "action"
} {
"turnovers": [
{
"property": "Harbor View loft",
"checkout": "2026-11-20",
"cleaner": "Example Cleaning Co"
},
{
"property": "Pine Cabin",
"checkout": "2026-11-21",
"cleaner": null
}
]
} Backups are the cleaners you set for a property next to its main cleaner, so a turnover still has someone to ask. Setting them changes who may be asked to clean, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → set_backup_cleaners
REST endpointPUT https://cotlet.dev/api/v1/turno/backup-cleaners
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `set`. `list` only reads. |
| property string required | string | The rental property, by the name it has in Turno. |
| cleaners array | array | For `set`: backup cleaners in the order you want them, by name. |
{
"action": "action",
"property": "property"
} {
"property": "Pine Cabin",
"backups": [
"Sample Sparkle Services",
"Example Cleaning Co"
],
"saved": true
} What the cleaner works through, cleaners who bid on your property, and payment for completed projects.
The checklist is what your cleaner works through at each turnover. `update` replaces the list with the one you give, so the agent reads it first and shows you the change. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → manage_property_checklists
REST endpointPOST https://cotlet.dev/api/v1/turno/property-checklists/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `get` only reads. |
| property string required | string | The rental property, by the name it has in Turno. |
| items array | array | For `update`: the full list of checklist items, in order. |
{
"action": "update",
"property": "Harbor View loft",
"items": [
"Strip and remake beds",
"Restock coffee and toiletries",
"Photo of living room when done"
]
} {
"property": "Harbor View loft",
"checklist": [
"Strip and remake beds",
"Restock coffee and toiletries",
"Photo of living room when done"
],
"saved": true
} Returns cleaners in your area and any bids they made on your property, with their price. Cleaners on the Marketplace set their own prices. Reading changes nothing and contacts no one.
MCP callturno_read → find_marketplace_cleaners
REST endpointGET https://cotlet.dev/api/v1/turno/marketplace-cleaners/find
| Name | Type | Description |
|---|---|---|
| property string required | string | The rental property, by the name it has in Turno. |
{
"property": "property"
} {
"property": "Pine Cabin",
"bids": [
{
"cleaner": "Sample Sparkle Services",
"price": 95
},
{
"cleaner": "Example Home Care",
"price": 110
}
]
} Turno can pay your cleaners automatically when they complete a project; this tool reads those payments and pays one that is still open. A payment moves money, so `pay` always shows the cleaner, project and amount first. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → pay_cleaners
REST endpointPOST https://cotlet.dev/api/v1/turno/cleaners/pay
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `pay`. `list` only reads. |
| project string | string | For `pay`: the completed cleaning project. |
| from string | string | For `list`: ISO start date. |
{
"action": "action"
} {
"projects": [
{
"project": "Harbor View loft, 14 Nov",
"cleaner": "Example Cleaning Co",
"amount": 120,
"paid": true
},
{
"project": "Pine Cabin, 15 Nov",
"cleaner": "Sample Sparkle Services",
"amount": 95,
"paid": false
}
]
} Every client's turnovers in one list, new jobs in your area, bids at your own price and invitations to hosts you already clean for.
Turno puts each new turnover from your clients' calendars on your schedule and tells you when a cleaning project changes. This tool reads that schedule; it changes nothing.
MCP callturno_read → view_turnover_schedule
REST endpointGET https://cotlet.dev/api/v1/turno/turnover-schedules/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date. Defaults to today. |
| to string | string | ISO end date. Defaults to seven days on. |
| client string | string | Limit to one host. |
{
"turnovers": [
{
"date": "2026-11-20",
"client": "Example Host",
"property": "Harbor View loft"
},
{
"date": "2026-11-20",
"client": "Sample Stays",
"property": "Lake House"
},
{
"date": "2026-11-21",
"client": "Example Host",
"property": "Pine Cabin"
}
]
} Returns the open jobs Turno shows you in your area. Reading them contacts no host.
MCP callturno_read → find_marketplace_jobs
REST endpointGET https://cotlet.dev/api/v1/turno/marketplace-jobs/find
| Name | Type | Description |
|---|---|---|
| area string | string | City or postcode. Defaults to the area on your Turno profile. |
{
"area": "Asheville, NC",
"jobs": [
{
"job": "Two bedroom cabin, turnover cleaning",
"host": "Example Host"
},
{
"job": "Studio apartment, turnover cleaning",
"host": "Sample Stays"
}
]
} Turno lets cleaners set their own prices and bid for free. The bid reaches the host, so the agent shows you the job and price first. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → bid_on_cleaning_job
REST endpointPOST https://cotlet.dev/api/v1/turno/cleaning-job/bid
| Name | Type | Description |
|---|---|---|
| job string required | string | The Marketplace job, as find_marketplace_jobs returns it. |
| price number required | number | Your price for the clean, in your account currency. |
| note string | string | A short note to the host. |
{
"job": "job",
"price": 1
} {
"job": "Two bedroom cabin, turnover cleaning",
"price": 95,
"sent": true
} The invitation reaches the host, so it waits for your OK. Once they join, their turnovers land on your schedule. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → invite_customers
REST endpointPOST https://cotlet.dev/api/v1/turno/customers/invite
| Name | Type | Description |
|---|---|---|
| name string required | string | The host's name. |
| email string required | string | The host's email address. |
{
"name": "Jane Doe",
"email": "jane@example.com"
} {
"name": "Example Host",
"email": "host@example.com",
"invited": true
} Turno's in-app chat between hosts and cleaners. Sending asks first.
The message reaches the other person in Turno's in-app chat, so the agent shows you the text before it sends. By default you confirm each call; you can switch that off for this tool.
MCP callturno_write → send_chat_message
REST endpointPOST https://cotlet.dev/api/v1/turno/chat-messages
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `read`, `send`. `read` only reads. |
| with string required | string | The cleaner or host, by name. |
| message string | string | For `send`: the text. |
{
"action": "action",
"with": "with"
} {
"with": "Example Cleaning Co",
"sent": true,
"message": "Guests leave at 10 on Thursday. Please restock coffee at Harbor View."
} Your signed-in Turno browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 11 Turno tools. The session cookie stays in the Cloud Browser.
The properties, cleaners, clients and payments of the one Turno account you signed in with.
Your payment methods and payout details, your plan, and your Turno profile settings.
You log in again yourself, in the same Cloud Browser.
Disable Turno for agents, reset the browser, or change your Turno password.
You type your Turno password yourself; the agent only uses the session that log-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
get. | Action | How to put it right |
|---|---|
| Checklist changed | Call manage_property_checklists again with the earlier items |
| Cleaner or backups set | Run schedule_cleaners or set_backup_cleaners again with the right names |
| Calendar imported to the wrong property | Import it again on the right one and remove the wrong link in Turno |
| Payment, bid, invitation or message | Already with the other person: talk to them directly |
All 8 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 read tools, Marketplace searches and the cleaner schedule, run at once.
{
"name": "manage_property_checklists",
"arguments": {
"action": "update",
"property": "Harbor View loft",
"items": [
"Strip and remake beds",
"Restock coffee and toiletries",
"Photo of living room when done"
]
}
} curl -X POST https://cotlet.dev/api/v1/turno/property-checklists/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"update","property":"Harbor View loft","items":["Strip and remake beds","Restock coffee and toiletries","Photo of living room when done"]}' {
"property": "Harbor View loft",
"checklist": [
"Strip and remake beds",
"Restock coffee and toiletries",
"Photo of living room when done"
],
"saved": true
} The example sets a three item checklist on one loft. A cron job or n8n flow can make the same call over REST at /api/v1/turno with the same key and price, in JSON, for example to copy one checklist to every property. Failed calls are free.
About $15 a monthfor a host with six rentals, 2,650 credits. Your Turno plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Daily check for turnovers with no cleaner | 2 × 30 | 600 |
| Messages to cleaners | 1 × 30 | 300 |
| Weekly payment check | 2 × 4 | 80 |
| Checklist updates | 2 × 4 | 80 |
| Marketplace bids and backups | 2 × 3 | 60 |
| New property setup | 3 × 1 | 30 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 115 calls | 2,650 |
The smallest pack, 5,000 credits for $29, covers this month. A busier season means more turnovers and more calls.
Credit packs are one-time purchases, not a subscription. The month above is our own assumption, 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 |
|---|---|---|
| Turno External API v2 | Properties, bookings, projects, checklists and webhooks for your own code. | Partner access on request; no Marketplace, payments or chat. |
| Turno's calendar import | Brings bookings in from Airbnb, Vrbo, Booking.com, channel managers and calendars. | Feeds Turno; it is not a route for an AI agent. |
| Turno mobile apps | Turno for Hosts and Turno for Cleaners on your phone. | One tap at a time, by you. |
| By hand | Open each property in Turno. | Only while you are looking. |
If you build software for many hosts and Turno grants you partner access, its API and webhooks are the right route for calendars and projects. Cotlet fits when you run your own rentals or cleaning business and want ChatGPT, Claude or a script working in Turno today.
Cotlet.dev is made by Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273) and building software since 2019, with Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) as founders. For questions about the Turno tools, write to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=turno, turn on Turno under Integrations in the console and log in at https://app.turno.com/login in your Cloud Browser. Then connect your AI agent and ask it about next week's turnovers. The trial needs no card.
Yes, for partners: Turno has an External API v2 (apidocs.turnoverbnb.com) for properties, bookings, cleaning projects, checklists, cleaners and webhooks, and asks you to contact Turno so it can grant access (checked 16 Nov 2026). It has no Marketplace bids, cleaner payments or chat. No Turno MCP server and no official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Turno account.
Yes. Sign in with the Turno account you use. Host accounts use the calendar, cleaner, checklist, Marketplace and payment tools; cleaner accounts use view_turnover_schedule, find_marketplace_jobs, bid_on_cleaning_job and invite_customers. Chat works for both.
Yes. Turno for Hosts and Turno for Cleaners are described on Google Play as formerly the TurnoverBnB Host App and Cleaner App, and the API still lives at apidocs.turnoverbnb.com.
Not by default. pay_cleaners asks first on every payment and shows the cleaner, project and amount. Turno's own automatic payments keep running as you set them in Turno.
Only in how it is called. Both carry the same 11 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 Turno.
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