X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Statsig MCP with Hermes

Connect Hermes to Statsig MCP. List all active experiments for project, create a feature gate named beta, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Statsig MCP logoStatsig MCP
Dcr Oauth

Statsig MCP is a feature experimentation platform exposing experiments, feature gates, dynamic configs, layers, metrics, segments, and observability workflows. Use it to safely rollout features, measure impact, and iterate quickly.

86 Tools

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Statsig account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Statsig MCP with

ChatGPT WorkClaude Cowork

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,500+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Statsig with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Statsig

Ask your agent to connect to Statsig, or simply request any Statsig-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Statsig connection.

Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Statsig or request any Statsig-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Statsig MCP server, and what's possible with it?

The Statsig MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Statsig account. It provides structured and secure access so your agent can perform Statsig operations on your behalf.

Way Forward

With Statsig connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

TOOLS

Supported Tools

Every Statsig MCP action and event your agent gets out of the box.

Approve autotune review

Approve an in-flight review of an autotune experiment.

Approve dynamic config review

Approve an in-flight review of a dynamic config.

Approve experiment review

Approve an in-flight review of an experiment (A/B test).

Approve gate review

Approve an in-flight review of a gate (feature flag).

Cancel autotune review

Cancel (withdraw) an in-flight review of an autotune experiment.

Cancel dynamic config review

Cancel (withdraw) an in-flight review of a dynamic config.

Cancel experiment review

Cancel (withdraw) an in-flight review of an experiment (A/B test).

Cancel gate review

Cancel (withdraw) an in-flight review of a gate (feature flag).

Cluster log patterns

Cluster similar log lines into templates (same as `statsig-query log-patterns`).

Commit autotune review

Commit a review of an autotune experiment, APPLYING its proposed change to the live autotune.

Commit dynamic config review

Commit a review of a dynamic config, APPLYING its proposed change to the live config.

Commit experiment review

Commit a review of an experiment (A/B test), APPLYING its proposed change to the live experiment.

Commit gate review

Commit a review of a gate (feature flag), APPLYING its proposed change to the live gate.

Create autotune

Create an Autotune (multi-armed bandit) experiment that automatically shifts traffic toward the best-performing variant.

Create autotune review

Open a review proposing a change to an autotune experiment.

Create dynamic config

