MCP Server

Important: The MeetRox MCP Server is in private beta. It is enabled by MeetRox per workspace. Contact your Customer Success Manager to request access.

Overview

The MeetRox MCP Server lets an AI assistant answer questions with real data from your MeetRox workspace, such as "which calls last month scored below 6?" or "rank our reps by AI score in October". The assistant decides which tools to call based on the question, and MeetRox returns the data.

Read-only. No tool creates, updates or deletes anything in MeetRox or in your CRM.
Per user. Each person connects their own MeetRox account and sees only the conversations they can already see in the MeetRox app.
No API key. The server uses OAuth. API keys from the MeetRox API do not work with the MCP Server, and MCP tokens do not work with the API.

Server URL

https://mcp.meetrox.ai/mcp

The server uses the Streamable HTTP transport.

Requirements

An MCP client that supports remote servers over Streamable HTTP with OAuth, such as:
- Claude (claude.ai, Claude Desktop and Claude Code)
- ChatGPT (web)
- Cursor
- VS Code with GitHub Copilot
- Other clients that follow the MCP authorization spec
A plan with your AI provider that allows adding custom connectors or MCP servers. In ChatGPT, for example, custom MCP servers are available on Business and Enterprise/Edu workspaces and are added by a workspace admin or an authorized member.
A MeetRox account with the Workspace Manager or Member role in the workspace you want to connect. Editors and Guests cannot use the MCP Server: the connection may complete, but every question returns an access error.
The MCP Server enabled for your workspace by MeetRox.

Connecting a Client

In your AI client, add a new MCP server (custom connector) with the server URL above.
The client opens the MeetRox sign-in page. Sign in with your MeetRox account, including SSO if your workspace uses it.
On the authorization screen, select the workspace to connect and click Allow access.
The client receives the credentials and the MeetRox tools become available in the chat.

If the MCP Server is not enabled for your account, the authorization screen says so and the connection does not complete.

Claude (claude.ai and Claude Desktop)

Go to Settings → Connectors → Add custom connector, enter the server URL and complete the sign-in.

Claude Code

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

Then run /mcp inside Claude Code and complete the sign-in.

Cursor

Add the server to your mcp.json:

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

Cursor asks you to sign in the first time it uses the server.

ChatGPT

Custom MCP servers are available in ChatGPT on the web, for Business and Enterprise/Edu workspaces.

Go to Plugins, select + and then Add custom MCP server.
Enter a name, such as "MeetRox", and the server URL.
Choose OAuth as the authentication method and complete the MeetRox sign-in.
Review the risk warning, confirm it and select Create as a plugin.
In a chat, type @ and select the MeetRox plugin.

On Business workspaces, only admins and owners can add and publish the connection. On Enterprise/Edu, admins can also allow selected members to add it.

Important: ChatGPT keeps a snapshot of the tools approved by your workspace admin. When MeetRox updates the tools, an admin may need to refresh them in the workspace app settings before they work again.

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your project, or to your user configuration:

{
  "servers": {
    "meetrox": {
      "type": "http",
      "url": "https://mcp.meetrox.ai/mcp"
    }
  }
}

Start the server from the file and complete the sign-in when VS Code asks. You can also use MCP: Add Server in the Command Palette and choose HTTP.

Other clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect with the server URL. Clients that only support local (stdio) servers can use a bridge such as mcp-remote.

Authentication

The MCP Server is an OAuth 2.1 protected resource. Clients that follow the MCP authorization spec discover and complete the flow on their own:

A request without a token returns 401 with a WWW-Authenticate header that points to the protected resource metadata.
The metadata lists https://app.meetrox.ai as the authorization server.
The client registers itself (Dynamic Client Registration), runs the Authorization Code flow with PKCE (S256) and requests the mcp:read scope.

Endpoint	URL
Protected resource metadata	`https://mcp.meetrox.ai/.well-known/oauth-protected-resource`
Authorization server metadata	`https://app.meetrox.ai/.well-known/oauth-authorization-server`
Authorization	`https://app.meetrox.ai/oauth/authorize`
Token	`https://app.meetrox.ai/oauth/token`
Client registration	`https://app.meetrox.ai/oauth/register`
Revocation	`https://app.meetrox.ai/oauth/revoke`

Redirect URIs must use https, or http on a loopback address (localhost, 127.0.0.1) for native apps.

Workspaces and Permissions

One workspace per connection. Each authorization covers a single workspace. To use another workspace, disconnect and authorize again choosing the new one. The latest authorization replaces the previous one for the same client.
Same visibility as the app. Workspace Managers see every visible conversation in the workspace. Members see their own conversations, public conversations and the ones shared with them. Rankings and aggregated metrics for a Member cover only what that Member can see.
Checked on every request. If the user is blocked, removed from the workspace or moved to the Editor or Guest role, requests are denied immediately, even with a valid token.

Token Lifetime

