Eppo logoMCP server · Analytics

Eppo MCP server

Eppo in any MCP client, through Memtro: Eppo does not publish this server. Memtro's Eppo connector reads Eppo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Eppo experimentation and feature flags: experiments by status, tag and date with their hypothesis, variations, progress, winner, outcome and takeaways, an experiment's diagnostic checks, feature flags with their environments, variations and allocations, metrics, environments and tags; when you ask, can duplicate, refresh or delete an experiment, add a metric collection to one, create or edit a flag, turn a flag on or off in an environment, add or archive an allocation, archive a flag, and create or delete tags.

Reads

  • eppo_list_experimentsList Eppo experiments: status, hypothesis, dates, variations, progress, winner, outcome, decision reason and key takeaways…
  • eppo_get_experimentRead one Eppo experiment by id: everything eppo_list_experiments shows, for one experiment.
  • eppo_experiment_diagnosticsRead an Eppo experiment's diagnostic checks (assignments, traffic imbalance, metric data, compute status) with each one's status and error…
  • eppo_list_feature_flagsList Eppo feature flags with their key, description, whether each environment has it on, tags and when they changed.
  • eppo_get_feature_flagRead one Eppo feature flag by id with its environments, variations and allocations (targeting, exposure and any experiment).
  • eppo_list_metricsList Eppo metrics: type, description, desired direction, whether certified, minimum detectable effect and guardrail cutoff.
  • eppo_list_environmentsList Eppo's flag environments with their ids and which is production.
  • eppo_list_tagsList the tags used on Eppo experiments and flags, with ids.

Acts, when you ask

These change something in Eppo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • eppo_duplicate_experimentCopies an Eppo experiment into a new one with the name you give (and optionally a new hypothesis).
  • eppo_refresh_experiment_resultsAsks Eppo to recompute an experiment's results now.
  • eppo_delete_experimentDeletes an Eppo experiment.
  • eppo_add_metric_collectionAdds a metric collection's metrics to an Eppo experiment, so they appear in its results.
  • eppo_create_feature_flagCreates an Eppo feature flag with the key, variations and entity you give.
  • eppo_update_feature_flagRenames an Eppo feature flag or changes its description or tags (tags, if given, replace the flag's tags).
  • eppo_set_flag_environmentTurns an Eppo feature flag on or off in one environment.
  • eppo_create_allocationAdds a targeting allocation to an Eppo feature flag in one environment: who it applies to (rules on subject attributes, and/or saved audiences)…
  • eppo_archive_allocationArchives one allocation of an Eppo feature flag, so its targeting stops being served.
  • eppo_archive_feature_flagArchives an Eppo feature flag.
  • eppo_create_tagCreates a tag in Eppo for labelling experiments and flags.
  • eppo_delete_tagPermanently deletes an Eppo tag; experiments and flags lose it.

Connect it

First connect Eppo on Dashboard → Connections, then add Memtro to your client once. The Eppo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Eppo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which experiments are running, and who is winning?
  • › Why does the checkout experiment have no results?
  • › Which feature flags are on in production?
  • › Which metrics are certified, and what is their guardrail cutoff?
  • › Turn the new-pricing flag off in staging.

Questions

Is this an official Eppo MCP server?
No. It is Memtro's MCP server with Memtro's Eppo connector behind it: the connector reads Eppo through its API with the credentials you connect on Dashboard → Connections, and Eppo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Eppo?
Only when you ask, and only what it has been granted: duplicate an experiment under a new name; refresh an experiment's results (runs queries on your data warehouse); delete an experiment; add a metric collection to an experiment; create a feature flag; rename a feature flag or change its description or tags; turn a feature flag on or off in an environment; add a targeting allocation to a feature flag; archive an allocation of a feature flag; archive a feature flag; create a tag; delete a tag. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Analytics

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time