How to connect meeting notes to Claude, ChatGPT and other AI assistants with MCP

How to connect meeting notes to Claude, ChatGPT and other AI assistants with MCP
Share this post
Get Krisp for Free

Most people still feed meeting notes to their AI assistant by hand. A client call ends, Claude opens for the follow-up email, and the transcript gets pasted in before any real work starts. The same routine repeats an hour later in ChatGPT, this time for a different project. Your assistant ends up knowing only what you remembered to paste.

Krisp offers a shorter route. Its hosted MCP server gives Claude, ChatGPT, Cursor, VS Code, Gemini, Grok and Meta Muse direct access to your meeting notes through a single URL. The assistant can then search past meetings, read transcripts and summaries, and update your action items whenever you ask.

This guide walks through how to connect meeting notes to Claude and each of the other assistants. It also covers the first prompts worth trying and what the assistant is allowed to change. The last part deals with the errors people run into most often.

The short answer

Krisp’s MCP server lives at https://mcp.krisp.ai/mcp, and every assistant connects to it with your Krisp sign-in. Claude and ChatGPT need a single click from Settings → Integrations in the Krisp app, and Cursor has its own Add to Cursor button. Grok, Gemini and Meta Muse accept the URL as a custom connector. Krisp MCP comes with every paid plan: Core, Advanced and Enterprise.

Where to add Krisp in each AI assistant

All of these assistants talk to the same Krisp MCP server. The only differences are where the setup starts and how many clicks it takes.

Assistant Where you start How it connects Good to know
Claude (web and desktop app) Krisp app: Settings → Integrations → Claude card One click, then a Krisp sign-in Claude opens Krisp in its connector directory
Claude Code Your terminal One command, then /mcp to sign in Useful for coding and agent workflows
ChatGPT Krisp app: Settings → Integrations → ChatGPT card One click, then a few steps in ChatGPT Ends with a Krisp sign-in and an access request
Cursor Krisp app: Settings → Integrations → Add to Cursor One click, or a pasted JSON config A project-level config shares the setup with your team
Grok grok.com/connectors The URL as a custom connector Open to all Grok users. On Grok Business and Enterprise, an admin adds the connector first
Gemini gemini.google.com: Settings → Connected Apps A custom app with the URL Personal Google accounts in the US, 18 and over, in English
Meta Muse A chat in the Muse app (web, iOS or Android) A request to Muse to create a custom connector Adults in the US, Canada, Japan and Singapore
VS Code Command Palette → MCP: Add Server The pasted URL A Krisp sign-in appears when prompted

What does an MCP connector for meeting notes actually do?

An MCP connector for meeting notes lets your AI assistant look up meetings on its own. It no longer depends on whatever ended up in the chat. MCP, short for Model Context Protocol, is an open standard that lets AI assistants read and update data in other apps.

The gap becomes obvious once a question covers more than one call. A pasted transcript only ever describes a single meeting. A connected assistant can take a question like “What did we promise X client across the last three calls?” and search your meetings for it. It pulls the relevant summaries and action items, then answers from all of them at once.

Krisp MCP opens your Krisp workspace to the assistant, including meeting data, action items and calendar. Some of its tools only read, while others make changes.

Reads
Find meetings
Searches by topic, attendees, tag, folder, speaker, duration or date range
Search inside meetings
Finds the exact passages across your transcripts that mention a topic
Pull meeting content
Fetches full transcripts, summaries, key points and action items
Plan ahead
Lists upcoming calendar meetings for the next 1 to 14 days
Changes
Manage action items
Adds, edits, reassigns and marks action items done
Organize meetings
Creates private folders, files meetings in them, and adds or removes tags
Clean up transcripts
Replaces “Speaker 1” labels with real names and renames meetings
Import recordings
Uploads an existing audio or video file as a new Krisp meeting

Krisp’s supported tools article lists every tool along with example prompts.

Before you start

Three things need to be in place before any assistant can reach your notes.

  • The first is a set of meetings in Krisp. The Krisp AI Note Taker records and transcribes calls in Zoom, Google Meet, Microsoft Teams and other calling apps. Those calls become the material your assistant reads.
  • The second is the right address. Krisp MCP runs only at https://mcp.krisp.ai/mcp, and it supports Streamable HTTP only, not Server-Sent Events (SSE).
  • The third is your Krisp sign-in. Krisp uses OAuth 2.0 with PKCE, which means there’s no API key to copy anywhere. An assistant opens a sign-in window the first time it reaches for Krisp and asks you to allow access.

One setting on the assistant’s side deserves attention too. Human confirmation for tool calls should stay switched on. It makes the assistant show what it’s about to change (an action item, a folder, a speaker name) before anything happens.

How to connect meeting notes to Claude

