Krisp
by Krisp
Search Krisp meeting transcripts, notes and action items from an AI agent. Anthropic lists 7 read-only tools; Krisp's own tool page documents 6 and the names do not fully agree. OAuth 2.0 with PKCE, and the descriptor advertises a write scope no tool carries.
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.
Connect Krisp via MCP
https://mcp.krisp.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Krisp Tools & Capabilities (7)
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::writeanduser::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_documenton one side andget_multiple_documentsplusget_user_preferenceson the other. Krisp's own overview article names a tool its own tool page omits. get_user_preferencesis 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 ownwww-authenticateheader 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
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.
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.
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.
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.
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.
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.
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.
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
- Krisp MCP: Supported tools (retrieved 2026-08-23, via the Zendesk
help_centerJSON API after the HTML returned 403 to our client) · retrieved 2026-08-23 - Krisp MCP overview (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp MCP: Integrating your own MCP client (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp Meeting Assistant API documentation and
llms.txtindex — · · (retrieved 2026-08-23). That host'srobots.txtcarriesContent-Signal: ai-train=no, search=yes, ai-input=yes— AI synthesis expressly permitted. · retrieved 2026-08-23 - Krisp Public API help article (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp Sharing your meetings (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp Manager View, External Meeting Sharing (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp Invite to collaborate after meetings (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp AI Meeting Assistant FAQ (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp privacy policy, storage and retention (retrieved 2026-08-23) · retrieved 2026-08-23
- Krisp product index,
llms.txt(retrieved 2026-08-23), source of the bot-free recording claim · retrieved 2026-08-23 - Live OAuth posture check: anonymous initialize returned HTTP 401 with a
www-authenticateBearer challenge naminghttps://mcp.krisp.ai/.well-known/oauth-protected-resource; that descriptor and the authorization server metadata athttps://mcp.krisp.ai/.well-known/oauth-authorization-serverwere both read (2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Krisp support — <mailto:support@krisp.ai> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Krisp
- Tools
- 7
- Domain
- mcp.krisp.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.