MCP server

Point Claude Desktop, Cursor, or any MCP client at mcp.recordx.io and get three tools back: search_meetings, fetch_transcript, and upload_audio. Authenticated with OAuth, scoped to your account.

What it is

Model Context Protocol is an open standard from Anthropic for connecting LLM applications to external tools and data. Instead of every LLM host writing bespoke integrations to every service, MCP defines one wire protocol so any MCP-capable client can talk to any MCP server. The RecordX MCP server is one such endpoint, exposing your meetings and transcripts to any MCP client that authenticates against your account.

Point Claude Desktop, Claude Code, or Cursor at mcp.recordx.io, complete an OAuth flow once, and three tools show up inside that client: search_meetings for semantic search across your workspace, fetch_transcript for pulling the full transcript of a specific meeting, and upload_audio for pushing a local file into RecordX for transcription and processing.

You do not have to leave your editor or your assistant to work with your meetings. Ask Claude Desktop to find every mention of a customer in your last month of calls and it makes the search itself. Ask Cursor to pull the transcript of yesterday's design review and paste it into your PR context. The MCP server is the plumbing that makes all of that possible without any custom integration on your end.

Try the MCP server free

How it works

The endpoint lives at https://mcp.recordx.io. Authentication is OAuth through Amazon Cognito. Each environment has its own narrow Cognito client, which means a token issued for the dev endpoint cannot be used against production and vice versa. Tokens are scoped to your account; every tool call verifies the token and returns only data your account can access.

On the client side, configuration is a small JSON block. In Claude Desktop the file lives in the app's settings directory; in Cursor and Claude Code the syntax is similar. A minimal server entry looks like this.

{
  "mcpServers": {
    "recordx": {
      "url": "https://mcp.recordx.io"
    }
  }
}

After you add the server, the client will open the RecordX login page in a browser. You approve access with your normal RecordX credentials, the client stores the OAuth token, and the three tools become available in the current session. Every subsequent call flows through the token, so a compromised client cannot upload audio or read transcripts without also holding your token.

1. Add the server. Paste the JSON config into your MCP client. Restart the client if it asks.
2. Authorize. The client opens the OAuth flow. You sign in to RecordX; Cognito issues a token scoped to your account.
3. Use the tools. Ask the client to search your meetings, fetch a transcript, or upload a file. It calls the corresponding tool on the server.
4. Answers stay grounded. Transcripts and search hits go back to the client and become context for the model's reply.

Example prompts

Once the server is wired up, plain-English requests inside your MCP client work.

• Search my RecordX meetings for anything about the Q4 pricing change.
• Pull the full transcript of the Tuesday call with Acme and summarize the pricing block.
• Upload this audio file to RecordX and tell me who spoke.
• Find every meeting in the last two weeks where SSO came up and paste the timestamps.
• Fetch the transcript for meeting id 42fa and extract just the action items.
• Search my library for calls that mention the Frankfurt datacenter and list them by date.

The client decides which tool to call for each request. You do not have to name the tool. Under the hood search_meetings handles the search phase, fetch_transcript pulls a specific transcript by id, and upload_audio pushes a local file into the standard RecordX processing pipeline.

Where it lives

The production endpoint is https://mcp.recordx.io. It is a normal MCP-over-HTTP server; nothing to install on your machine beyond an MCP-capable client. Configure once in Claude Desktop, Cursor, or Claude Code and you are done. There is no separate desktop app for RecordX MCP.

Because MCP is an open standard, third-party MCP clients also work. If a tool speaks MCP, it can speak to mcp.recordx.io. The RecordX app itself and the chat over history feature use the same three tools internally.

Privacy and retention

Every request is authenticated with your OAuth token and scoped to your account. The server never returns meetings, transcripts, or audio that belong to another user. Same encryption in transit and at rest as the RecordX app. Source audio is deleted after processing; transcripts stay in your account for one year and can be deleted at any time. See the privacy policy.

Content that flows through the MCP server does not train foundation models. Bedrock is the model host for RecordX AI features that touch your data, and Bedrock's terms exclude your content from training.

Pricing

MCP access is included on all paid tiers. The free tier can connect too, subject to per-day rate limits on the three tools to keep costs predictable. See the current numbers on the pricing page.

Getting started

In Claude Desktop, open Settings, find the MCP servers section, and add https://mcp.recordx.io. The client walks you through the OAuth flow. Once authorized, ask Claude to search your meetings or fetch a transcript. The same steps work in Cursor and Claude Code.

Start for free

FAQ

What is MCP

Model Context Protocol is an open standard from Anthropic for connecting LLM applications to external tools and data. Any MCP-capable client can talk to any MCP server. RecordX exposes an MCP endpoint so tools like Claude Desktop or Cursor can search meetings, fetch transcripts, and upload audio through your RecordX account.

Which clients can connect

Any MCP-capable client. That includes Claude Desktop, Claude Code, Cursor, and any custom or third-party MCP client. MCP is an open standard, not a Claude-only surface.

What tools does the server expose

Three tools: search_meetings for semantic search across your workspace, fetch_transcript for a full transcript by meeting id, and upload_audio for pushing a local file into RecordX for processing.

How does authentication work

OAuth via Amazon Cognito. Each environment has its own narrow Cognito client, so a token issued for the dev endpoint cannot be used against production. Tokens are scoped to your account and expire on the standard Cognito schedule.

Can I use this from Claude Code

Yes. Claude Code is an MCP client. Add the RecordX MCP server as you would any other MCP endpoint and the three tools become available inside your session.

Does the server see other users' data

No. Every call is authenticated with your OAuth token and scoped to your account. The server never returns another user's meetings or transcripts.

Start for free