Resources · Claude connector

Claude Krisp connectorWhat Claude can do in your Krisp account.

The Claude Krisp connector exposes 7 tools. 7 of them read your meeting history, 0 change it on the directory sheet, and 0 are left undocumented. Below: what Claude can pull from your calls, what Krisp says exists beyond the sheet, and who controls it.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can reach your meetings

Decisions made on calls tend to vanish into recordings nobody replays. With this connector, you ask Claude what was agreed, who owes what or what is coming up, and it looks through your Krisp history itself: summaries, key points, action items and, when needed, full transcripts. The answer lands in the conversation you are already having.

Recover a decision without replaying the call. A product manager wonders what was settled on pricing last month: Claude runs search_meetings by topic and date, then opens the matching summary or transcript with get_multiple_documents.

Know what is still open. list_action_items returns tasks from your meetings with their assignee, due date and status, so a Monday check-in starts from a real list rather than scattered notes.

Prepare for what is next. list_upcoming_meetings shows the calls planned in the coming days, with participants and the video link, which gives Claude enough to draft a short brief before each one.

What it will not do from this sheet: by default, the directory lists only reading tools. Krisp's own article mentions six tools that change a workspace, but none of them appears on the Claude sheet dated September 2026, so this page does not describe them. And no tool reacts by itself when a meeting ends; running a job on that event is an automation tool's work, a different trade covered by the Integrations hub.

Vocabulary

Five words before you connect

The vocabulary Claude uses around this connector, quickly.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers.
Tool
One named action a connector lets Claude take. Claude chooses the tools it needs by itself, and the directory lists each one by name.
Authorization
The login screen of the service itself, where you give Claude the access it will use. Granted once per person, and revocable.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
MCP
The shared standard connectors are built on, which is what lets an assistant such as Claude talk to an outside service like Krisp.
Connect

Connect Krisp to Claude in three steps

  1. 01

    Find Krisp in Claude

    Open Claude's settings, go to Customize and then Connectors, and look for Krisp in the list. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on before each member can sign in.

  2. 02

    Start the connection

    Click Connect on its row, then sign in to Krisp in the window Krisp opens itself. If the link stops working one day, use Disconnect and connect again from the same place.

  3. 03

    Review the authorization screen

    Read the authorization screen before you accept. It belongs to Krisp, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Krisp account.

Tools

The 7 tools, all on the reading side

Krisp gives Claude 7 tools: 7 that read your account, 0 that change something in it.

On the directory sheet, every tool of this connector reads. Tool names stay exactly as Claude displays them.

  • 7 read

What Claude reads (7)

7 tools

Seven tools that look into your meetings and leave them as they are.

date_time

Gives Claude the current date and time, or the list of dates inside a range, so it stops guessing when you say last Tuesday or next week.

When it helps
you ask for every call held in the first half of the month and Claude needs exact dates to filter.

Sourcehelp.krisp.ai · September 23, 2026 ↗

get_multiple_documents

Opens one or several meeting documents by their identifier and picks the parts you want: notes, summary, key points, action items, tags, a recording link or the full transcript.

When it helps
you need yesterday's client call word for word before replying to their email.
Watch out
Krisp says summaries fit up to 50 meetings at once, while transcripts are heavy and go a handful at a time.

Sourcehelp.krisp.ai · September 23, 2026 ↗

get_user_preferences

Looks up the name, timezone and company set in your Krisp profile, which Claude uses to get times and names right in its answers.

When it helps
your team spans two continents and a meeting time must be read in your own zone.

Sourcehelp.krisp.ai · September 23, 2026 ↗

list_action_items

Returns the tasks and follow-ups raised in your meetings, each with its assignee, due date, completion status and source meeting. Filters cover status, items assigned to you, one meeting or one folder.

When it helps
before a standup, you want the list of what is still pending on your side.

Sourcehelp.krisp.ai · September 23, 2026 ↗

list_activities

Reads the Krisp Activity Center, newest first: notifications, task assignments, meeting summaries and similar items, each with a link into Krisp and an unread count.

When it helps
back from a day off, you ask Claude what landed in Krisp while you were away.