The easiest way to connect meeting notes to Claude starts in the Krisp app rather than in Claude. Krisp passes you over to Claude’s connector directory with everything already filled in.

Claude on the web and in the desktop app

The Claude card sits under Settings → Integrations in Krisp, and its Connect button opens Krisp’s listing in Claude’s connector directory. One more click on Connect there brings up the Krisp sign-in, and allowing access finishes the setup.

A question only your meetings could answer is the quickest test. Something like “What action items do I have open from this week’s meetings?” does the job.

Claude Code

Claude Code connects from the terminal with a single command:

bash
claude mcp add --transport http krisp <https://mcp.krisp.ai/mcp>

Running /mcp inside Claude Code afterwards starts the sign-in flow. Claude Code can then pull meeting context while it works, such as the requirements a client walked you through on yesterday’s scoping call.

How to connect meeting notes to ChatGPT

ChatGPT follows the same pattern as Claude, starting in Krisp and finishing in ChatGPT. The ChatGPT card under Settings → Integrations has its own Connect button. ChatGPT then walks you through a few short steps, which end with the Krisp sign-in and an access request.

ChatGPT can then answer questions like “Summarize every call I had with the design team in October” straight from your meeting history. Teams that keep project context in ChatGPT get the most out of this, since nobody has to retype what was decided on the last call.

How to connect meeting notes to Cursor

Cursor has the quickest route of all. The Add to Cursor button under Settings → Integrations in Krisp opens Cursor with Krisp ready to install.

The manual route takes a minute longer. The menu path is Cursor Settings → MCP → Add new global MCP server, and this is the configuration to paste:

json
{
  "mcpServers": {
    "krisp": {
      "url": "https://mcp.krisp.ai/mcp"
    }
  }
}

A restart loads the new server. The Krisp sign-in appears the first time Cursor uses a Krisp tool, and completing it connects your workspace.

Share the setup with your team

A project-level config gives everyone on a project the same connection. The same configuration goes into a .cursor/mcp.json file in the project root. Each person still signs in with their own Krisp account, so the assistant only sees meetings that person can access.

Engineers tend to feel the benefit first. A product manager might walk through edge cases on Tuesday’s planning call, for example. Cursor can search that transcript while the code is being written, and nobody has to dig through recaps to find what was said.

How to connect meeting notes to Grok

Grok connectors are open to all Grok users, and Krisp joins them as a custom MCP connector. The setup follows xAI’s connector documentation and takes about as long as pasting a link.

The starting point is grok.com/connectors on the web, or Settings → Connectors in the Grok mobile app. The New Connector button leads to a Custom option, where https://mcp.krisp.ai/mcp goes in as the server URL. A Krisp sign-in and an access approval complete the connection.

Grok then finds the tools Krisp offers and uses them on its own whenever a question is about your meetings. A fresh chat asking “What were the action items from my last Krisp meeting?” makes a good first test. The Disconnect button on grok.com/connectors removes Krisp again if you ever need to.

Grok Business and Enterprise. Teams on these plans need an admin to add the connector before anyone else can use it. xAI’s docs confirm that requirement, while the admin steps come from third-party guides. The admin signs in at console.x.ai with the Team Read-Write role, opens Grok Business → Connectors and clicks + Add Connector. The Krisp URL then goes in under the Other option, and team members connect their own Krisp accounts at grok.com/connectors.

Grok Bot. Grok Bot, xAI’s separate agent app on paid plans, handles the setup through conversation. A request to add a custom MCP server named Krisp with the URL https://mcp.krisp.ai/mcp is all it needs. An Authorize button and a Krisp sign-in follow, and Krisp joins any chat when you type @ and pick it.

How to connect meeting notes to Gemini

Gemini treats Krisp as a custom app, and the setup happens in the Gemini web app. Custom apps are available for personal Google accounts in the US, for people 18 and over, in English.

The path starts at gemini.google.com and goes through Settings → Connected Apps, where Add a custom app sits under Custom apps. The Krisp URL, https://mcp.krisp.ai/mcp, goes into that form. A click on Next, a Krisp sign-in and an access approval finish the job.

Krisp then shows up when you type @ in a chat, and Gemini can also reach for it when you simply ask about your meetings. The connection carries over to the Gemini mobile app as well. A missing Custom apps section usually points to a work or school account, or to Keep Activity being switched off in your Gemini settings.

How to connect meeting notes to Meta Muse

Meta Muse builds custom connectors through conversation, so adding Krisp starts with a message in a Muse chat. Muse is available to adults in the US and Canada, and more recently in Japan and Singapore. The setup works in the Muse app on the web (muse.ai), iOS or Android, but it doesn’t work from WhatsApp.

