[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 MCP tools

> The Bluedot MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/bluedot

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Bluedot has 14 operations on the Cotlet MCP server, in bluedot_read and bluedot_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `bluedot_read`, `bluedot_write`
- Connects with: Your own Bluedot account (any role: Owner, Admin or Member; custom templates need the Pro plan, workspace settings need Owner or Admin)
- Integration page: https://cotlet.dev/integrations/bluedot-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_workspaces`](https://cotlet.dev/docs/mcp/bluedot/list_workspaces.md) | List the Bluedot workspaces your account belongs to. |
| [`list_collections`](https://cotlet.dev/docs/mcp/bluedot/list_collections.md) | List collections and sub-collections with your access level in each. |
| [`list_meetings`](https://cotlet.dev/docs/mcp/bluedot/list_meetings.md) | List recordings, newest first, filtered by collection, date, uploader or participant. |
| [`search_meetings`](https://cotlet.dev/docs/mcp/bluedot/search_meetings.md) | Search transcripts, titles and descriptions across your recordings. |
| [`get_meeting`](https://cotlet.dev/docs/mcp/bluedot/get_meeting.md) | Get one recording with its summary, transcript and participants. |
| [`list_comments`](https://cotlet.dev/docs/mcp/bluedot/list_comments.md) | List the comments on one recording's transcript. |
| [`list_templates`](https://cotlet.dev/docs/mcp/bluedot/list_templates.md) | List the notes templates in Workspace Settings > Templates. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`move_meeting_to_collection`](https://cotlet.dev/docs/mcp/bluedot/move_meeting_to_collection.md) (Confirm) | Move one recording into a collection. |
| [`create_collection`](https://cotlet.dev/docs/mcp/bluedot/create_collection.md) (Confirm) | Create a collection or a sub-collection. |
| [`create_template`](https://cotlet.dev/docs/mcp/bluedot/create_template.md) (Confirm) | Add a custom notes template to the workspace. |
| [`apply_template_to_meeting`](https://cotlet.dev/docs/mcp/bluedot/apply_template_to_meeting.md) (Confirm) | Assign a notes template to an existing recording. |
| [`set_collection_template`](https://cotlet.dev/docs/mcp/bluedot/set_collection_template.md) (Confirm) | Set the default notes template of a collection and optionally enforce it. |
| [`add_comment`](https://cotlet.dev/docs/mcp/bluedot/add_comment.md) (Confirm) | Comment on a highlighted line of a recording's transcript. |
| [`share_meeting`](https://cotlet.dev/docs/mcp/bluedot/share_meeting.md) (Confirm) | Share a recording by email or by link. |

---

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.