MeetingDebrief

MCP server

Give Claude, Cursor, and other AI tools read-only access to your meetings

Overview

MeetingDebrief ships a built-in Model Context Protocol (MCP) server. It gives AI assistants such as Claude Desktop, Claude Code, and Cursor read-only access to your transcripts and summaries. You can ask your favorite agent to search across meetings, pull up a transcript, or summarize what you committed to last week, without copy-pasting anything.

How it works

The server runs on demand as a local sidecar. It opens no network ports and, like everything in MeetingDebrief, nothing leaves your machine. The AI tool launches it when needed and talks to it directly on your device.

Connecting a client

Open Settings and go to the MCP section. You will find a ready-to-paste configuration with a Copy button. Paste it into your AI tool's MCP configuration to wire up the client in seconds:

  • Claude Desktop: add it to your MCP servers configuration.
  • Claude Code: add it to your MCP servers configuration.
  • Cursor: add it to your MCP servers configuration.

You can also just ask the agent to add the MCP server automatically by pasting the snippet.

After pasting the config and restarting the client, the assistant can read your meetings.

What the agent can do

  • Search across all of your meetings by content.
  • Pull up a full transcript for a specific meeting.
  • Read summaries and surface action items or decisions.

Access is read-only. The MCP server cannot record, delete, or modify your sessions.

MCP server and the local HTTP API

The MCP server is the simplest way to connect an AI tool. If you need full programmatic control, including starting recordings and triggering summaries, use the local HTTP API instead.