Krisp MCP connector
Connect Krisp to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can search your meeting transcripts, pull notes, tick off action items and file recordings, each person working inside their own Krisp access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Krisp to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Krisp once
-
Open Connections, choose Add connection, and pick Krisp.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Krisp. Krisp's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Krisp MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Krisp MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Krisp MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Krisp to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Krisp through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch up on a call before following up
Ask for the transcript and action items from yesterday's call with a prospect, then draft the follow-up from what was actually said rather than what you remember.
-
Customer success
Close out action items after a renewal review
List the open action items from the quarterly review, mark the ones already handled as complete, and keep the rest in front of the team.
-
Support
Find every call where a bug came up
Search meeting content for a product name or an error message, and pull the matching conversations together for the engineering handoff.
-
Product
Pull themes from a week of interviews
Fetch the notes from several user interviews at once, tag them by feature, and summarize what people kept asking for.
-
Recruiting
File interview recordings in the right folder
Import a recording from another source, check that it finished processing, correct the speaker names, and tag it with the role.
-
Leadership
Know what is next and what was decided
List today's upcoming meetings, then revisit the recent ones that matter to find decisions and owners without rewatching an hour of video.
Try asking
- “Summarize open action items from this week's customer calls”
- “Find every meeting where pricing came up last month”
- “Tag yesterday's standup as engineering and file it in Q3”
Compare
Elaichi vs Zapier MCP vs Composio for Krisp
All three can connect Krisp to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Krisp tools | Allow or restrict single Krisp tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Krisp call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Krisp tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Krisp, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Krisp builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Krisp gets you
6 screens from the product, each doing one job for your Krisp account.
The agent
Ask about any Krisp meeting in plain language.
Answers come from live transcripts, notes and action items, not a stale export.
- meetings
- action items
- folders
- tags
Ask Elaichi to work across your apps.
Summarize open action items from this week's customer calls
Find every meeting where pricing came up last month
Tag yesterday's standup as engineering and file it in Q3
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one governed endpoint.
Connect Krisp once and every MCP client works through it, no SDK, no shared key.
Copy the endpoint
Tool catalog
18 ways to work your Krisp meetings.
Meetings, transcripts, action items, folders, tags and speakers covered, with no custom code to write.
- Search meetings
- Search meeting content
- Get multiple documents
- List action items
Toolboxes
Every team gets its own Krisp toolbox.
Sales sees call notes, Success sees action items, each toolbox scoped to one team.
- Sales
- Customer success
- Support
- Product
Shared connections
Teammates use the Krisp connection, never the credential.
One person connects Krisp, shares it with teams, and nobody else handles a sign-in.
- Sales EMEA
- Customer success
- Support
- Product research
Audit log
Every Krisp call answers who did what.
When, who, what happened and which meeting, kept in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Krisp meetings into a digest.
Yesterday's meetings are fetched, grouped, drafted, approved by a person, then posted back to Krisp.
Krisp digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch meetings
Krisp
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Krisp
Queued
Collections and dashboards
Krisp meeting health, computed without a model.
Four metrics, 14 days of meetings created and a team breakdown, refreshed on schedule.
Krisp health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Action items
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Customer success 27%
Support 21%
Product research 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Krisp to Claude?
Connect Krisp in Elaichi first: you sign in to Krisp over OAuth and approve the connection, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi and your Krisp meetings are available in the conversation.
Does Krisp work with ChatGPT and Cursor as well as Claude?
Yes. Krisp is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Krisp meetings?
It can search your Krisp meetings and the words inside them, pull the notes from several meetings at once, list open action items and mark them complete, file meetings into folders, add or remove tags, correct speaker names, import a recording and check whether it has finished, and tell you what is on the calendar next. Short, concrete asks work best, such as the action items from Tuesday's call rather than a long paragraph.
Does connecting Krisp give the AI every meeting in the workspace?
No. Access follows the person who signed in, so the AI only sees the Krisp meetings, folders and action items that person can already open in Krisp. Elaichi can narrow that further for a team or a role, but it can never widen it beyond what Krisp itself allows.
Can I stop an agent from changing things in Krisp?
Yes. Restrictions in Elaichi work per action, so you can allow searching Krisp meetings and reading notes while blocking tagging, speaker changes, imports or completing action items. A restricted action is never shown to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Krisp connection when someone leaves?
Offboarding a person in Elaichi ends their access to Krisp through every client at once. A Krisp connection that was shared with a team keeps working for everyone else on it. If you want the connection gone entirely, disconnecting Krisp once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Krisp MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Krisp is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Krisp?
Yes. Both let Claude, ChatGPT or Cursor use Krisp. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Krisp call.
How is Elaichi different from Composio for Krisp?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Krisp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Krisp in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.