Krisp MCP

This article will help you connect your own AI tools, such as Cursor, Claude Code, or VS Code, to your Krisp workspace.

Krisp MCP uses the Model Context Protocol (MCP), an open standard that lets AI assistants read and update data in other applications.
 

Overview

Krisp MCP is a hosted server that gives AI tools secure access to your Krisp workspace, including your meeting data, action items, and calendar. It is designed to work with AI assistants like Claude Code, Cursor, VS Code, ChatGPT, and others.

Krisp MCP supports Streamable HTTP transport only. Server-Sent Events (SSE) is not supported.
 

Why use Krisp MCP?

• OAuth setup: Connect through OAuth 2.0 with PKCE; complete the flow when your tool prompts you
• Meeting intelligence: AI tools can search meetings, read transcripts and summaries, and list action items
• Structured for AI: Tools return structured data and natural-language summaries for agent use

What can you do with Krisp MCP?

• Search meetings: Find past meetings by topic, attendees, tags, folder, speaker, duration, or date range
• Search inside meetings: Find the exact passages across your transcripts that mention a topic
• Read meeting content: Fetch full transcripts, summaries, key points, and action items by document ID
• Rename meetings: Change a meeting's title
• Manage action items: List, add, and edit action items (text, assignee, due date, priority), and mark them done
• Organize folders: Create private folders, rename them, and add or remove meetings
• Manage tags: List your tags, and add or remove tags across meetings in bulk
• Assign speakers: Replace "Speaker 1" style labels with real names across a transcript and its summary
• Import recordings: Upload an existing audio or video file to Krisp and check when it is ready
• Plan ahead: List upcoming calendar meetings and agenda IDs for the next 1-14 days
• Stay updated: List Activity Center notifications (assignments, summaries, etc.)
• Check your settings: Read your name, timezone, and company
• Date/time: Get current date/time or enumerate dates in a range for accurate scheduling
• Send feedback: Tell Krisp what you need or what didn't work, right from your AI tool

Connecting to Krisp MCP

This guide walks you through connecting your AI tool to Krisp MCP. Once connected, your tool can read and update your Krisp meetings, action items, folders, and tags based on your access and permissions.
 

Transport and URL

Claude (web and desktop app)

1. In Krisp, go to Settings Integrations and click Connect on the Claude card
2. Claude opens Krisp in its connector directory. Click Connect
3. Sign in to Krisp and allow access

ChatGPT

1. In Krisp, go to Settings Integrations and click Connect on the ChatGPT card
2. Finish the steps in ChatGPT, then sign in to Krisp and allow access

VS Code

1. Open the Command Palette and run "MCP: Add Server"
2. Choose HTTP and paste "https://mcp.krisp.ai/mcp"
3. Name it "krisp", then sign in to Krisp when prompted

Cursor

Fastest way: in Krisp, go to Settings Integrations and click Add to Cursor. Cursor opens with Krisp ready to install. To set it up by hand instead, follow the steps below.

1. Go to Cursor Settings MCP Add new global MCP server

2. Paste the following configuration (JSON):

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

3. Save and restart Cursor. When you use a Krisp tool for the first time, complete the OAuth flow to connect your workspace

Project-level configuration

To share the Krisp MCP configuration with your team, create a ".cursor/mcp.json" file in your project root:

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

Claude Code

Run the following in your terminal:

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

Then authenticate by running "/mcp" in Claude Code and following the OAuth flow.

Other tools

If your AI tool supports MCP with a remote HTTP server, use:

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

If your tool does not support remote HTTP connections directly, use the mcp-remote bridge:

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

Security best practices

• Use the official endpoint only: Connect only to https://mcp.krisp.ai/mcp. Do not use other URLs for Krisp MCP
• Review actions: Enable human confirmation when possible so you can review what the agent does with your data
• Protect your data: Untrusted tools or agents could be instructed to exfiltrate data. Use only trusted MCP clients and review permissions
• Secure token storage: Store access and refresh tokens securely (e.g. encrypted); never expose them in client-side or public storage
• HTTPS only: Use HTTPS for all OAuth redirect URIs and MCP connections in production

Troubleshooting