Skip to content

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
Claude Elaichi connected

Summarize open action items from this week's customer calls

Working in Krisp with Elaichi

  • Search meetings
  • Search meeting content
  • Get multiple documents
Ask anything…
Governance / Audit log Last 24 hours
Krisp Get multiple documents Emily Carter · Claude · 9:41 AM Done
Krisp Search meeting content Emily Carter · Claude · 9:41 AM Done
Krisp Search meetings Emily Carter · Claude · 9:41 AM Done
Krisp List action items Megan Brooks · ChatGPT · 9:38 AM Done
Krisp Complete action item Ryan Hayes · Cursor · 9:35 AM Done

How to connect Krisp to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Krisp MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 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. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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”

See all 18 Krisp tools →

What connecting Krisp gets you

6 screens from Elaichi, each doing one job for your Krisp account.

Elaichi Agent

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.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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.

ElaichiTools
Tool Action Description
Search meetings Search Search meetings by text or retrieve by meeting ID(s). Returns metadata, summaries, key points, and action items. Filter by date range, tag, folder, speaker, participant email domain, duration, recurring meetings, or meetings you own versus ones shared with you. Use…
Search meeting content Search Full-text search inside meeting content across every meeting you can access: transcripts, agendas, and notes. Returns the matching passage from each meeting with its document ID and date, one result per meeting. Search terms need at least 3 characters. Narrow by date range, or…
Get multiple documents Get Fetch one or more documents by their 32-character IDs (meeting, agenda, transcript, etc.) and choose which parts you want: notes, summary, key points, action items, tags, a recording download link, or the full transcript. Summaries, key points, action items and tags are light,…
List action items List List action items (tasks and follow-ups) from meetings, with their assignee, due date, completion status, and source meeting. Filter by completion status, by items assigned to you, by a single meeting, or by folder. Each item comes back with its own ID, which is what you need…
Complete action item Complete Mark one action item done, or reopen one that was already marked done. It works by action item ID from "list_action_items", not by title, because titles are not unique.

Tool catalog

18 ways to work your Krisp meetings.

Meetings, transcripts, action items, folders, tags and speakers covered, with no custom code to write.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Krisp · customer calls and action items

Krisp starter 18 Mar 4, 2026

Customer success toolbox

Krisp · renewal reviews and follow-ups

— 9 Mar 2, 2026

Support toolbox

Krisp · escalation calls and notes

— 24 Feb 27, 2026

Product toolbox

Krisp · user interviews and feedback

Krisp starter 6 Feb 19, 2026

Recruiting toolbox

Krisp · interview recordings and tags

— 31 Jan 30, 2026

Leadership toolbox

Krisp · meeting digests and decisions

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Krisp toolbox.

Sales sees call notes, Success sees action items, each toolbox scoped to one team.

ElaichiConnections
Connection Scope Status Access
KR

Krisp (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
KR

Krisp (Customer success)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
KR

Krisp (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
KR

Krisp (Product research)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
KR

Krisp (Recruiting)

Connected by Ryan Hayes

Personal • Active Not shared
KR

Krisp (Exec team)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Krisp Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Krisp Meetings Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Krisp Meetings List Toolbox

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch meetings

    Krisp

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. 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

Live

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.

    help.krisp.ai/hc/en-us/requests/new

Why run a vendor's MCP server through Elaichi →

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.

Elaichi compared with Zapier MCP and Composio for Krisp, by what to check
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.

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 my team share one Krisp connection?

Yes. One person connects Krisp in Elaichi and shares it with a team, and nobody else ever handles a Krisp credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every search and every completed action item.

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