A new chat with this message gets things going: “Create a custom connector. Name: Krisp. Transport: Streamable HTTP. URL: https://mcp.krisp.ai/mcp. Sign-in: OAuth.” Some versions of the app also offer Settings → Connectors → Add custom connector, which accepts the URL directly.

Muse then shows a Krisp sign-in button, and signing in and allowing access completes the connection. “Use the Krisp connector to list my last 5 meetings” makes a good test prompt. Muse asks for your approval the first time, and again for any action it treats as sensitive.

Approval settings live under Settings → Permissions, and Settings → Connectors is where Krisp can be removed later.

VS Code and other MCP-compatible tools

Any AI tool that supports remote MCP servers can connect to Krisp with the same URL.

VS Code. VS Code adds Krisp through the Command Palette with MCP: Add Server. The HTTP option takes the URL https://mcp.krisp.ai/mcp, and krisp works fine as the server name. A Krisp sign-in prompt follows.

Other tools that support remote HTTP servers can use this configuration:

json
{
  "mcpServers": {
    "krisp": {
      "url": "https://mcp.krisp.ai/mcp"
    }
  }
}

Tools that only support local servers can reach Krisp through the mcp-remote bridge:

json
{
  "mcpServers": {
    "krisp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.krisp.ai/mcp"]
    }
  }
}

Developers building their own MCP client can follow Krisp’s guide to integrating your own MCP client.

First prompts to try once you’re connected

A read-only question is the safest first prompt, because it shows the connection working before the assistant changes anything. The jobs you’d normally do by hand after a call make good next steps.

If you’re a…
Try asking
Consultant or account lead
“Find my last three calls with X company and draft a status update covering what we agreed and what’s still open.”
Product manager
“Search my transcripts since June for onboarding drop-off and group what users said by theme.”
Sales or customer success
“List my pending action items from this week’s customer calls, then mark the pricing deck one done.”
Engineer
“Find where we discussed the API rate limits and show me the exact passage.”
Anyone after a busy week
“What meetings do I have in the next three days, and what did we decide last time I met each of these people?”

Two small habits make the answers noticeably better. The first is putting real names on speakers. The assistant can handle that itself with a request like “Speaker 1 is Tonny and Speaker 2 is Jane, fix the transcript.” Questions about who said what only work once that’s done. The second habit is tagging or filing meetings by client or project, so the assistant can search one folder instead of your whole history.

How to keep your meeting data safe when an AI assistant can read it

Two companies handle your meeting data once an AI assistant can read it. Krisp stores the notes, and the assistant reads whatever it needs to answer you. That arrangement deserves the same care you’d give any app with access to your calendar.

Krisp’s recommendations make a good baseline. The connection should only ever point to the official endpoint, https://mcp.krisp.ai/mcp, since no other URL is Krisp MCP. Human confirmation should stay on so every change gets your review before it runs. Only trusted MCP clients belong in the setup, because an untrusted tool or agent could be instructed to send your data somewhere else. A regular look at the assistant’s permissions helps too, along with disconnecting tools you no longer use.

Krisp’s side of the connection is covered by SOC 2 Type II and GDPR compliance. Meeting data is encrypted at rest (AES-256) and in transit (TLS 1.2 or higher), and Krisp never uses it to train its AI model. The copy an assistant reads falls under that assistant’s own data policies, though. Its settings are worth checking too, especially when your calls involve client information.

Troubleshooting common connection errors

Most meeting notes MCP problems trace back to an old connection or a client that doesn’t support remote servers.

What you see Why it happens How to fix it
“This action needs updated access” or “Reconnect to keep using Krisp” Connections made before Krisp added its write tools only have read access The Reconnect button next to Claude or ChatGPT under Settings → Integrations in Krisp refreshes access. Other tools need a disconnect, a fresh connection and a retry
The tool won’t accept the URL Your client doesn’t support remote MCP servers The mcp-remote configuration in the section above solves this
Connection fails or keeps dropping The client is trying SSE, or the sign-in didn’t finish The client needs to use Streamable HTTP, followed by a disconnect, a reconnect and a completed sign-in
“Bearer token is missing” The client isn’t sending your access token A fresh run through the sign-in flow lets the client store and send the token
“Document not found” The meeting ID is in the wrong format Document IDs are 32 lowercase hex characters with no dashes. The assistant can strip the dashes and retry
Gemini has no Custom apps section You’re on a work or school account, outside the US, or Keep Activity is off A personal Google account in the US with Keep Activity turned on fixes this
Gemini or Muse answers without using Krisp The assistant didn’t pick the connector for your question Gemini picks Krisp when you type @ and choose it. Muse responds best to requests that start with “Use the Krisp connector”
Muse asks for a client ID or API key Muse defaulted to key-based sign-in A reply explaining that Krisp supports OAuth with automatic registration, so no client ID is needed
Krisp stops answering in Muse The connection needs a fresh sign-in A request to Muse to reconnect the Krisp connector, followed by a new Krisp sign-in

