Krisp MCP connector
Connect Krisp to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize open action items from this week's customer calls
Working in Krisp with Elaichi
-
Search meetings
-
Search meeting content
-
Get multiple documents
How to connect Krisp to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Krisp MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Krisp through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Krisp is logged.
-
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”
What connecting Krisp gets you
6 screens from Elaichi, each doing one job for your Krisp account.
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, Cursor or Microsoft Copilot
The agent
Ask about any Krisp meeting in plain language.
Answers come from live transcripts, notes and action items, not a stale export.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint.
Connect Krisp once and every MCP client works through it, no SDK, no shared key.
Tool catalog
18 ways to work your Krisp meetings.
Meetings, transcripts, action items, folders, tags and speakers covered, with no custom code to write.
Toolboxes
Every team gets its own Krisp toolbox.
Sales sees call notes, Success sees action items, each toolbox scoped to one team.
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.
Audit log
Every Krisp call answers who did what.
When, who, what happened and which meeting, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Krisp
Queued
Workflows
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 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%
Collections and dashboards
Krisp meeting health, computed without a model.
Four metrics, 14 days of meetings created and a team breakdown, refreshed on schedule.
Why connect Krisp's MCP server through Elaichi
Krisp builds and runs this MCP server. Elaichi sits in front of it, so Krisp's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Krisp's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Krisp's tools at the same Elaichi address as every other connected app. Nobody adds Krisp's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Krisp sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Krisp's server. By default, a tool Krisp does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Krisp
Krisp builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Krisp team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 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 restricting tagging, speaker changes, imports or completing action items. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot