Bluedot MCP Server

Organiza, crea plantillas, comenta y comparte reuniones de Bluedot; también lee las transcripciones.

Servidor MCP alojado

npx add-mcp 'https://cotlet.dev/mcp/v1/bluedot'

Se instala en Claude Code, Codex, Cursor y más

Documentación

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Bluedot API and MCP server: Let your AI agent tidy up after every Bluedot call.

Yes, Bluedot runs its own remote MCP server, also listed as a Claude connector and a ChatGPT plugin (checked 27 Oct 2026). Its 8 tools only read meetings, transcripts, summaries, collections and participants, and it needs Basic or higher. There is no REST API, and nothing official moves, templates, comments on or shares a recording. Cotlet runs 14 Bluedot tools hosted, the reads plus those 7 writes.

Organize, template, comment on and share Bluedot meetings; read transcripts too. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Bluedot. Bluedot is a trademark of its owner. If Bluedot's own integrations cover what you need, use them first.

What can you automate in Bluedot?

  • File recordings into collections
  • Re-note old calls with a new template
  • Comment on promises and @mention owners
  • Share calls with outside attendees
  • Find what a customer said and when
  • Send a weekly digest of customer calls

Does Bluedot have an MCP server or an API?

  • If your agent only needs to read and search meetings, Bluedot's own connector does it on any paid plan at no extra cost.
  • Webhooks (Svix) and the Zapier and Make apps fire when a summary or transcript is ready. Zapier has 2 triggers and no action.
  • The help page says of the official server: "No additional permissions are granted through MCP."
What you needBluedot MCPZapier, MakeCotlet
Read summaries and transcriptsYesNew ones, as triggersYes
Search transcriptsYesNoYes
Read comments and templatesNoNoYes
File into collectionsNoNoYes, after your OK
Apply a template to old callsNoNoYes, after your OK
Comment and shareNoNoYes, after your OK
Bluedot planBasic or higherAny, Free tooAny; templates need Pro

Checked 27 Oct 2026. Sources: Bluedot MCP Overview (Bluedot Help Center), How to Connect Bluedot to ChatGPT, How to Set Up Webhooks in Bluedot, Bluedot on Zapier, Bluedot pricing

How does Cotlet connect to Bluedot?

  1. Sign in to Bluedot. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Bluedot password, and no move, template change, comment or share that teammates or attendees would see happens before you approve it.

Connect Bluedot to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Open Bluedot in a Cloud Browser. Make a Cotlet account, open Bluedot in its Cloud Browser, sign in with the Bluedot login you record with and press Enable for agents.
  2. Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 where your agent takes an MCP server or a custom connector.
  3. Approve the link. Claude and ChatGPT show a Cotlet sign-in page. Cursor, Codex, n8n and scripts send an API key from the console.

Every app you enable in Cotlet sits behind https://cotlet.dev/mcp/v1, Bluedot too. You can keep Bluedot's own connector next to it; enable Bluedot in Cotlet later and refresh the connector to see the new tools.

Claude:

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"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

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

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: bluedot_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: bluedot_write

How to use the Bluedot REST API

Create your Cotlet API key

Create a Cotlet API key with access to Bluedot and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Bluedot in Cotlet and enable it for agents. Account access: Your own Bluedot account (any role: Owner, Admin or Member; custom templates need the Pro plan, workspace settings need Owner or Admin).

Make your first Bluedot API request

REST:

curl https://cotlet.dev/api/v1/bluedot/workspaces \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read workspaces and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "bluedot",
  "tool": "list_workspaces",
  "result": {
    "workspaces": [
      {
        "workspace_id": "w_90c1d7",
        "name": "Northwind Sales",
        "role": "admin"
      },
      {
        "workspace_id": "w_3a4be2",
        "name": "Personal",
        "role": "owner"
      }
    ]
  }
}

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.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Bluedot workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestList recordings, newest first, filtered by collection, date, uploader or participant. Use list_meetings in your configured workspace report.
MakeHTTP > Make a requestGet one recording with its summary, transcript and participants. Use get_meeting in your configured workspace report.
Python or Node.jsREST APIList the comments on one recording's transcript. Use list_comments in your configured workspace report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Bluedot; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Bluedot API endpoints and MCP tools

Meetings and transcripts

Bluedot's own MCP server has these four reads too. Another member's private recording is missing for every role, Owner included.

  • List workspaces (list_workspaces, read): List the Bluedot workspaces your account belongs to.
  • List meetings (list_meetings, read): List recordings, newest first, filtered by collection, date, uploader or participant.
  • Search meetings (search_meetings, read): Search transcripts, titles and descriptions across your recordings.
  • Get meeting (get_meeting, read): Get one recording with its summary, transcript and participants.

Collections

A move shows the recording to everyone with access to the collection and can post its notes to Slack. No tool deletes a collection, because Bluedot deletes the recordings inside it.

  • List collections (list_collections, read): List collections and sub-collections with your access level in each.
  • Move meeting to collection (move_meeting_to_collection, write, asks first): Move one recording into a collection.
  • Create collection (create_collection, write, asks first): Create a collection or a sub-collection.
  • Set collection template (set_collection_template, write, asks first): Set the default notes template of a collection and optionally enforce it.

Notes templates

Custom templates need Bluedot Pro. An enforced collection template reaches new meetings only; old ones need apply_template_to_meeting.

  • List notes templates (list_templates, read): List the notes templates in Workspace Settings > Templates.
  • Create notes template (create_template, write, asks first): Add a custom notes template to the workspace.
  • Apply template to meeting (apply_template_to_meeting, write, asks first): Assign a notes template to an existing recording.

