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:

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.

Note

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

init

Retrieve initial context for experiment analysis

find_website

Find a website by its ID or URL

list_websites

List all available websites

list_experiments

Get the list of available experiments

read_experiment

Get experiment data by its URI

read_variation

Get variation data by its URI

read_goal

Get goal data by its URI

read_segment

Get segment data by its URI

list_experiments_performance_overview

Bulk performance overview for up to 10 experiments (users, conversion rate, revenue, leads, survey respondents) over a date range

get_experiment_performance_report

Get a performance report for an experiment

get_experiment_performance_chart_series

Get performance chart series for an experiment

Available resources

  • Experiment

  • Variation

  • Goal

  • Segment

Updated