Meetric MCP

Connect your AI assistant directly to your Meetric meeting data using the Model Context Protocol.

Overview

MCP is an open standard that lets AI tools (like Claude, Cursor, Codex, and other MCP-compatible assistants) securely call external tools. Meetric hosts an MCP server so your assistant can read your meeting data — conversations, transcripts, summaries, insights, users, teams, and departments — through your signed-in user permissions - you connect by logging in with your normal account.

Switched off by default. MCP is switched off for every account by default. An account owner or admin switches it on in the app under Settings → Account → AI assistant connection (MCP). If your account comes from a partner, the partner has to allow MCP first.
https://meetric.com/mcp JSON-RPC 2.0 over HTTPS

How it works

  1. User sign-in mode: OAuth-capable MCP clients (including Notion) dynamically register, then open a Meetric login screen. Use your normal password, SSO, and MFA flow. The MCP can only see what your user can see.
  2. Your permissions apply: the connection is tied to your user and account - the MCP can only ever see what you can see in the app.
  3. Your assistant calls tools/list to discover tools, then tools/call to fetch data. Every call is validated against the Meetric API and scoped to your account.

Authentication

Meetric MCP uses user sign-in only: OAuth + PKCE with Dynamic Client Registration, issuing a mcp_at_… token tied to your user and account. Invalid or expired tokens are rejected with 401.

Token lifetime. An access token (mcp_at_…) is valid for 60 minutes. AI clients renew it on their own with the refresh token, which is valid for 30 days and renewed on every use, so you stay signed in for as long as you keep using the connection. If you build your own integration, it must implement the OAuth refresh_token grant: a copied access token stops working after an hour. For automation that runs without a signed-in user, use the Meetric REST API with an API token instead.

Recommended: sign in with Meetric

Use this for personal assistants such as Claude, Notion, Cursor, and Codex. The client opens Meetric login, including password, SSO, and MFA when required. Data access follows the signed-in user's normal Meetric permissions.

Connect your assistant

Claude Desktop

Claude Desktop runs MCP servers locally, so bridge the hosted endpoint with mcp-remote. Add this to claude_desktop_config.json (Settings → Developer → Edit Config):

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

Cursor

Cursor supports remote MCP servers directly. Add this to ~/.cursor/mcp.json (or Settings → MCP):

{
  "mcpServers": {
    "meetric": {
      "url": "https://meetric.com/mcp"
    }
  }
}

Codex (OpenAI Codex CLI)

Add this to ~/.codex/config.toml:

[mcp_servers.meetric]
command = "npx"
args = ["-y", "mcp-remote", "https://meetric.com/mcp"]

Notion & other MCP-compatible tools

For any assistant that supports a remote / custom MCP connector, add the endpoint - the connector opens the Meetric sign-in when you connect:

{
  "mcpServers": {
    "meetric": {
      "url": "https://meetric.com/mcp"
    }
  }
}

If the tool only supports local (stdio) MCP servers, use the mcp-remote bridge shown in the Claude example.

Verify it works

List the available tools from a terminal:

curl -s https://meetric.com/mcp \
  -H "Authorization: Bearer YOUR_MCP_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Available tools

ToolScopeDescription
account_get—Get basic account and branding information for the connected account.
users_listusersList active users in the account. Requires REST scope: users.
teams_listteamsList teams and members in the account. Requires REST scope: teams.
departments_listdepartmentsList enabled departments in the account. Requires REST scope: departments.
conversation_types_listconversationsList enabled conversation types for the account (system defaults plus account-defined). The name values match the conversation_type field on conversations and the conversation_type filter of conversations_list. Requires REST scope: conversations.
conversations_listconversationsList recent conversations using the existing REST API filters.
conversations_getconversationsGet one conversation by ID. Requires REST scope: conversations.
conversations_transcripttranscriptsGet transcript for one conversation. Requires REST scope: transcripts.
conversations_insightsinsightsGet insights/topics for one conversation. Requires REST scope: insights.
conversations_summaryconversationsGet summary for one conversation. Requires REST scope: conversations.
topics_listtopicsList topics (KPI-grouped insights) you can access, aggregated across your visible conversations. User-authenticated (OAuth) mode only.
topics_drilldowntopicsDrill into a topic to get its underlying insights with source conversation references and transcript timestamps. Provide kpi_label and/or insight_type from topics_list. User-authenticated (OAuth) mode only.
searchsearchSearch transcripts and insights (semantic + exact keyword) for words or phrases across the conversations you can access. Returns hits with conversation references + timestamps for transcript drilldown. User-authenticated (OAuth) mode only.

Limits & behavior

  • Read-only. Public Meetric tools do not modify Meetric data.
  • Account-scoped. A connection only ever sees the data of its own account, filtered by the signed-in user permissions.
  • Pagination. List results are capped (limit is clamped to 25); use the returned cursor for more.
  • Request size. Requests are limited to 64 KB.
Important: GDPR & compliance boundaries. While Meetric ensures secure data transit and protocol compliance within the MCP environment, you are solely responsible for ensuring that all downstream applications, custom connected servers, and external data storage locations comply with your organization’s GDPR policies and local privacy regulations. Meetric does not monitor or manage compliance rules applied outside of the Meetric platform.

Support

Questions or feedback? Email [email protected].