[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Breezeway API and MCP server

> Breezeway has a REST API for properties, reservations, tasks and people, but you need API keys from a request form, and it has no official MCP server (checked 20 Oct 2026). Templates, task tags, subdepartments and supplies can only be created in the app.

Operations platform for vacation rental and property managers: a schedule of cleaning, inspection, maintenance and safety tasks, reservations, property details and a mobile app for field staff.

## What is the Breezeway API?

Cotlet's Breezeway API exposes 13 endpoints for your own Breezeway account: list properties, list people, list task templates, list tasks, get task, list task comments, get task checklist responses, create task, assign task, add task comment, close task, approve task and reopen task. The list_properties endpoint returns the properties in your Breezeway account, with ID, name and address. Each endpoint takes simple JSON inputs like task_id, department or property_id and works both as an operation of the breezeway_read or breezeway_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate.md)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-18

Breezeway has a REST API for properties, reservations, tasks and people, but you need API keys from a request form, and it has no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Breezeway with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Breezeway have an official API?

Breezeway has a REST API for properties, reservations, tasks and people, but you need API keys from a request form, and it has no official MCP server (checked 20 Oct 2026). Templates, task tags, subdepartments and supplies can only be created in the app.

| Task | Breezeway official | Cotlet |
|---|---|---|
| List tasks | Partly: One property per call: home_id or reference_property_id is required | Yes |
| Create tasks | Yes: Needs API keys | Yes |
| Assign people to tasks | Yes: Needs API keys | Yes |
| Comment on tasks | Yes: Needs API keys | Yes |
| Close, approve and reopen tasks | Yes: Approve works only on a closed task | Yes |
| Read checklist responses | Yes: Needs API keys | Yes |
| List people and templates | Yes: Needs API keys | Yes |
| Work without an approved API key | No: Keys are issued through a request form | Yes |

Sources: [Breezeway Developer Hub: Getting Started](https://developer.breezeway.io/docs/getting-started), [Breezeway Developer Hub: Obtaining Credentials](https://developer.breezeway.io/docs/obtaining-credentials), [Breezeway Developer Hub: Authentication](https://developer.breezeway.io/docs/authentication), [Breezeway Developer Hub: Index of all endpoints](https://developer.breezeway.io/llms.txt)

## For AI agents

```text
Breezeway has a REST API for properties, reservations, tasks and people, but you need API keys from a request form, and it has no official MCP server (checked 20 Oct 2026). Templates, task tags, subdepartments and supplies can only be created in the app.
Cotlet provides a hosted MCP server and REST API for Breezeway: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=breezeway, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    breezeway_read, breezeway_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/breezeway, each operation at its own route, e.g. POST /api/v1/breezeway/properties/{property_id}/tasks
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_properties, list_people, list_templates, list_tasks, get_task, list_task_comments, get_task_checklist, create_task, assign_task, add_task_comment, close_task, approve_task, reopen_task
Confirm      create_task, assign_task, add_task_comment, close_task, approve_task, reopen_task (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/breezeway-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=breezeway, requests Breezeway in the Cotlet console and creates an API key there.
2. The user signs in to Breezeway once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Breezeway for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Breezeway server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Breezeway in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Breezeway only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Breezeway login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Breezeway's terms; Cotlet is not affiliated with Breezeway.
```

## What can an AI agent do in Breezeway?

Cotlet is best for vacation rental managers who want their AI agent to create, assign and approve Breezeway tasks without requesting API keys or running a server.

- **[Assign unassigned tasks](https://cotlet.dev/integrations/breezeway-api-mcp-server/assign-unassigned-tasks.md)** (runs: daily): "List tomorrow's unassigned Breezeway tasks. Give each housekeeping task to a housekeeper whose shift covers it, and list the ones nobody can take." → `list_tasks`, `list_people`, `assign_task`
- **[Create maintenance tasks from guest issues](https://cotlet.dev/integrations/breezeway-api-mcp-server/create-maintenance-tasks-from-guest-issues.md)** (runs: daily): "Read this guest message about Harbor View 4, create an urgent maintenance task from the right template, and assign the property's maintenance person." → `list_properties`, `list_templates`, `list_people`, `create_task`
- **[Approve finished tasks](https://cotlet.dev/integrations/breezeway-api-mcp-server/approve-finished-tasks.md)** (runs: daily): "Review yesterday's finished Breezeway tasks. Approve the ones with every checklist item done and photos where required, and reopen the rest with a comment." → `list_tasks`, `get_task_checklist`, `approve_task`, `reopen_task`, `add_task_comment`
- **Daily overdue tasks digest** (runs: daily): "Every morning, list Breezeway tasks scheduled before today that are not finished, grouped by property, with the assignee." → `list_tasks`, `get_task`
- **Nudge assignees on stuck tasks** (runs: daily): "For urgent Breezeway tasks not started by noon, add a comment asking the assignee for an update." → `list_tasks`, `add_task_comment`

## Can Breezeway automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Breezeway connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to assign unassigned tasks, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/breezeway/tasks. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/breezeway/tasks with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Breezeway.

### list_properties

the properties in your Breezeway account, with ID, name and address. Access: read. REST: `GET /api/v1/breezeway/properties`. MCP: `breezeway_read → list_properties`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a property name or address. |

Returns each property with its ID, name and address, in the order the Properties page shows them. The property ID is what list_tasks and create_task take. Cross-company accounts see the company that is open in the app.

Example response:

```json
{
  "properties": [
    {
      "property_id": 16052,
      "name": "Harbor View 4",
      "address": "12 Harbor Street"
    },
    {
      "property_id": 16077,
      "name": "Maple Cabin",
      "address": "8 Maple Lane"
    }
  ]
}
```

### list_people

Lists the staff of your account with their departments and weekly shifts. Access: read. REST: `GET /api/v1/breezeway/peoples`. MCP: `breezeway_read → list_people`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One of active, invited, inactive. Defaults to active. |

Returns each person with ID, name, role, departments, groups and shifts per weekday. The person ID is what assign_task and create_task take. Reading people needs an administrator or supervisor account.

Example response:

```json
{
  "people": [
    {
      "person_id": 136,
      "name": "Ana Lopez",
      "role": "service_partner",
      "departments": [
        "housekeeping",
        "inspection"
      ],
      "shifts": {
        "monday": [
          {
            "start": "09:00",
            "end": "17:00"
          }
        ]
      }
    },
    {
      "person_id": 187,
      "name": "Marco Diaz",
      "role": "service_partner",
      "departments": [
        "maintenance"
      ],
      "shifts": {
        "monday": [
          {
            "start": "08:00",
            "end": "16:00"
          }
        ]
      }
    }
  ]
}
```

### list_templates

Lists the active task templates (checklists) of a department. Access: read. REST: `GET /api/v1/breezeway/templates`. MCP: `breezeway_read → list_templates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department` | string | no | One of housekeeping, inspection, maintenance, safety. Omit for all. |

Returns each active template with its ID, name and department. The template ID goes into create_task. Templates are created in the app, under Settings > Tasks > Templates.

Example response:

```json
{
  "templates": [
    {
      "template_id": 27,
      "name": "Default Inspection",
      "department": "inspection"
    },
    {
      "template_id": 31,
      "name": "Plumbing issue",
      "department": "maintenance"
    }
  ]
}
```

### list_tasks

Lists tasks filtered by property, department, dates and assignee. Access: read. REST: `GET /api/v1/breezeway/tasks`. MCP: `breezeway_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | integer | no | Breezeway property ID. Omit to read all properties. |
| `department` | string | no | One of housekeeping, inspection, maintenance, safety. |
| `scheduled_from` | string | no | First scheduled date, YYYY-MM-DD. |
| `scheduled_to` | string | no | Last scheduled date, YYYY-MM-DD. |
| `assignee_id` | integer | no | Only tasks assigned to this person ID. |
| `unassigned` | boolean | no | Only tasks with nobody assigned. |

Returns one row per task with ID, name, property, department, priority, status, scheduled date and assignees. Results come in pages and the agent follows the cursor to the end. Tasks you cannot see in the app are not returned.

Example response:

```json
{
  "tasks": [
    {
      "task_id": 4417302,
      "name": "Turnover clean, Harbor View 4",
      "property": "Harbor View 4",
      "department": "housekeeping",
      "priority": "normal",
      "status": "Scheduled",
      "scheduled_date": "2026-10-21",
      "assignees": []
    }
  ],
  "next_cursor": null
}
```

### get_task

Returns one task with assignees, tags, supplies and report link. Access: read. REST: `GET /api/v1/breezeway/tasks/{task_id}`. MCP: `breezeway_read → get_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |

Returns the full task as the task page shows it: description, status, scheduled date and time, assignees with their response, tags and supplies. Use list_task_comments for the comments.

Example response:

```json
{
  "task_id": 4417295,
  "name": "Turnover clean, Harbor View 4",
  "property": "Harbor View 4",
  "department": "housekeeping",
  "priority": "normal",
  "status": "Completed",
  "scheduled_date": "2026-10-20",
  "assignees": [
    {
      "person_id": 136,
      "name": "Ana Lopez"
    }
  ],
  "tags": [],
  "report_url": "https://portal.breezeway.io/task/report/example"
}
```

### list_task_comments

Lists the comments on a task, oldest first. Access: read. REST: `GET /api/v1/breezeway/task-comments`. MCP: `breezeway_read → list_task_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |

Returns each comment with its text, author and time. Photos on a comment are not returned.

Example response:

```json
{
  "comments": [
    {
      "comment_id": 36076431,
      "text": "All cleaned up",
      "author": "Ana Lopez",
      "created_at": "2026-10-20T11:05:00"
    }
  ]
}
```

### get_task_checklist

Returns the checklist answers staff gave on a completed task. Access: read. REST: `GET /api/v1/breezeway/tasks/{task_id}/checklist`. MCP: `breezeway_read → get_task_checklist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |

Returns each requirement with section, action text, the response, any note, whether a photo was required and how many photos are attached. Only tasks started from a template have a checklist; others return an empty list.

Example response:

```json
{
  "requirements": [
    {
      "section": "Bathroom",
      "action": "Fold clean linens",
      "response": "check",
      "note": null,
      "photo_required": true,
      "photos": 0
    },
    {
      "section": "Kitchen",
      "action": "Wipe the oven",
      "response": "check",
      "note": null,
      "photo_required": false,
      "photos": 0
    }
  ]
}
```

### create_task

Creates a task on a property. Access: write, asks the user first. REST: `POST /api/v1/breezeway/properties/{property_id}/tasks`. MCP: `breezeway_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | integer | yes | Breezeway property ID. |
| `name` | string | yes | Task name. |
| `department` | string | no | One of housekeeping, inspection, maintenance, safety. |
| `priority` | string | no | One of urgent, high, normal, low, watch. |
| `description` | string | no | Text shown on the task. |
| `template_id` | integer | no | Template ID from list_templates. |
| `scheduled_date` | string | no | Date, YYYY-MM-DD. |
| `person_ids` | array | no | IDs from list_people to assign. |

Returns the new task ID, status and assignees. A task from a template carries the template's checklist. Assigned people can be notified depending on the account's draft and commit settings. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 4417310,
  "name": "No hot water, Harbor View 4",
  "department": "maintenance",
  "priority": "urgent",
  "status": "Scheduled",
  "scheduled_date": "2026-10-21",
  "assignees": [
    {
      "person_id": 187,
      "name": "Marco Diaz"
    }
  ]
}
```

### assign_task

Sets the people assigned to a task. Access: write, asks the user first. REST: `POST /api/v1/breezeway/tasks/{task_id}/assign`. MCP: `breezeway_write → assign_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |
| `person_ids` | array | yes | IDs from list_people. Replaces the current assignees. |

Returns the task with its new assignees. The list replaces the current assignees, so include everyone who should stay. Drafted tasks notify nobody until they are committed in Breezeway. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 4417302,
  "name": "Turnover clean, Harbor View 4",
  "assignees": [
    {
      "person_id": 136,
      "name": "Ana Lopez"
    }
  ],
  "scheduled_date": "2026-10-21"
}
```

### add_task_comment

Adds a comment to a task, under your name. Access: write, asks the user first. REST: `POST /api/v1/breezeway/tasks/{task_id}/comment`. MCP: `breezeway_write → add_task_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |
| `comment` | string | yes | Comment text. |

Returns the comment ID and time. The comment is visible to the task's assignees and managers and cannot be removed through Cotlet. Text only. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": 36076440,
  "task_id": 4417295,
  "created_at": "2026-10-21T08:30:00"
}
```

### close_task

Marks a task as finished. Access: write, asks the user first. REST: `POST /api/v1/breezeway/tasks/{task_id}/close`. MCP: `breezeway_write → close_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |

Returns the task with its finished time and status. Use it for tasks staff did not close themselves. A closed task can be approved or reopened. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 4417299,
  "name": "Replace smoke detector battery",
  "status": "Closed",
  "finished_at": "2026-10-21T09:12:00"
}
```

### approve_task

Moves a closed task to Approved. Access: write, asks the user first. REST: `POST /api/v1/breezeway/tasks/{task_id}/approve`. MCP: `breezeway_write → approve_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |

Returns the task with its new status. Only a closed task can be approved, and the account needs "Approve tasks after completion" turned on. Needs an administrator or supervisor. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 4417295,
  "name": "Turnover clean, Harbor View 4",
  "status": "Approved"
}
```

### reopen_task

Puts a closed task back in progress. Access: write, asks the user first. REST: `POST /api/v1/breezeway/tasks/{task_id}/reopen`. MCP: `breezeway_write → reopen_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | integer | yes | Breezeway task ID. |
| `notify_assignees` | boolean | no | Tell the assignees the task was reopened. Defaults to false. |

Returns the task with its new status. With notify_assignees true, the assignees hear about it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 4417301,
  "name": "Deep clean, Maple Cabin",
  "status": "In progress",
  "notified": false
}
```

## How do I connect Breezeway to Claude Code, Codex or Cursor?

Connecting Breezeway takes three steps: sign up, sign in to Breezeway once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Breezeway to your agent.

1. **Create an account** Sign up and add Breezeway in the console. Your API key is there too.

2. **Sign in to Breezeway in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Breezeway there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Breezeway tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List tomorrow's unassigned Breezeway tasks. Give each housekeeping task to a housekeeper whose shift covers it, and list the ones nobody can take.
```

### Call Breezeway from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/breezeway with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/breezeway/properties/16052/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"No hot water, Harbor View 4","department":"maintenance","priority":"urgent","scheduled_date":"2026-10-21","description":"Guest reports no hot water since this morning.","person_ids":[187]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "task_id": 4417310,
  "name": "No hot water, Harbor View 4",
  "department": "maintenance",
  "priority": "urgent",
  "status": "Scheduled",
  "scheduled_date": "2026-10-21",
  "assignees": [
    {
      "person_id": 187,
      "name": "Marco Diaz"
    }
  ]
}
```

## Why use Cotlet for Breezeway?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Breezeway yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Breezeway changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Breezeway to Cotlet?

Yes. You sign in to Breezeway yourself, in your own Cloud Browser, and we never save your password. Your agents only get Breezeway once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Breezeway integration?**

No, Cotlet is independent of Breezeway. Breezeway's own API is too limited for this work. Cotlet works through your own Breezeway account, the way you use Breezeway in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Breezeway in your console: your agents lose access at once and you stay signed in. Signing out of Breezeway in the browser works too, and Reset browser deletes the whole profile.

## Is there a Breezeway MCP server on GitHub?

Yes. Breezeway's own API covers tasks, people and comments, so you can write a script or your own MCP server on it. You request keys by form, exchange them for a token that lasts 24 hours, and host and fix the server yourself. Cotlet hosts the same tools for you and works from your signed-in account, with no key request.

|  | Breezeway API | Cotlet |
|---|---|---|
| Setup | Send the request form, wait for keys, write a server, handle tokens | Sign up, sign in to Breezeway once, add one MCP server or API key |
| When Breezeway changes | You read the changelog and update your code | Our team tests it daily and fixes it for you; failed calls are free |
| Your credentials | Client ID and secret in your own config | No API keys; your session lives in your own Cloud Browser in the EU, profile encrypted, disabled for agents in one click |
| When access expires | Access token lasts 24 hours; your code must refresh it, and the token endpoint allows 1 request per minute | Your Cloud Browser keeps you signed in; if Breezeway logs you out, your agent gets a link to sign in again |
| Upkeep | You host, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Wherever you deploy it | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | The API has no listed fee; you pay with engineering time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Breezeway changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Breezeway API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Breezeway API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Breezeway account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Breezeway yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Breezeway only after you enable it. When Breezeway signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Breezeway, sign out of Breezeway in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Breezeway's terms:** You use your own Breezeway account and stay responsible for following Breezeway's terms. Cotlet is independent and not affiliated with Breezeway. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Breezeway in the console and press Request access. Then you create your API key and connect Breezeway there.

**Do I need to be technical?**

No. You sign in to Breezeway once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Breezeway to Cotlet?**

Yes. You sign in to Breezeway yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Breezeway once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Breezeway sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Breezeway cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Breezeway's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Breezeway sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Breezeway login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Breezeway offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need Breezeway API keys?**

No. Cotlet works in your own signed-in Breezeway account. Breezeway issues API keys to account holders through a request form, and Cotlet does not use them. Your role still counts: creating, assigning and approving tasks needs an administrator or supervisor account.

**Why can approve_task fail?**

Breezeway lets a task move to Approved only after it was closed, and only when "Approve tasks after completion" is on under Settings > General > Operations. If either is missing, the call fails and the agent reports why.

**Can my agent post or send messages in Breezeway without asking me?**

No. Every call to create_task, assign_task, add_task_comment, close_task, approve_task or reopen_task waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Breezeway API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/breezeway from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.