Why connect Krisp meeting notes

An MCP connection is only as useful as the notes behind it. A thin or garbled record, or one missing half your meetings, leaves the assistant answering confidently from bad material. Krisp’s case rests on what happens before the notes ever reach the assistant.

On the call

Krisp AI Meeting Note Taker is bot-free by default. It captures calls through Krisp’s own microphone and speaker on your computer, so no extra participant shows up in your client’s meeting. That works in Zoom, Google Meet, Microsoft Teams, Slack Huddles and any other calling app. Bot-free capture matters most on the calls you’d most want an assistant to remember later.

Krisp works on the audio itself as well. Krisp AI Noise Cancellation removes background noise and echo in real time on both sides of the call. Its Voice Isolation filters out other people talking around you when you wear a compatible headset. The person on the other end hears you clearly, and the transcript records your conversation rather than the coffee grinder behind you. Transcripts and summaries work in 17 languages, with custom vocabulary to help with client names and product terms.

In your AI assistant

An AI meeting tool with MCP integration should fit into the assistants you already use. One Krisp connection works across Claude, ChatGPT, Cursor, Grok, Gemini, Meta Muse and VS Code. There’s no need to choose an assistant before choosing a note taker. Krisp MCP also includes write tools, so the assistant can handle the admin after a call as well as answer questions about it. It can close and reassign action items, file meetings into a client folder and fix speaker names without you ever leaving the chat.

https://mcp.krisp.ai/mcp
Claude
ChatGPT
Cursor
Grok
Gemini
Meta Muse
VS Code
Close and reassign action items
File meetings into a client folder
Fix speaker names

In the rest of your stack

Meeting notes can also flow into the tools your team already runs on through Krisp integrations. Core connects to HubSpot, Pipedrive, Affinity, Slack, Notion and Zapier, and Advanced adds Salesforce and ConnectWise.

The bottom line

Copy and paste works fine for a single meeting. It falls apart as soon as you ask an AI assistant about a client, a project or a decision that played out over several calls. An MCP connection to your meeting notes closes that gap. Krisp turns it into one URL, https://mcp.krisp.ai/mcp, that works in Claude, ChatGPT, Cursor, Grok, Gemini, Meta Muse and VS Code. One setup, with human confirmation left on, is all it takes for your next follow-up to start from what was actually said.

FAQ

Claude connects to your meeting notes through the Krisp app. The Connect button on the Claude card, under Settings → Integrations, opens Krisp in Claude’s connector directory. A second click on Connect there brings up the Krisp sign-in. Claude Code users can run a single terminal command instead.

ChatGPT can read your meeting notes once Krisp is connected through MCP. It can search your meetings, read transcripts and summaries, and list your action items. The setup starts from Settings → Integrations in the Krisp app, with the Connect button on the ChatGPT card.

Krisp meeting notes work in both Gemini and Meta Muse. Each one adds Krisp as a custom connector with the URL https://mcp.krisp.ai/mcp. Gemini custom apps need a personal Google account in the US. Meta Muse is available to adults in the US, Canada, Japan and Singapore, and the connector is set up by asking Muse in a chat.

Krisp MCP is Krisp’s hosted MCP server at https://mcp.krisp.ai/mcp. It lets AI assistants search your meetings and read transcripts and summaries. It can also manage action items, folders, tags and speaker names. It’s included on the paid Core, Advanced and Enterprise plans.

A good AI meeting notetaker MCP server is hosted by the vendor, uses OAuth sign-in and works with the assistants you already use. A growing number of AI note takers publish an MCP server, and the differences matter. The main questions are who hosts it and whether it signs you in with OAuth or a shared API key. Another is whether it can update action items and folders or only read them. Krisp MCP is hosted, uses OAuth and includes both read and write tools. It connects to Claude, ChatGPT, Cursor, Grok, Gemini, Meta Muse, VS Code and other MCP clients.

The assistant can change some things when you ask, but it can’t delete meetings. It can update action items, folders, tags, speaker names and meeting titles, and it can import new recordings. Human confirmation in your assistant means you approve every one of those changes before it runs.

Krisp works with meetings from Zoom, Teams, Google Meet and any other calling app on your computer. The Krisp mobile app also records in-person meetings. Any meeting in your Krisp workspace is within reach of your connected assistant, whichever app the call happened in.

Krisp never uses meeting data to train its own AI models. The assistant you connect reads your notes under its own data policies. Its privacy and training settings are worth a review before you connect it to client meetings.

You're one step away from
supercharging your online meeting!

background for toggle
Get started