Krisp MCP Server
Share meetings, file them in folders and assign action items.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/krisp'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Krisp API and MCP server: Let your AI agent share, file and assign in Krisp.
Krisp runs its own MCP server at mcp.krisp.ai, listed in Claude's connector directory since March 2026, and opened a Meeting Assistant API in July 2026 (checked 27 Oct 2026). Both need Core or Advanced. They search meetings, read notes and transcripts, tag meetings and tick off action items. Cotlet runs 11 Krisp tools hosted, 5 of them writes, for the rest: sharing, folders, owners and due dates.
Share meetings, file them in folders and assign action items. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Krisp
- Page: https://cotlet.dev/integrations/krisp-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Krisp. Krisp is a trademark of its owner. If Krisp's own integrations cover what you need, use them first.
What can you automate in Krisp?
- Share client calls with the attendees
- File meetings into client folders
- Give action items an owner and a date
- List your open action items each Monday
- Sum up calls teammates shared with you
- Close meetings open to anyone with the link
Does Krisp have an MCP server or an API?
- Krisp's MCP server has 18 tools. Six change something: add or remove tags, complete one or up to 50 action items, rename speakers and import a recording. None shares a meeting, adds one to a folder or sets an assignee, due date or priority.
- The API has 7 endpoints, all reads plus recording import, at 5 requests a second per account. It skips meetings reached by public link or shared with the whole workspace.
- Zapier has 6 Krisp triggers and no actions. Webhooks send transcripts, notes and action items out; nothing comes back in.
| What you need | Official Krisp MCP | Krisp API, Zapier | Cotlet |
|---|---|---|---|
| Search meetings, read notes and transcripts | Yes | Yes, API | Yes |
| Tag meetings, mark action items done | Yes | No | Yes |
| Share a meeting or change its link access | No | No | Yes, after your OK |
| Add meetings to folders | Lists them only | No | Yes, after your OK |
| Set action item owner, due date, priority | No | No | Yes, after your OK |
| Krisp plan you need | Core or Advanced | Core or Advanced | Core or Advanced |
Checked 27 Oct 2026. Sources: Krisp Help: Krisp MCP, Krisp Help: Krisp MCP supported tools, Krisp Help: Public API, Krisp Meeting Assistant API reference, Krisp Help: Webhook API, Krisp Help: Integrate Krisp with Zapier, Krisp connector in the Claude directory, Krisp pricing
How does Cotlet connect to Krisp?
- Sign in to Krisp. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Krisp password, and no share, folder move or assignment goes through until you approve it.
Connect Krisp 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.
- Enable Krisp for agents. Make a Cotlet account, open Krisp in its Cloud Browser, sign in to app.krisp.ai as yourself and press Enable for agents.
- Add the Cotlet address. Give your agent https://cotlet.dev/mcp/v1 as its MCP server or connector URL.
- Approve the connection. Chat apps send you to a Cotlet sign-in page; Claude Code, Cursor, n8n and scripts use an API key from the console.
One Cotlet address, https://cotlet.dev/mcp/v1, serves Krisp and every other app you enable. It can run next to Krisp's own connector at mcp.krisp.ai; the tool names differ, so your agent can use both. Enabled Krisp after connecting? Refresh the Cotlet connector to load its 11 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: krisp_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: krisp_write
How to use the Krisp REST API
Create your Cotlet API key
Create a Cotlet API key with access to Krisp and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Krisp in Cotlet and enable it for agents. Account access: Your own Krisp account (Core or Advanced plan for the notes features; any role, with folder and sharing rights as Krisp gives them).
Make your first Krisp API request
REST:
curl https://cotlet.dev/api/v1/krisp/meetings \
-H "Authorization: Bearer $COTLET_API_KEY"
Read meetings 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": "krisp",
"tool": "list_meetings",
"result": {
"meetings": [
{
"meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
"title": "Acme weekly sync",
"started_at": "2026-10-21T14:00:00Z",
"duration_minutes": 32,
"tags": [
"Client"
],
"folders": [],
"open_action_items": 4
},
{
"meeting_id": "7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c",
"title": "Lumen onboarding",
"started_at": "2026-10-21T09:30:00Z",
"duration_minutes": 48,
"tags": [],
"folders": [
"Lumen"
],
"open_action_items": 2
}
],
"next_cursor": null
}
}
Returns meetings in the order My Notes shows them, each with its ID, title, start time, duration, tags, folders and the number of open action items. A next_cursor means there are more.
Only your own meetings are listed; meetings shared with you come from list_shared_with_me.
from: Earliest start date, YYYY-MM-DD.
to: Latest start date, YYYY-MM-DD.
cursor: next_cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Krisp workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Returns the notes of one meeting: summary, key points, action items, outline and transcript. Use get_meeting in your configured workspace report. |
| Make | HTTP > Make a request | Lists action items from the Action Items page. Use list_action_items in your configured workspace report. |
| Python or Node.js | REST API | Shows who a meeting is shared with, as the Share dialog does. Use get_meeting_sharing 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 Krisp; 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.
Krisp API endpoints and MCP tools
Meetings and notes
Your own meetings from My Notes, and the ones teammates shared with you. Ask for the transcript only when the summary is not enough; it is the large part.
- List meetings (
list_meetings, read): Your meetings from My Notes, with tags, folders and open action items. - Get meeting (
get_meeting, read): Returns the notes of one meeting: summary, key points, action items, outline and transcript. - List meetings shared with me (
list_shared_with_me, read): Lists meetings that teammates shared with you, the Shared with me page.
Sharing and link access
Only the meeting owner sees the full share list and can change it. People invited by email keep their access whatever the general option is.
- Get meeting sharing (
get_meeting_sharing, read): Shows who a meeting is shared with, as the Share dialog does. - Share meeting (
share_meeting, write, asks first): Invites people by email to a meeting you own. - Set meeting access (
set_meeting_access, write, asks first): Changes the general access option of a meeting you own.
Folders and tags
Only your own meetings go into a folder, and only one where you are Owner or Can collaborate. Tags are shared with the team, 7 per meeting at most.
- List folders (
list_folders, read): Lists your meeting folders in Private and Teamspace. - Add meeting to folder (
add_meeting_to_folder, write, asks first): Adds one of your meetings to a folder. - Tag meeting (
tag_meeting, write): Adds tags to a meeting, or removes them.
Action items
Updates go by item ID, since titles repeat. An assignment lands in the assignee's Activity Center.
- List action items (
list_action_items, read): Lists action items from the Action Items page. - Update action item (
update_action_item, write, asks first): Sets the due date, priority, assignee or completion of an action item.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/krisp-api-mcp-server#tools
Who can see my Krisp session, and how do I revoke it?
- What we store. Your signed-in Krisp dashboard profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 11 Krisp tools. Never your session token.
- What the session sees. What you see in Krisp: your calls, shared calls, transcripts, recordings.
- What no tool touches. Recording, audio settings, seats, billing, deletes.
- If Krisp signs you out. You sign in again yourself in the same Cloud Browser.
- How to cut access. Disable for agents or reset the browser. The next call stops.
Transcripts hold what clients and colleagues said, so check your own policy before an agent reads them. Krisp offers a SOC 2 report on Enterprise. Cotlet has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads yesterday's calls. Titles, participants and summaries from My Notes.
- Matches your rule. Client name or email domain picks who gets the call.
- Checks who has it. Skips people who already have access, and open links.
- Waits, then shares. Each invite shows up in your Cotlet console first.
| Action | Undo |
|---|---|
| Tag a meeting | Yes, tag_meeting with remove |
| Set owner, date or priority | Yes, set the old values; the assignee was already notified |
| Add to a folder | Remove it in Krisp; folder members may have opened it |
| Change link access | Yes, set the old option back |
| Share by email | No, the invite email is already sent |
4 of 11 tools ask first: share_meeting, set_meeting_access, add_meeting_to_folder and update_action_item. Each one reaches another person, by email, by a folder they belong to or in their Activity Center. Tags reach nobody, so tag_meeting runs at once. Turn the wait off per tool once a rule has run clean for a week.
A Teamspace folder is visible to your whole Krisp team. The agent names the space of each folder before it files a meeting there.
MCP call:
{
"name": "share_meeting",
"arguments": {
"meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
"emails": [
"dana@acme-example.com"
],
"access": "can_view"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/krisp/meetings/3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a/share \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"emails":["dana@acme-example.com"],"access":"can_view"}'
Response:
{
"meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
"invited": [
{
"email": "dana@acme-example.com",
"access": "can_view",
"status": "invited"
}
]
}
Scripts reach the same tools over REST at /api/v1/krisp, with the same key and price. A Krisp webhook on "Transcript created" can start a script that calls share_meeting for the new meeting. A share on a meeting you do not own fails, and failed calls are free. Each tool row above lists its REST path.
How much does the Krisp MCP server cost?
About $35 a month for one person with about 12 recorded calls a week, 6,020 credits, on top of the Krisp plan.
| Job | Calls | Credits |
|---|---|---|
| Share client calls with attendees, each workday | 5 × 22 | 1,100 |
| Owners and due dates on new action items, each workday | 6 × 22 | 1,320 |
| File and tag the week's calls | 32 × 4 | 1,280 |
| Monday list of open action items | 4 × 4 | 160 |
| Key points of calls shared with you, each workday | 3 × 22 | 660 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 6,020 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Krisp Core is $16 a month, or $8 billed yearly
Krisp publishes no meetings per user, and reviews use 5 to 10 a week as a typical profile, so the month is our example: 12 recorded calls a week, 6 with clients. Krisp's own MCP server costs nothing extra on Core; use it for questions about your calls. Dollars at the $29 pack rate.
Krisp MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Krisp MCP | Krisp's own hosted server, 18 tools: search, transcripts, action items, tags, speakers, import, upcoming meetings. | Cannot share, change link access, file into folders or assign. Core or Advanced. |
| rhdeck/krisp-cli | Command line over Krisp's MCP server, one subcommand per tool. MIT, 0 stars, last commit 20 Apr 2026. | Same tools as the official server. |
| Aeroverra/KrispDownloader | Exports meeting details, transcripts and recordings to files. 3 stars, last commit 20 May 2026. | Runs on a bearer token you copy from DevTools; export only, no MCP. |
| Krisp on Zapier | 6 triggers, from action items generated to transcript shared. | No actions: it sends data out and changes nothing in Krisp. |
We found no community Krisp MCP server that writes. If you only ask questions about your calls, Krisp's connector does it with the plan you pay for. If new action items should land in Jira or Slack, Zapier or a webhook covers it. If the agent should share, file and assign after each call, Cotlet does that next to the official server.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and run by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the Krisp tools.
Krisp API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Krisp under Integrations in the console and sign in to Krisp in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect Krisp to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Krisp 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 Krisp account through Cotlet, in their phone apps too.
What can ChatGPT do in Krisp?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Krisp: share meeting notes after calls; organize meetings into folders and tags; assign action items with owners and due dates. You ask in plain words, and anything that reaches other people waits for your OK first.
Which Krisp plan do I need?
Krisp's own MCP server and Webhook API are for the Core and Advanced plans (Krisp Help, checked 22 Oct 2026). Cotlet works in your Krisp account dashboard, so it sees what your plan and role show there. Features such as the Outline need Core, and a call fails with a clear error when your plan or role does not allow the action.
Does Cotlet record meetings?
No. Krisp records and transcribes in its own app, and each recorded meeting is saved to your account dashboard. Cotlet works with those saved meetings: it reads them, shares them, files them and updates their action items. Nothing changes your Krisp app, audio settings or billing.
Can I use it next to Krisp's own MCP server?
Yes. Add both connectors: let mcp.krisp.ai answer questions and tag, and let Cotlet share, file and assign. They do not touch each other.
Does Krisp have webhooks?
Yes, on Core and Advanced: transcript created, note generated, transcript shared, recording available, and action items, key points or outline alone. Advanced adds a team webhook. Cotlet sends no events; point a webhook at a script that calls the Cotlet tools, or run your agent on a schedule.
Is the MCP server different from the REST API?
Only in how you call it. Both carry the same 11 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and webhook handlers use REST.
Is Cotlet affiliated with Krisp?
No. Cotlet is independent and not affiliated with Krisp Technologies, Inc.
Can I use the Krisp 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.