Sourcehelp.krisp.ai · September 23, 2026 ↗

list_upcoming_meetings

Shows calendar meetings planned for the next 1 to 14 days, with title, time, organizer, participants, whether guests are external and the video link.

When it helps
Monday morning, you want the week's external calls in one view to plan prep time.
Watch out
beyond 14 days, Krisp documents nothing for this tool.

Sourcehelp.krisp.ai · September 23, 2026 ↗

search_meetings

Finds meetings by text or by ID and returns metadata, summaries, key points and action items. Krisp lists filters for date, tag, folder, speaker, participant domain, duration and ownership.

When it helps
you are looking for every call with a given customer domain since the spring.
Watch out
full transcripts come from the fetch tool, not from this one.

Sourcehelp.krisp.ai · September 23, 2026 ↗

Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account on someone's behalf, with the prompt shown in the conversation.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also restrict what a connector does for the whole organization, for instance keeping reading and closing writing, and nobody overrides that from a personal account. Claude also works with the rights of the person who connected, nothing more: a meeting you cannot open in Krisp stays out of its reach. Krisp itself advises keeping human confirmation on for any tool that changes a workspace.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability, so the answer for Krisp is published nowhere.

Anthropic does publish the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector before members connect one by one. For the current state of Krisp on your account, open its sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing starts on its own when a meeting ends or a transcript is ready.

This connector is documented by its publisher only: no page of Claude's help center covers it. A tool list that only reads is an observed floor, not a guarantee, since an administrator can open writing that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. Connectors such as the Claude asana connector follow the same logic of rights.

Need help

Need help connecting Krisp to Claude?

A person reads every message.

FAQ

Questions about the Claude Krisp connector

01What can Claude do with the Krisp connector?
Claude can search and read your Krisp meeting history from a conversation. Its seven tools cover searching meetings, fetching summaries or full transcripts, listing action items, showing upcoming calls, reading the activity feed, checking your profile preferences and getting exact dates. That lets it answer questions such as what was decided last month or what is still open for you, based on your own recorded meetings rather than on memory or guesswork.
02Can Claude change anything in my Krisp workspace?
Not through the tools on the directory sheet: by default, it lists only reading tools. Krisp's help article does mention six tools that change a workspace, and says those editing an existing meeting also need edit access to it, but none of them appears on the Claude sheet read in September 2026. A reading-only list is still a floor rather than a guarantee, because an administrator can open actions that no public sheet shows.
03Does Claude ask before it uses the Krisp tools?
By default, Claude asks for confirmation before each action it takes on an account for someone. No source describes a confirmation specific to any of the seven reading tools, so that general rule is what applies. Krisp recommends keeping human confirmation on for its tools that change a workspace. On Team and Enterprise workspaces, owners decide whether members may skip some prompts, and they can narrow the connector for the whole organization.
04Which Claude plans can use this connector?
No official source publishes plan availability connector by connector, and none of the directory's sheets shows it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. The connector's sheet in the official directory is the only place that shows its current state for your account, so check it there.
05Does Claude see every meeting in our Krisp workspace?
No, it works with the rights of the person who connected. Search covers meetings you own and meetings shared with you, and nothing beyond what your own Krisp account can open. A colleague who attended other calls will get other answers. On top of that, an owner of a Team or Enterprise workspace can restrict what the connector does for the whole organization, and members cannot lift that restriction themselves.
06Why can Claude not pull a whole quarter of transcripts at once?
Because Krisp treats notes and full transcripts as heavy content. Its article says summaries, key points, action items and tags are light, up to 50 meetings in one request, while notes and transcripts should be fetched a handful of meetings at a time. In practice, ask Claude for summaries across the period first, then for the full transcript of the few calls that really matter to your question. Meeting search already returns summaries and key points on its own.
07Should I use Claude or an automation tool with Krisp?
They do different jobs, so choose by need. Claude works inside a conversation: you ask, it searches your meetings and answers, and nothing moves once you stop. It does not react by itself when a call ends or a new transcript appears. If you want something to run in the background on that kind of event, that is an automation tool's job. For questions about past or upcoming meetings on demand, the connector fits.