Create a new Dynamic Config (static, targetable JSON object) in the Statsig console, including targeting rules, its ID (how we'll refer to it in-code) and its IDtype, which it'll randomize users on.

Create dynamic config review

Open a review proposing a change to a dynamic config.

Create experiment

Create an experiment, including its ID (which is how we refer to it in-code), its groups (test/control, and return values) and the ID type it should randomize users on.

Create experiment review

Open a review proposing a change to an experiment (A/B test).

Create gate

Create a new gate (feature flag), including its rules (who should pass it) its ID (how we'll refer to it in-code) and its IDtype, which it'll randomize users on.

Create gate review

Open a review proposing a change to a gate (feature flag).

Create layer

Create a new layer, including its name, ID type, and optional target apps or team ownership.

Create param store

Create a new Param Store (a reusable, named collection of typed parameters) in this Statsig project.

Create segment

Create a new segment, including its name, type, optional ID, ID type, and rules for rule-based segments.

Delete experiment

Delete an experiment (A/B test) by ID.

Delete param store

Delete a Param Store by name.

Edit autotune review

Edit an in-flight autotune review's metadata — description and/or requested reviewers.

Edit dynamic config review

Edit an in-flight dynamic config review's metadata (description, requested reviewers) and/or its proposed `change`.

Edit experiment review

Edit an in-flight experiment (A/B test) review's metadata — description and/or requested reviewers.

Edit gate review

Edit an in-flight gate (feature flag) review's metadata (description, requested reviewers) and/or its proposed `change`.

Fetch

Fetch the full document for a search result id.

Get audit logs

List audit logs for this Statsig project.

Get autotune eligible reviewers

List the users and reviewer groups eligible to approve/reject a review of this autotune experiment.

Get autotune review by id

Get a single review for an autotune experiment by its review ID, including its status, proposed change type, author, and requested reviewers.

Get dynamic config details by id

Get the details (including rules, return values, and more) for a Dynamic Config (static, targetable JSON) in the Statsig console.

Get dynamic config eligible reviewers

List the users and reviewer groups eligible to approve/reject a review of this dynamic config.

Get dynamic config review by id

Get a single review for a dynamic config by its review ID, including its status, proposed change, author, and requested reviewers.

Get dynamic config version history

List historical versions of a Dynamic Config (static, targetable JSON object) to reconstruct a timeline of how it changed — rules, return values, defaults, and metadata across edits.

Get experiment details by id

Get details including parameters (return values), groups, status & more of an experiment in Statsig.

Get experiment eligible reviewers

List the users and reviewer groups eligible to approve/reject a review of this experiment (A/B test).

Get experiment metric dimension results

Get topline and dimensional breakdown results for one specific experiment metric.

Get experiment overall results

Get overall pulse results for an experiment across all pulse metrics.

Get experiment review by id

Get a single review for an experiment (A/B test) by its review ID, including its status, proposed change type, author, and requested reviewers.

Getexperimentsummarycharts

Get Experiment Summary charts and underlying data.

Get experiment version history

List historical versions of an experiment (AB Test) to reconstruct a timeline of how it changed — groups, allocation, status, parameters, and metadata across edits.

Get gate details by id

Get all details about a gate (feature flag) like its rules, idType, and more, from the Statsig Console.

Get gate eligible reviewers

List the users and reviewer groups eligible to approve/reject a review of this gate (feature flag).

Get gate results

Get the metric results for a given gate and rule in the gate

Get gate review by id

Get a single review for a gate (feature flag) by its review ID, including its status, proposed change, author, and requested reviewers.

Get gate version history

List historical versions of a gate (feature flag) to reconstruct a timeline of how it changed — rules, IDtype, enabled state, and metadata across edits.

Get layer details by id

Get all details about a layer, including its parameters and metadata, from the Statsig Console.

Get layer experiments

List the experiments in a layer, including each experiment's allocation and groups within the layer.

Get layer overrides

Get the conditional and ID overrides configured for a layer in the Statsig Console.

Get list of autotune reviews

List the reviews for an autotune experiment, newest first.

Get list of dynamic config reviews

List the reviews for a dynamic config, newest first.

Get list of dynamic configs

List all Dynamic Configs (static, targetable JSON objects) in this Statsig project.

Get list of experiment reviews

List the reviews for an experiment (A/B test), newest first.

Get list of experiments

List all experiments (AB Tests) in this Statsig project.

Get list of gate reviews

List the reviews for a gate (feature flag), newest first.

Get list of gates

List all gates (feature flags) in this Statsig project.

Get list of layers

List all layers in this Statsig project.

Get list of metrics

List all metrics in this Statsig project.

Get list of metric sources

List all metric sources in this Statsig project.

Get list of param stores

List param stores in this Statsig project.

Get list of segments

List all segments in this Statsig project.

Get list of tags

List all tags in this Statsig project, returning each tag's id and name.

Get metric definition by id

Get the full definition for a metric in Statsig, including its type, source, and configuration details.

Get param store details by id

Get a param store by name, including its description, typed parameters, and metadata.

Get segment by id

Get all details about a segment in the Statsig Console.

Get tool schema

Get the full input schema, description, and annotations for any Statsig MCP tool by name — including tools not shown in the default tool list (find them with Search_Tools).

Invoke tool

Execute any Statsig MCP tool by name with arguments — including tools not shown in the default tool list.

Query logs explorer

Fetch log lines from Statsig Logs Explorer (MCP equivalent of `statsig-query logs`).

Reject autotune review

Reject an in-flight review of an autotune experiment.

Reject dynamic config review

Reject an in-flight review of a dynamic config.

Reject experiment review

Reject an in-flight review of an experiment (A/B test).

Reject gate review

Reject an in-flight review of a gate (feature flag).

Search

Search the Statsig MCP data source and return relevant results.

Search tools

Search the full catalog of Statsig MCP tools by keyword.

Start experiment code cleanup

Start code cleanup for a stale experiment by name, which creates a PR to remove the experiment from your codebase.

Start gate code cleanup

Start code cleanup for a gate by name, which creates a PR to remove the gate from your codebase.

Update dynamic config entirely

Fully update a dynamic config, replacing everything the dynamic config currently has on the Statsig console with the data included in this POST request.

Update experiment entirely

Fully update an experiment, replacing everything the experiment currently has on the Statsig console with the data included in this POST request.

Update gate entirely

Fully update a gate, replacing everything the gate currently has on the Statsig console with the data included in this POST request.

Update layer entirely

Fully update a layer, replacing everything the layer currently has on the Statsig console with the data included in this POST request.

Update param store

Update an existing Param Store by name.

Update segment

Update a Statsig segment using the appropriate segment endpoint.

FRAMEWORKS

How to build Statsig MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use Statsig MCP with ChatGPT Work

Claude Cowork logo

Claude Cowork

Use Statsig MCP with Claude Cowork

FAQ

Frequently asked questions

With a standalone Statsig MCP server, the agents and LLMs can only access a fixed set of Statsig tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Statsig and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Statsig tools.

Yes, absolutely. You can configure which Statsig scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Statsig data and credentials are handled as safely as possible.

Start with Statsig MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Statsig MCP tool your agent needs.Free to start.

Start building