Krisp

Search Krisp transcripts, notes and action items.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Krisp connector does

The Krisp MCP server connects your Krisp meeting history — transcripts, AI notes, action items and upcoming calendar meetings — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists seven tools and all seven read. Sign-in is OAuth 2.0 with PKCE, and Krisp gates the server behind its paid Core and Advanced plans.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Krisp tools (7)

  • date_time
  • get_multiple_documents
  • get_user_preferences
  • list_action_items
  • list_activities
  • list_upcoming_meetings
  • search_meetings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The scope list names two verbs no tool carries. The resource descriptor advertises user::meetings:metadata::write and user::recording::import. Nothing in the seven tool names accounts for either. A clean read-only verb census is therefore not a safety result here.
  • The two tool lists disagree by name. Krisp documents six tools and Anthropic lists seven, with get_document on one side and get_multiple_documents plus get_user_preferences on the other. Krisp's own overview article names a tool its own tool page omits.
  • get_user_preferences is undocumented. It appears in Anthropic's listing and in no Krisp page we could find. We could not establish what it returns.
  • We could not read tool schemas or safety annotations. The endpoint returned HTTP 401 to an anonymous request, so no parameter-level detail or vendor annotation is published here.
  • Krisp's documented OAuth discovery path does not exist. Its client-integration article tells developers to fetch https://mcp.krisp.ai/mcp/.well-known/oauth-protected-resource. That path returned 404 on 2026-08-23; the working document is at the host root, which is what the server's own www-authenticate header points to. The same article also cites "RFC 9470" for Protected Resource Metadata, which is RFC 9728.
  • There is no delete, edit or correction path. No tool can remove a transcript, redact a passage or fix a misattributed speaker. Everything an agent reads it reads as-is, and Krisp routes deletion through its dashboard or a support email.
  • Retention is open-ended. Krisp publishes no expiry for transcripts or notes, storing them until you request deletion. The connector inherits that horizon.
  • Rate limits for MCP are unpublished. Krisp documents 5 req/s with a 25-per-5s burst for its Meeting API, per account rather than per key. Whether the MCP server shares that budget is not stated.
  • The connector needs a paid plan. Core or Advanced. There is no free tier for this server.
  • Whether Auto-Share widens the read surface without your knowledge is a real risk, not a hypothetical. Krisp states Auto-Share defaults to ON, and that meetings shared to you are visible to a key that acts as you. We found no way to scope the connector to only meetings you recorded.

Frequently asked questions

Can the Krisp connector share or send a meeting summary to anyone?

No tool among the seven sends, shares or emails anything. All seven read. Krisp's platform does share meetings by email, link and auto-share to calendar invitees, and its Manager View shares externally, but those are dashboard and admin features with no counterpart in this tool listing. The connector reads what sharing has already produced.

What personal data does the Krisp MCP server expose to an agent?

Verbatim speech by everyone in your meetings, attributed by name. Krisp's Meeting API schema returns a participant record carrying email, first name, last name and avatar URL, and transcript segments are documented as verbatim from the source. Those participants include people outside your company who never agreed to an agent reading them.

How long does Krisp keep meeting transcripts?

Indefinitely, until you ask for deletion. Krisp's privacy policy states it stores recordings and meeting notes until you instruct it to delete them or close your account, and directs deletion requests to support@krisp.ai. There is no published time-based expiry, so the connector's reach grows with every meeting you record.

Does the Krisp MCP server request any write permission?

Yes, two. The server's own RFC 9728 descriptor advertises user::meetings:metadata::write and user::recording::import alongside six read scopes, on 2026-08-23. No tool name among the seven carries a write, import or upload verb, so those two scopes name capability the published tool list does not account for.

How many tools does the Krisp MCP server actually have?

Anthropic lists seven and Krisp documents six, and the two lists disagree by name. Krisp's supported-tools page describes get_document; the directory lists get_multiple_documents and get_user_preferences instead. Krisp's own MCP overview article names get_multiple_documents in troubleshooting, so its tool page is behind its own product.

Does anyone in the meeting know Krisp is recording them?

Not from Krisp. Krisp markets bot-free recording and states plainly that no bot joins the meeting while it records, and its FAQ confirms you need not invite a Krisp user to transcribe. Notice to other participants is therefore entirely your responsibility, in every jurisdiction where it is required.

What do I need before connecting Krisp to Claude?

A paid Krisp plan and an OAuth sign-in. Krisp documents the MCP server as available on the Core and Advanced plans, and connection uses OAuth 2.0 authorization code flow with PKCE, completed when your client prompts. Krisp also states only Streamable HTTP is supported and that SSE will not work.

Are there rate limits on Krisp meeting data?

Krisp publishes none for MCP specifically. Its Meeting API documents 5 requests per second with a 25-per-5-second burst, enforced per account rather than per key, returning HTTP 429 when exceeded. Krisp does not state whether the MCP server shares that budget, so treat it as an unpublished limit.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Krisp to work.

Connect Krisp once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.