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

# Bluedot API and MCP server

> Bluedot documents no REST API, but it has an official MCP server and webhooks (checked 20 Oct 2026). The MCP server has 8 tools that only read meetings, transcripts, summaries, collections and participants, and the pricing page lists it from the Basic plan. Webhooks and the Zapier and Make apps only send new summaries and transcripts out.

AI meeting recorder and note taker: it records calls, writes transcripts and AI notes from templates, and files them in collections your team can search, comment on and share.

## What is the Bluedot API?

Cotlet's Bluedot API exposes 14 endpoints for your own Bluedot account: list workspaces, list collections, list meetings, search meetings, get meeting, list comments, list notes templates, move meeting to collection, create collection, create notes template, apply template to meeting, set collection template, add comment and share meeting. The list_workspaces endpoint returns list the Bluedot workspaces your account belongs to. Each endpoint takes simple JSON inputs like workspace_id, meeting_id or collection_id and works both as an operation of the bluedot_read or bluedot_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-22

Bluedot documents no REST API, but it has an official MCP server and webhooks (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Bluedot with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Bluedot have an official API?

Bluedot documents no REST API, but it has an official MCP server and webhooks (checked 20 Oct 2026). The MCP server has 8 tools that only read meetings, transcripts, summaries, collections and participants, and the pricing page lists it from the Basic plan. Webhooks and the Zapier and Make apps only send new summaries and transcripts out.

| Task | Bluedot official | Cotlet |
|---|---|---|
| List and filter meetings | Yes: Official MCP list_meetings, paid plan | Yes |
| Read summaries and transcripts | Yes: Official MCP get_meeting, with speaker labels and timestamps | Yes |
| Search transcripts | Yes: Official MCP search_meeting | Yes |
| Move recordings into collections | No: Auto-sorting by title keyword in the app only files new recordings | Yes |
| Create collections and sub-collections | No | Yes |
| Create notes templates | No | Yes |
| Apply a template to an existing recording | No | Yes |
| Comment on a transcript | No | Yes |
| Share a recording by email or link | No | Yes |

Sources: [Bluedot Help: Bluedot MCP overview](https://help.bluedothq.com/en/articles/14708332-bluedot-mcp-overview), [Bluedot: Pricing](https://www.bluedothq.com/pricing), [Bluedot Help: How to set up webhooks](https://help.bluedothq.com/en/articles/11461975-how-to-set-up-webhooks-in-bluedot), [Bluedot Help: How to connect Bluedot to Make](https://help.bluedothq.com/en/articles/13367564-how-to-connect-bluedot-to-make-com)

## For AI agents

```text
Bluedot documents no REST API, but it has an official MCP server and webhooks (checked 20 Oct 2026). The MCP server has 8 tools that only read meetings, transcripts, summaries, collections and participants, and the pricing page lists it from the Basic plan. Webhooks and the Zapier and Make apps only send new summaries and transcripts out.
Cotlet provides a hosted MCP server and REST API for Bluedot: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=bluedot, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    bluedot_read, bluedot_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/bluedot, each operation at its own route, e.g. POST /api/v1/bluedot/collections
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_workspaces, list_collections, list_meetings, search_meetings, get_meeting, list_comments, list_templates, move_meeting_to_collection, create_collection, create_template, apply_template_to_meeting, set_collection_template, add_comment, share_meeting
Confirm      move_meeting_to_collection, create_collection, create_template, apply_template_to_meeting, set_collection_template, add_comment, share_meeting (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/bluedot-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=bluedot, requests Bluedot in the Cotlet console and creates an API key there.
2. The user signs in to Bluedot once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Bluedot 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 Bluedot 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 Bluedot 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 Bluedot 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 Bluedot 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 Bluedot's terms; Cotlet is not affiliated with Bluedot.
```

## What can an AI agent do in Bluedot?

Cotlet is best for Bluedot teams who want their agent to organize recordings, apply templates, comment and share without running or fixing a server.

- **[Sort meetings into collections](https://cotlet.dev/integrations/bluedot-api-mcp-server/sort-meetings-into-collections.md)** (runs: daily): "Find my unsorted Bluedot recordings from the last 2 weeks. File calls with customers into Customer calls and demos into Sales demos. Leave anything unclear for me." → `list_collections`, `list_meetings`, `get_meeting`, `move_meeting_to_collection`
- **[Apply a notes template to past meetings](https://cotlet.dev/integrations/bluedot-api-mcp-server/apply-notes-template-to-past-meetings.md)**: "Apply the Sales call template to last month's recordings in Customer calls. Do one first and show me the notes before you do the rest." → `list_templates`, `list_meetings`, `apply_template_to_meeting`, `get_meeting`
- **[Comment on action items in transcripts](https://cotlet.dev/integrations/bluedot-api-mcp-server/comment-on-meeting-action-items.md)** (runs: daily): "Read yesterday's customer calls. For every promise someone made, comment on that line of the transcript and mention the person who owns it." → `list_meetings`, `get_meeting`, `list_comments`, `add_comment`
- **Weekly digest of customer calls** (runs: weekly): "Every Monday, list last week's calls in Customer calls and summarize the action items from each in one message." → `list_meetings`, `get_meeting`
- **Set up a collection for a new client**: "Create a collection named Acme with a Client call template enforced on it, visible to everyone as view only." → `create_template`, `create_collection`, `set_collection_template`
- **Share recordings with attendees**: "Email last week's customer calls to their attendees from outside the company, with a password on the link." → `list_meetings`, `get_meeting`, `share_meeting`

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

Yes. Cotlet does not replace your automation platform: it gives it a Bluedot 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 sort meetings into collections, 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/bluedot/collections. | 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/bluedot/collections with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 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 Bluedot.

### list_workspaces

List the Bluedot workspaces your account belongs to. Access: read. REST: `GET /api/v1/bluedot/workspaces`. MCP: `bluedot_read → list_workspaces`.

No parameters.

Returns each workspace with its ID, name and your role (owner, admin or member). Every Bluedot user belongs to at least one workspace, and each workspace has its own billing and roles. Use the ID in the other tools when you work in more than one.

Example response:

```json
{
  "workspaces": [
    {
      "workspace_id": "w_90c1d7",
      "name": "Northwind Sales",
      "role": "admin"
    },
    {
      "workspace_id": "w_3a4be2",
      "name": "Personal",
      "role": "owner"
    }
  ]
}
```

### list_collections

List collections and sub-collections with your access level in each. Access: read. REST: `GET /api/v1/bluedot/collections`. MCP: `bluedot_read → list_collections`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |
| `parent_collection_id` | string | no | Only the sub-collections of this collection. Leave out to list all. |

Returns the collections you can see in the sidebar, nested ones with their parent_collection_id. Each row has your access (full_access, can_upload, can_view or no_access), whether it sends notes to Slack and the ID of its enforced notes template, if any. Collections you have no access to do not appear.

Example response:

```json
{
  "collections": [
    {
      "collection_id": "c_5d90e7a2",
      "title": "Customer calls",
      "parent_collection_id": null,
      "your_access": "full_access",
      "sends_notes_to_slack": true,
      "enforced_template_id": null
    },
    {
      "collection_id": "c_17f8b3d6",
      "title": "Sales demos",
      "parent_collection_id": null,
      "your_access": "can_upload",
      "sends_notes_to_slack": false,
      "enforced_template_id": "t_41c7a9f3"
    }
  ]
}
```

### list_meetings

List recordings, newest first, filtered by collection, date, uploader or participant. Access: read. REST: `GET /api/v1/bluedot/meetings`. MCP: `bluedot_read → list_meetings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |
| `collection_id` | string | no | Only recordings in this collection. |
| `since` | string | no | Only recordings made on or after this date, ISO 8601. |
| `until` | string | no | Only recordings made on or before this date, ISO 8601. |
| `uploader_email` | string | no | Only recordings uploaded by this person. |
| `participant_email` | string | no | Only recordings this person attended. |
| `sort` | string | no | newest (default) or oldest. |
| `cursor` | string | no | next_cursor from the previous page. Leave out for the first page. |

Returns recordings you are allowed to open, with title, date, length, owner, collection and whether a summary is ready. A recording outside any collection has collection_id null. Private recordings of other members never appear, even for an Owner or Admin. Pages end when next_cursor is null.

Example response:

```json
{
  "meetings": [
    {
      "meeting_id": "m_8f3a21c4",
      "title": "Catch up",
      "recorded_at": "2026-10-15T14:00:00Z",
      "duration_minutes": 32,
      "owner_email": "sam@northwind.example",
      "collection_id": null,
      "summary_ready": true
    },
    {
      "meeting_id": "m_2b6d94e0",
      "title": "Pricing review",
      "recorded_at": "2026-10-14T09:30:00Z",
      "duration_minutes": 47,
      "owner_email": "sam@northwind.example",
      "collection_id": "c_5d90e7a2",
      "summary_ready": true
    }
  ],
  "next_cursor": null
}
```

### search_meetings

Search transcripts, titles and descriptions across your recordings. Access: read. REST: `GET /api/v1/bluedot/meetings/search`. MCP: `bluedot_read → search_meetings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Words to look for, for example "pricing". |
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |
| `collection_id` | string | no | Only search inside this collection. |
| `cursor` | string | no | next_cursor from the previous page. Leave out for the first page. |

Returns matching recordings with the matching text and the timestamp where it was said, so you can jump there. Only recordings you can open are searched. Use it to find a topic, then call get_meeting for the full notes.

Example response:

```json
{
  "matches": [
    {
      "meeting_id": "m_2b6d94e0",
      "title": "Pricing review",
      "at": "00:12:40",
      "speaker": "Dana Whitfield",
      "snippet": "we can hold the pricing until Q1 if you sign this month"
    }
  ],
  "next_cursor": null
}
```

### get_meeting

Get one recording with its summary, transcript and participants. Access: read. REST: `GET /api/v1/bluedot/meetings/{meeting_id}`. MCP: `bluedot_read → get_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |
| `include` | string | no | summary, transcript or all (default all). |

Returns the AI notes split by section, the transcript with speaker labels and timestamps, and the participants with their emails. The notes follow the template the recording uses. Recordings you cannot open in Bluedot return APP_PERMISSION_DENIED.

Example response:

```json
{
  "meeting_id": "m_2b6d94e0",
  "title": "Pricing review",
  "template": "Sales call",
  "summary": {
    "sections": [
      {
        "heading": "Overview",
        "text": "Northwind reviewed Q4 pricing with Acme."
      },
      {
        "heading": "Action items",
        "text": "Dana sends the quote by Friday."
      }
    ]
  },
  "transcript": [
    {
      "speaker": "Dana Whitfield",
      "at": "00:24:10",
      "text": "I will send the quote by Friday."
    }
  ],
  "participants": [
    "dana@northwind.example",
    "li@acme.example"
  ]
}
```

### list_comments

List the comments on one recording's transcript. Access: read. REST: `GET /api/v1/bluedot/meetings/{meeting_id}/comments`. MCP: `bluedot_read → list_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |

Returns each comment with its author, text, the highlighted transcript text and the timestamp it is attached to, oldest first. Read it before add_comment: a posted comment cannot be edited, so a duplicate stays until someone deletes it.

Example response:

```json
{
  "comments": [
    {
      "comment_id": "k_72a9",
      "author": "Sam Rivera",
      "at": "00:12:40",
      "quoted_text": "we can hold the pricing until Q1",
      "text": "Check with finance first.",
      "created_at": "2026-10-14T11:02:00Z"
    }
  ]
}
```

### list_templates

List the notes templates in Workspace Settings > Templates. Access: read. REST: `GET /api/v1/bluedot/templates`. MCP: `bluedot_read → list_templates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |

Returns each template you can see with its name, AI model, visibility (private or shared) and creator. Custom templates need the Pro plan, so the list is short or empty on a lower plan. Use the ID with apply_template_to_meeting or set_collection_template.

Example response:

```json
{
  "templates": [
    {
      "template_id": "t_41c7a9f3",
      "name": "Sales call",
      "model": "Claude 4.6 Sonnet",
      "visibility": "shared",
      "created_by": "Sam Rivera"
    },
    {
      "template_id": "t_88d2c05e",
      "name": "Weekly sync",
      "model": "GPT-5",
      "visibility": "private",
      "created_by": "You"
    }
  ]
}
```

### move_meeting_to_collection

Move one recording into a collection. Access: write, asks the user first. REST: `POST /api/v1/bluedot/collections/{collection_id}/meetings/{meeting_id}/to-collection/move`. MCP: `bluedot_write → move_meeting_to_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |
| `collection_id` | string | yes | Collection ID from list_collections. |

Does what the Move icon does in Bluedot. The recording becomes visible to everyone who has access to the collection, and a collection with Send notes to Slack on posts the notes to its channel. A collection you cannot add to returns APP_PERMISSION_DENIED. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "m_8f3a21c4",
  "title": "Catch up",
  "collection_id": "c_5d90e7a2",
  "collection_title": "Customer calls",
  "moved": true
}
```

### create_collection

Create a collection or a sub-collection. Access: write, asks the user first. REST: `POST /api/v1/bluedot/collections`. MCP: `bluedot_write → create_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Collection title. |
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |
| `parent_collection_id` | string | no | Create it inside this collection. A sub-collection takes the access of its parent. |
| `everyone_access` | string | no | Default access for Everyone at Bluedot: full_access, can_upload, can_view or no_access. Leave out to keep Bluedot's default. |

Does what the + next to Collections does. The default access decides who in the workspace sees the collection, so it reaches other people. There is no tool to delete a collection, because Bluedot deletes every recording inside it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "collection_id": "c_a02e51f9",
  "title": "Acme",
  "parent_collection_id": null,
  "everyone_access": "can_view"
}
```

### create_template

Add a custom notes template to the workspace. Access: write, asks the user first. REST: `POST /api/v1/bluedot/templates`. MCP: `bluedot_write → create_template`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Template name, for example a call type. |
| `prompt` | string | yes | The prompt that tells the AI how to write the notes. It may ask for a table or a checklist. |
| `model` | string | no | AI model as the Add Template form lists it, for example Claude 4.6 Sonnet or GPT-5. |
| `visibility` | string | no | private (only you, default) or shared (everyone in the workspace). |
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |

Needs the Pro plan or higher. A shared template is visible to everyone in the workspace, who can then use it, so it reaches other people; a private one reaches nobody. Returns the template ID. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "template_id": "t_41c7a9f3",
  "name": "Sales call",
  "model": "Claude 4.6 Sonnet",
  "visibility": "shared"
}
```

### apply_template_to_meeting

Assign a notes template to an existing recording. Access: write, asks the user first. REST: `POST /api/v1/bluedot/meetings/{meeting_id}/templates/{template_id}/to-meeting/apply`. MCP: `bluedot_write → apply_template_to_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |
| `template_id` | string | yes | Notes template ID from list_templates. |

Does what assigning a template from the notes view does. The recording's notes follow the new template, and everyone the recording is shared with sees them. Returns once Bluedot accepts the change; read the new notes with get_meeting. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "m_2b6d94e0",
  "title": "Pricing review",
  "template_id": "t_41c7a9f3",
  "template_name": "Sales call",
  "status": "applied"
}
```

### set_collection_template

Set the default notes template of a collection and optionally enforce it. Access: write, asks the user first. REST: `PUT /api/v1/bluedot/templates/{template_id}/collections/{collection_id}/template`. MCP: `bluedot_write → set_collection_template`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |
| `template_id` | string | yes | Notes template ID from list_templates. |
| `enforce` | boolean | no | true turns on Enforce notes template: new meetings use it whatever each member prefers. Existing notes are not regenerated. |

Needs editing permission on the collection. With enforce on, every member's new meetings in that collection use this template. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "collection_id": "c_17f8b3d6",
  "title": "Sales demos",
  "default_template_id": "t_41c7a9f3",
  "enforced": true
}
```

### add_comment

Comment on a highlighted line of a recording's transcript. Access: write, asks the user first. REST: `POST /api/v1/bluedot/meetings/{meeting_id}/comments`. MCP: `bluedot_write → add_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |
| `quoted_text` | string | yes | The transcript text to highlight, exactly as written. The comment takes the timestamp of this line. |
| `text` | string | yes | The comment. Start a name with @ to mention a teammate. |

Posts a comment that is time-stamped to the highlighted line. A mentioned teammate is notified. Bluedot cannot edit a posted comment, so a wrong one has to be deleted in Bluedot. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "k_9c31",
  "meeting_id": "m_6e0f13b8",
  "at": "00:24:10",
  "quoted_text": "I will send the quote by Friday",
  "text": "@Dana Whitfield owns this: send the quote by Friday.",
  "mentions": [
    "Dana Whitfield"
  ],
  "created_at": "2026-10-16T08:05:00Z"
}
```

### share_meeting

Share a recording by email or by link. Access: write, asks the user first. REST: `POST /api/v1/bluedot/meetings/{meeting_id}/share`. MCP: `bluedot_write → share_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Recording ID from list_meetings or search_meetings. |
| `emails` | array of strings | no | People to invite. They get the link and a summary by email. |
| `anyone_with_link` | boolean | no | true sets Link access to Anyone with the link. |
| `password` | string | no | Protect the link with this password. Share the password separately. |

Reaches the people you name, and a link set to Anyone with the link opens the recording for whoever holds it until you turn it off. A workspace admin can disable sharing for non-admins, and then the call fails with APP_PERMISSION_DENIED. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "m_2b6d94e0",
  "invited": [
    "li@acme.example"
  ],
  "link": "https://app.bluedothq.com/share/xyz",
  "password_protected": true
}
```

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

Connecting Bluedot takes three steps: sign up, sign in to Bluedot 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 Bluedot to your agent.

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

2. **Sign in to Bluedot in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Bluedot 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 Bluedot 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.

```
Find my unsorted Bluedot recordings from the last 2 weeks. File calls with customers into Customer calls and demos into Sales demos. Leave anything unclear for me.
```

### Call Bluedot 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/bluedot 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/bluedot/collections \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workspace_id":"w_90c1d7","title":"Acme","everyone_access":"can_view"}'
```

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

