# 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. Source: https://elaichi.ai/connectors/krisp/ ## Facts | | | | --- | --- | | Application | Krisp | | Category | Conversational Intelligence | | AI tools | 18 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. Krisp builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | help.krisp.ai/hc/en-us/requests/new | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Krisp is connected - 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 ## Connect Krisp in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Krisp. 2. Optionally set Share with, then press Connect. 3. Approve it in Krisp. Krisp's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Krisp tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Krisp MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Krisp to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Krisp tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Krisp through Elaichi ### Catch up on a call before following up Sales. 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. ### Close out action items after a renewal review Customer success. 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. ### Find every call where a bug came up Support. Search meeting content for a product name or an error message, and pull the matching conversations together for the engineering handoff. ### Pull themes from a week of interviews Product. Fetch the notes from several user interviews at once, tag them by feature, and summarize what people kept asking for. ### File interview recordings in the right folder Recruiting. Import a recording from another source, check that it finished processing, correct the speaker names, and tag it with the role. ### Know what is next and what was decided Leadership. List today's upcoming meetings, then revisit the recent ones that matter to find decisions and owners without rewatching an hour of video. ## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 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 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. ## All 18 Krisp tools Every tool below is callable through https://api.elaichi.ai/mcp once Krisp is connected, subject to the toolbox it is in and the restrictions on the caller. - **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. - **Complete action items** (Complete). Mark up to 50 action items done, or not done, in one go. If some items fail, the rest still go through and the result names the ones that did not. - **List folders** (List). List or search your meeting folders. Returns each folder's name, description, visibility (private or teamspace), your role on it, and how many meetings and members it has. Use it to find a folder by name or to resolve a folder ID. - **Get folder** (Get). Open one folder: its details and the meetings filed in it. Use it to answer questions about "this folder," then fetch the meetings you need with "get_multiple_documents". - **List tags** (List). List or search your tags, including which ones you use most. Returns each tag's name, color and ID. Use it first when you want to filter meetings by tag, then pass the tags to "search_meetings". - **Attach tag** (Action). Add tags to meetings by name, one meeting or many in a single request. A tag name that does not exist yet is created and shared with your team, the same as creating one in the app. A meeting holds at most 7 tags in total, so 1 to 3 precise tags per meeting works best. - **Detach tag** (Action). Remove tags from meetings by name, across as many meetings as you want. The tag itself stays in your workspace, it is only removed from those meetings. - **Bulk update speakers** (Update). Replace "Speaker 1" style labels in a meeting's transcript with real names, one speaker at a time or all of them at once. The transcript and the summary both update, the same as renaming a speaker in the app. You can add an email to link a speaker to a known contact. - **Import recording** (Import). Import an existing audio or video recording as a new Krisp meeting. The tool returns a one-time upload link rather than uploading the file itself; your AI tool sends the file to that link, and that upload alone creates the meeting and starts transcription. Supported files are… - **Get import status** (Get). Check an import started with "import_recording". Status is uploading, processing, ready, or failed with the reason. Once it is ready you get the meeting ID; the transcript can take a few more minutes to appear after that. - **List upcoming meetings** (List). List upcoming calendar meetings for the next 1–14 days, with title, time, status, organizer, participants, whether the meeting is recurring or has external participants, and the video conferencing link. - **List activities** (List). List items from the Activity Center: notifications, action item assignments, meeting summaries, and other updates, newest first, each with a link into Krisp and a count of unread items. - **Get user preferences** (Get). Read your display preferences: name, timezone, and company. AI tools use these to get dates, times and names right in their answers. - **Date time** (Action). Get current date/time or enumerate dates in a range. Use whenever you need exact date/time information instead of guessing.