Connect via MCP
Overview
The Omniconvert MCP Server exposes your experiments and analytics data through the Model Context Protocol (MCP), letting AI tools read your Explore data directly.
Compatibility
-
MCP spec:
2025-06-18 -
JSON-RPC:
2.0 -
Supported transport: Streamable HTTP
-
MCP entry point:
https://web.omniconvert.com/mcp
Connection methods
Depending on which AI tool you're connecting, use one of these:
-
Connect Claude AI - custom connector.
-
Connect ChatGPT - custom connector.
-
Connect via API Key - for Cursor, Claude Code, Claude Desktop, and other API-key-based clients.
Authentication
The server accepts two authentication schemes, both sent via the standard Authorization header:
-
ApiKey -
Authorization: ApiKey <token>. Recommended for programmatic clients (Cursor, Claude Code CLI, Claude Desktop via bridge, custom integrations). See Connect via API Key for how to generate a key and configure it. -
OAuth 2.1 Bearer -
Authorization: Bearer <token>, with dynamic client registration. Used automatically by the Claude AI and ChatGPT custom connectors - no manual setup required for those.
Tokens are scoped to the Omniconvert account that owns them. A token can read experiments, variations, goals, segments, and reports for any website attached to that account - it cannot reach resources belonging to a different account.
Available tools
|
Tool |
Purpose |
|
|
Retrieve initial context for experiment analysis |
|
|
Find a website by its ID or URL |
|
|
List all available websites |
|
|
Get the list of available experiments |
|
|
Get experiment data by its URI |
|
|
Get variation data by its URI |
|
|
Get goal data by its URI |
|
|
Get segment data by its URI |
|
|
Bulk performance overview for up to 10 experiments (users, conversion rate, revenue, leads, survey respondents) over a date range |
|
|
Get a performance report for an experiment |
|
|
Get performance chart series for an experiment |
Available resources
-
Experiment
-
Variation
-
Goal
-
Segment