```
{
  "collection_id": "c_a02e51f9",
  "title": "Acme",
  "parent_collection_id": null,
  "everyone_access": "can_view"
}
```

## Why use Cotlet for Bluedot?

**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 Bluedot 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 Bluedot changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Bluedot to Cotlet?

Yes. You sign in to Bluedot yourself, in your own Cloud Browser, and we never save your password. Your agents only get Bluedot 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 Bluedot integration?**

No, Cotlet is independent of Bluedot. Bluedot's own API is too limited for this work. Cotlet works through your own Bluedot account, the way you use Bluedot 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 Bluedot in your console: your agents lose access at once and you stay signed in. Signing out of Bluedot in the browser works too, and Reset browser deletes the whole profile.

## Is there a Bluedot MCP server on GitHub?

No open-source Bluedot MCP server exists on GitHub. The realistic options are Bluedot's own MCP server, which only reads, and the Zapier and Make apps, which fire when a summary or transcript is ready. Cotlet reads the same data and also writes: it files recordings, applies templates, comments and shares in your own account, hosted and maintained for you.

|  | Bluedot MCP and Zapier | Cotlet |
|---|---|---|
| Setup | A paid Bluedot plan, then the MCP connector in Claude or ChatGPT; Zapier and Make connect under Automation > Integrations | Sign up, sign in to Bluedot once, add one MCP server or API key |
| What it does | Reads meetings, transcripts and summaries; triggers when a summary or transcript is ready | The same reads, plus moving recordings, creating collections and templates, commenting and sharing |
| When Bluedot changes | Bluedot keeps its own MCP server and apps working | Our team tests it daily and fixes it for you; failed calls are free |
| Your Bluedot session | You sign in to the Bluedot account you want the assistant to use | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | Nothing for MCP; you build and watch each Zap or scenario yourself | Nothing to host or update |
| Where it runs | Claude and ChatGPT connectors; Zapier and Make for scheduled flows | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | MCP and webhooks are on Bluedot's paid plans; Zapier and Make have their own plans | 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 Bluedot 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 Bluedot API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Bluedot 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 Bluedot 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 Bluedot 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 Bluedot only after you enable it. When Bluedot 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 Bluedot, sign out of Bluedot 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.
- **Bluedot's terms:** You use your own Bluedot account and stay responsible for following Bluedot's terms. Cotlet is independent and not affiliated with Bluedot. [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 Bluedot in the console and press Request access. Then you create your API key and connect Bluedot there.

**Do I need to be technical?**

No. You sign in to Bluedot 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 Bluedot to Cotlet?**

Yes. You sign in to Bluedot yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Bluedot 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 Bluedot 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 Bluedot 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 Bluedot's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Bluedot 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 Bluedot 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?**

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

**Which Bluedot plan do I need?**

Bluedot's pricing page lists MCP integration and webhooks from the Basic plan, custom note templates from Pro, and org-wide MCP and webhooks, CRM and ATS integrations on Business. Cotlet works in your own account, so a tool works where the same click works for you: create_template needs Pro, and the Free plan allows 5 meetings in a lifetime.

**Can the agent read other members' private recordings?**

No. Bluedot makes a private recording visible only to its owner, and Owners and Admins get no default access either. The agent sees what your account sees, so another member's private recording is absent from list_meetings.

**Does moving a recording post to Slack?**

Only when the collection has Send notes to Slack on. Then Bluedot posts the notes with an overview and a link to the recording in the chosen channel. Slack caps a message at 3,000 characters, so a longer summary may not sync.

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

No. Every call to move_meeting_to_collection, create_collection, create_template, apply_template_to_meeting, set_collection_template, add_comment or share_meeting 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 Bluedot 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/bluedot 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.