MCP server for agent-run URL A/B testing. Create projects, allowlist domains, launch URL experiments, track conversions, and retrieve performance reports for customer-owned sites.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 23 tools
Each tool targets a distinct resource and action combination (e.g., domains_add, experiments_create, goals_deactivate, reports_experiment_chart). There is no overlap or ambiguity; even the three report tools serve clearly different purposes (totals, time-series, channel breakdown).
The vast majority of tools follow a resource_action snake_case pattern (domains_add, experiments_list). A couple deviate (billing_portal, usage_summary) but still place the resource first, making the pattern predictable and easy to parse.
With 23 tools covering projects, domains, experiments, goals, reports, billing, health, and usage, the count is well-scoped for a split-testing platform. Each tool addresses a specific need without ballooning into excessive granularity.
The tool surface provides CRUD-like operations for core entities (projects, experiments, goals, domains) and essential report types. Minor gaps exist (no goal update tool, no experiment delete—only archive) but these are reasonable trade-offs for the domain.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
domains_removeexperiments_archiveexperiments_create4 fields changedInput schema / properties / controlUrl / descriptionAdded value: +"Existing customer-owned URL for the control experience."Input schema / properties / targeting / descriptionPrevious value: -"Optional exact-match targeting filters. Use only documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields when available."New value: +"Optional targeting object. Device and visitor targeting are available on all plans; trafficFilters and geoFilters require Plus or Pro. Use documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields."Input schema / properties / urlPatternRules / descriptionPrevious value: -"Optional URL pattern rules for advanced URL matching. Prefer simple controlUrl/variationUrl first."New value: +"Optional Pro-only URL pattern rules for advanced matching across multiple paths. Prefer simple controlUrl/variationUrl first."Input schema / properties / variationUrl / descriptionAdded value: +"Existing customer-owned URL for the variation experience."experiments_getexperiments_list1 field changedInput schema / properties / status / descriptionAdded value: +"Optional lifecycle status filter."experiments_set_status2 fields changedInput schema / properties / experimentId / descriptionAdded value: +"Experiment ID returned by experiments_create or experiments_list."Input schema / properties / status / descriptionAdded value: +"Target lifecycle status. running starts the experiment; paused stops assignment without ending; ended records an end time."experiments_update6 fields changedInput schema / properties / controlUrl / descriptionAdded value: +"Replacement control URL. Omit to keep the current value."Input schema / properties / experimentId / descriptionAdded value: +"Experiment ID returned by experiments_create or experiments_list."Input schema / properties / targeting / descriptionPrevious value: -"Optional exact-match targeting filters. Use only documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields when available."New value: +"Optional targeting object. Device and visitor targeting are available on all plans; trafficFilters and geoFilters require Plus or Pro. Use documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields."Input schema / properties / trafficAllocation / descriptionAdded value: +"Replacement variation share. Accepts 0-1 or 0-100."Input schema / properties / urlPatternRules / descriptionPrevious value: -"Optional URL pattern rules for advanced URL matching. Prefer simple controlUrl/variationUrl first."New value: +"Optional Pro-only URL pattern rules for advanced matching across multiple paths. Prefer simple controlUrl/variationUrl first."Input schema / properties / variationUrl / descriptionAdded value: +"Replacement variation URL. Omit to keep the current value."goals_create3 fields changedInput schema / properties / eventName / descriptionAdded value: +"Exact event name the browser pixel will fire."Input schema / properties / name / descriptionAdded value: +"Human-readable goal name, e.g. Lead or Purchase."Input schema / properties / value / descriptionPrevious value: -"Optional default monetary value for this goal."New value: +"Optional default monetary value. Ignored when the plan does not include revenue tracking."goals_deactivategoals_list1 field changedInput schema / properties / active / descriptionAdded value: +"Optional filter. true returns active goals; false returns inactive goals."projects_archivebilling_portaldomains_adddomains_listexperiments_createexperiments_listexperiments_set_statusexperiments_updategoals_creategoals_listprojects_createprojects_getprojects_listprojects_updatereports_experiment_channelsreports_experiment_chartreports_experiment_detailssplitlaunch_healthcheckusage_summary
Add one secure layer between your agents and this server.