Comments and sharing

A posted comment cannot be edited, and an @mention notifies the teammate at once. An admin can turn sharing off for members.

  • List comments (list_comments, read): List the comments on one recording's transcript.
  • Add comment (add_comment, write, asks first): Comment on a highlighted line of a recording's transcript.
  • Share meeting (share_meeting, write, asks first): Share a recording by email or by link.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/bluedot-api-mcp-server#tools

Who can see my Bluedot session, and how do I revoke it?

  • What we store. Your signed-in Bluedot profile, encrypted with AES-256-GCM, in Finland. Never the password.
  • What your agent gets. 14 Bluedot tools. No cookie, no login, no recording files.
  • What the session sees. The recordings and collections your Bluedot user can open, and nothing private to others.
  • What no tool touches. Billing, recording, deleting, retention, members and workspace settings.
  • If Bluedot signs you out. We email you a sign-in link, and you sign in again yourself.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.

Bluedot itself states SOC 2 Type II and EU data residency (bluedothq.com/security, read 27 Oct 2026). The site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). Transcripts carry other people's words, so getting their consent to record stays with you, as Bluedot's terms say.

Approvals, undo and mistakes

  1. Lists the template. Checks that the template you named is in Workspace Settings > Templates.
  2. Counts the calls. Says how many recordings in the range would get new notes.
  3. Tries one. Applies it to a single call, after your OK, and shows you the new notes.
  4. Does the rest. Each call waits in your Cotlet console; view-only ones are reported, not retried.
ActionUndo
Move to a collectionMove it back; a Slack post from that collection stays
Apply a templateApply the old one; the notes are written again
Set a collection templateSet the old one; notes made meanwhile keep the new one
Create a collection or templateRemove it in Bluedot; an empty collection deletes nothing
Add a commentDelete it in Bluedot; the @mention was already sent
Share a recordingTurn the link off; invitees already have the email

All 7 write tools ask first, because each one reaches someone: collection members, Slack, a mentioned teammate or an attendee. The 7 reads run at once. For a scheduled run you can switch the wait off per tool, for example for moves into a private collection.

Bluedot cannot edit a posted comment, so the agent reads list_comments first and skips a line that already has one.

MCP call:

{
  "name": "create_collection",
  "arguments": {
    "workspace_id": "w_90c1d7",
    "title": "Acme",
    "everyone_access": "can_view"
  }
}

REST:

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"}'

Response:

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

A script that sets up a collection per new client in your CRM can call the same tools over REST at /api/v1/bluedot, with one key and one price. A call your Bluedot role does not allow returns an error and costs nothing. Every tool row above lists its REST path.

How much does the Bluedot MCP server cost?

About $39 a month for a sales team of 5 that records on Bluedot Pro, 6,790 credits. Pro itself is $20 a recording user a month billed yearly, $25 monthly.

JobCallsCredits
File the day's recordings, each workday9 × 221,980
Comment on promises in yesterday's calls10 × 222,200
Weekly digest of customer calls13 × 4520
Share a call with outside attendees2 × 20400
Collection and template for a new client3 × 260
New template on last month's calls13 × 1130
Cloud Browser, 30 days1,500
Total6,790
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Reads alone cost nothing with Bluedot's own connector

The month is our example: 5 people, the day's recordings filed and yesterday's promises commented on each workday, a weekly digest, 20 shares, two new clients and one template change. Bluedot publishes no typical account; 70% of its G2 reviews come from small businesses. Dollars at the $29 pack rate.

Bluedot MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Twiso/bluedot-cursor-pluginCursor skills and slash commands on top of Bluedot's own MCP server. MIT, 0 stars, last push 6 Sep 2026.Same 8 reads; it does not add a server.
jchu96/frame-of-mindA local screen-recording analyst that can pull Bluedot meetings through the official MCP. MIT, 4 stars, last push 12 Oct 2026.Reads only, built for its own reports.
Svix webhooksBluedot sends each finished summary and transcript to your endpoint, with retries.Out only; the team version needs Business and a request to support.

If you want Claude or ChatGPT to answer questions from your calls, use Bluedot's own connector. If finished notes should land in a CRM or a doc, webhooks or Zapier do it. If your agent should also file, re-template, comment on and share recordings, Cotlet does that hosted.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Bluedot tools go to contact@cotlet.dev.

Bluedot API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Bluedot under Integrations in the console and sign in to Bluedot in its Cloud Browser. The trial starts when you sign up, no card.

How do I connect Bluedot to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Bluedot once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Bluedot account through Cotlet, in their phone apps too.

What can ChatGPT do in Bluedot?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Bluedot: sort meetings into collections; apply a notes template to past meetings; comment on action items in transcripts. You ask in plain words, and anything that reaches other people waits for your OK first.

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.

Should I use Bluedot's own MCP server instead?

For reading and searching meetings, yes: it is official and included from Basic. Cotlet adds what it cannot do: comments and templates to read, and moves, templates, comments and shares to write. You can connect both.

Does Cotlet record my meetings?

No. Bluedot records through its extension and apps as before. The tools work on recordings that already exist in your account.

Is the MCP server different from the REST API?

Only in how you call it. Both have the same 14 tools, inputs and answers, with one API key and one price.

Is Cotlet affiliated with Bluedot?

No. Cotlet is independent and not affiliated with Bluedot.

Can I use the Bluedot API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

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.