MCP Server

The Record Meeting MCP (Model Context Protocol) server lets AI assistants like Claude, Cursor, Codex, ChatGPT, and other MCP-compatible clients access your recordings, transcripts, and organizations directly.

What is MCP?

Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. By connecting your AI assistant to the Record Meeting MCP server, you can ask questions about your meetings, search transcripts, manage recordings, and more - all from within your AI workflow.

Let your agent set itself up

If you already have an AI agent open, you do not need to follow this guide by hand. Copy this line and paste it into a fresh chat:

Fetch and execute the appropriate instructions to set me up for RecordMeeting from https://recordmeeting.com/agent-setup/prompt.md

Your agent reads the instructions at that URL, connects through the sign-in flow (or asks you for an API key if its tool cannot sign in), writes the configuration for whichever tool you are using, and then verifies the connection by listing one of your recordings. The same button is available in the app under Settings, and on the agent setup page.

The rest of this page covers the manual setup, which is worth reading if you want to know exactly what your agent is changing.

Prerequisites

• A Record Meeting account with at least one recording
• An MCP-compatible client (e.g. Claude Desktop, Claude Code, Cursor, Codex, ChatGPT)
• An API key (see API Keys), only if your client cannot sign in on its own

Connecting your client

The Record Meeting MCP server is available at:

https://api.recordmeeting.com/mcp

Sign in instead of pasting a key

Most clients can connect with a sign-in flow, so you do not need an API key at all. Add the server with no headers, and the client opens a Record Meeting page in your browser where you approve the connection. Claude.ai, Claude Desktop, Claude Code, ChatGPT and Cursor all support this.

Claude (claude.ai and Claude Desktop)

1. Open Settings, then Connectors, and choose Add custom connector.
2. Name it Record Meeting and enter https://api.recordmeeting.com/mcp as the URL.
3. Click Connect, sign in with the Google account you use for Record Meeting, and approve access.

ChatGPT

1. Open Settings, then Security and login, and turn on Developer mode. Adding your own server needs it until Record Meeting is listed in the ChatGPT directory.
2. Go to Plugins, choose the plus button, name it Record Meeting, and enter https://api.recordmeeting.com/mcp as the server URL.
3. Sign in with the Google account you use for Record Meeting and approve access.

Claude Code

claude mcp add --transport http recordmeeting https://api.recordmeeting.com/mcp

Then run /mcp inside Claude Code, pick recordmeeting, and choose Authenticate. For Cursor, add the server without a headers block and click the login prompt next to it in Settings, then MCP.

You can see and disconnect every connected agent under Settings, in the Connected agents section. The sections below use an API key instead, for clients that only support static headers.

Claude Desktop

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "recordmeeting": {
      "url": "https://api.recordmeeting.com/mcp",
      "headers": {
        "Authorization": "Bearer <your_api_key>"
      }
    }
  }
}

Claude Code

Run the following command in your terminal:

claude mcp add --transport http recordmeeting https://api.recordmeeting.com/mcp \
  --header "Authorization: Bearer <your_api_key>"

Cursor

Add the following to your .cursor/mcp.json file:

{
  "mcpServers": {
    "recordmeeting": {
      "url": "https://api.recordmeeting.com/mcp",
      "headers": {
        "Authorization": "Bearer <your_api_key>"
      }
    }
  }
}

Codex

Add the following to ~/.codex/config.toml (or a project-scoped .codex/config.toml):

[mcp_servers.recordmeeting]
url = "https://api.recordmeeting.com/mcp"
http_headers = { Authorization = "Bearer <your_api_key>" }

Note

Replace <your_api_key> with an actual API key from Settings → API Keys. See API Keys for how to create one.

Available tools

Once connected, your AI assistant can use the following tools. Read tools never change anything. Write tools change or remove data in your account, and most assistants ask you to confirm before they run one.

Recordings

Tool	Type	Description
list_recordings	Read	Browse your recordings, with filters for status, date range, folder, organization and member
search_recordings	Read	Find recordings by a word or phrase in the title
get_recording_by_date	Read	Find recordings from a day or a range such as “yesterday” or “last week”
get_recording	Read	Details of one recording: status, meeting notes and participants, plus a download link when you ask for one
get_transcript	Read	What was said, as speaker-labelled segments with timestamps
get_share_link	Read	The existing share link of a recording, without creating a new one
update_recording	Write	Rename a recording or replace its meeting notes
create_share_link	Write	Create a public share link, or change it to view or download. This replaces the previous public link
delete_recording	Write	Permanently delete a recording with its transcript, notes and share links

Organizations

Tool	Type	Description
list_organizations	Read	The organizations you belong to
list_folders	Read	The folders of an organization
list_members	Read	The members of an organization and their roles. Emails are shown only to owners and admins

Permissions and your data

• The connector sees only what your Record Meeting account can see: your own recordings, and the recordings your organizations share with you. Locked recordings on the Free plan stay locked.
• Your assistant fetches recordings, transcripts and notes only when a conversation needs them. Record Meeting does not read your chats, and the assistant’s provider (for example OpenAI or Anthropic) handles what it receives under its own terms.
• Nothing is shared publicly unless you ask for a share link.
• You can disconnect an assistant at any time under Settings, in the Connected agents section. Access stops immediately.
• See the Privacy Policy for how Record Meeting stores and protects recordings and transcripts.

Example prompts

Once connected, try asking your AI assistant things like:

• “What meetings did I have last week?”
• “Summarize the key decisions from yesterday’s standup”
• “Search my recordings for discussions about the product launch”
• “What action items came out of the Q1 planning meeting?”
• “Share the recording from this morning’s sync with view-only access”

Troubleshooting

“Unauthorized” or “401” errors

• If you signed in, disconnect and connect the connector again. Access also ends when you remove the assistant under Connected agents
• If you use an API key, make sure it is valid and has not been revoked
• Check that the Authorization header uses the Bearer prefix

Tools not appearing

• Verify the server URL is exactly https://api.recordmeeting.com/mcp
• Restart your AI client after updating the configuration

No recordings returned

• Confirm your account has recordings by checking the Record Meeting dashboard
• If using an organization context, make sure your role grants access to recordings