Item	Behavior
Access token	Valid for 1 hour. The client refreshes it automatically.
Refresh token	Rotates on every refresh. Each new refresh token is valid for 30 days.
Inactivity	Authorizations unused for 7 days are revoked. The user needs to connect again.
Revocation	Clients can revoke their tokens at the revocation endpoint, usually when the connector is removed. An access token already issued may remain valid until it expires, up to 1 hour.

Available Tools

The assistant chooses the tools based on the question. You do not need to call them by name.

Tool	What it does	Main parameters
`search_conversations`	Finds conversations by what was said (transcript search), by title, by participant, by date range or by AI score range. Content matches include up to 3 excerpts.	`content`, `query`, `speaker`, `date_from`, `date_to`, `min_ai_score`, `max_ai_score`, `mine`, `limit`, `cursor`
`get_conversation`	Returns one conversation with participants, summary and transcript. Chats also include channel and message count.	`id`, `transcript_offset`
`analyze_conversation`	Returns the MeetRox summary of a conversation, or its transcript so the assistant can extract action items and decisions.	`id`, `analysis_type` (`summary`, `action_items`, `key_decisions`, `all`), `transcript_offset`
`rep_interaction_profile`	Talk metrics for one conversation (talk ratio, exchanges, monologues, silence and, for chats, response times), or the averages across a rep's conversations in a period.	`id` or `agent`, `date_from`, `date_to`
`aggregate_calls`	Total conversations, total and average duration, average AI score and average manual score for a period.	`date_from`, `date_to`, `call_format`
`get_rep_leaderboard`	Ranks reps by average AI score, with conversation count, win rate, scores, average duration and talk ratio.	`date_from`, `date_to`, `call_format`, `top_n`, `cursor`
`get_rep_calls`	A rep's conversations with a performance summary, including win rate.	`agent`, `date_from`, `date_to`, `call_format`, `limit`, `cursor`
`scorecard_analysis`	A rep's score trend: average scores, scored conversations, best and worst conversation, and older versus newer half of the period.	`agent`, `date_from`, `date_to`
`call_scorecard_detail`	The AI scorecard of one conversation, question by question (met, missed or not applicable).	`id`

All tools also accept an optional workspace selector (workspace_filter or workspace_id). With one workspace per connection, it can be omitted.

Important: Tool names and parameters may change while the MCP Server is in beta. Clients read the current list from the server on every connection.

Behavior

Dates. date_from and date_to accept YYYY-MM-DD or a full ISO 8601 datetime. Dates without a time zone are UTC. Chat message times are returned in UTC.
Default period. When the question does not set a period, tools use the last 30 days. Every reply states the period it covered.
Maximum period. Each request covers at most 366 days. For longer periods, the server suggests consecutive windows to query one by one.
Scores. AI and manual scores are shown on a 0 to 10 scale, as in the MeetRox app. min_ai_score and max_ai_score also use 0 to 10.
Transcript search. content runs a full-text search over the transcripts of audio and video conversations. It matches words and phrases, not meaning, with Portuguese word forms and accents normalized. It supports "exact phrase", -exclude and or. Results are ordered by date, not by relevance. Coverage of chat conversations is not guaranteed yet.
Rep matching. agent accepts a name or email. When it matches more than one rep, the tool returns the candidates instead of combining them, and the assistant should ask which one.
Large results. Lists are returned in pages. When more results remain, the reply includes a cursor to request the next page. Long transcripts are returned in parts; the reply indicates the transcript_offset for the next part.

Rate Limits

Scope	Limit	Window
All MCP requests	100 requests	Per minute, per user

Every request to the server counts, including protocol messages such as listing the tools, not only tool calls. A single question can trigger several requests, for example a search followed by opening each conversation. When the limit is exceeded, the server responds with 429 Too Many Requests:

{
  "error": "rate_limit_exceeded"
}

Important: Wait at least 60 seconds before retrying after a 429.

Errors

Status	Meaning	What to do
`401 Unauthorized`	Missing, expired or revoked token, or a token without the `mcp:read` scope.	The client starts the sign-in again. If it does not, remove and add the connector.
`429 Too Many Requests`	Rate limit exceeded.	Wait and retry.

Other errors are returned to the assistant as a tool error, with a message explaining what happened:

Access denied. The MCP Server is not enabled for the workspace, the user's role cannot use it, or the user no longer has access to the workspace. The connection may look active in the client while every question fails. Check the user's role and contact your Customer Success Manager.
Invalid request. For example, an invalid date or a period longer than 366 days. The message explains how to fix the request.
Query timeout. The message asks for a shorter period. Retrying the same request does not help.

Security and Privacy

The MCP Server only reads data. It never writes to MeetRox or to your CRM.
Each user authorizes their own access and can stop it at any time by removing the connector. Unused authorizations are revoked automatically after 7 days.
Data returned by the tools is sent to the AI assistant you connected and is processed under that provider's terms. Review your AI provider's data policies before connecting.

Best Practices

Set the period. Ask with explicit dates for anything older than 30 days.
Prefer shorter periods in large workspaces. Month by month is faster than a full year.
Treat numbers as assistant output. Figures come from MeetRox, but the text is written by your AI assistant. For official numbers, use the MeetRox app.