How to connect Statsig to Claude

Connect Claude Web, Desktop and Cowork to Statsig MCP. Enable feature flag for user cohort, roll out config change to 10% users, and more using natural language, with authentication handled for you.

Statsig logoStatsig
Api Key

Statsig is a server-side platform for feature gate evaluation, dynamic configuration, experimentation, and event measurement. It helps teams safely roll out features, measure impact, and iterate quickly.

7 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Statsig account to Claude via Composio Connect, enabling it to enable feature flag for user cohort, roll out config change to 10% users, fetch experiment metric results for signup_flow, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Statsig with

Connecting Statsig to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Statsig account

Back in Claude, ask it to connect to Statsig or give it any Statsig-related task.

For example, ask Claude to:

  • "Enable feature flag for user cohort"
  • "Roll out config change to 10% users"
  • "Fetch experiment metric results for signup_flow"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Statsig account is ready to use.

What is the Statsig Claude Connector, 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.

Troubleshooting

1. Why does Claude not use the Composio connector for Statsig?

The connector can show as connected, but Claude must use it in each Statsig conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Statsig again.

2. Why does Claude show an MCP server error before Statsig connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Statsig.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Statsig.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Statsig authorization link not work?

The Composio connector is one server. Your Statsig account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Statsig connection.
  • Composio creates a fresh Statsig authorization link.
  • Open that link in your browser and finish the Statsig sign-in.

4. Why do Statsig actions fail after they worked before?

The Statsig connection can expire or lose permission.

  • Ask Claude to inspect the Statsig connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Statsig account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Statsig.
  • If the action still fails with a permission error, check that the connected account has that permission in Statsig itself.

5. How do I switch to a different Statsig account?

Claude can manage the Statsig connection for you.

  • Ask Claude to disconnect or delete the current Statsig account.
  • Ask Claude to connect Statsig again.
  • Open the new Composio authorization link for Statsig.
  • Sign in with the other Statsig account in the browser.
  • After the account connects, ask Claude to retry the Statsig task.

6. Why is my Statsig connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Statsig connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Statsig tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Statsig.
TOOLS

Supported Tools

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

Check Feature Gate

Evaluate one Statsig feature gate with optional user context without logging an exposure.

Check Feature Gates

Evaluate multiple Statsig feature gates with optional shared user context without logging exposures.

Get Dynamic Config

Evaluate a Statsig dynamic config or experiment with optional user context and return its value and assignment metadata without logging an exposure.

Get Layer

Evaluate a Statsig layer with optional user context and return its parameter values and assignment metadata without logging an exposure.

Get Ranked Variants

Rank variants for a Statsig contextual-bandit Autotune configuration using optional user context without logging an exposure.

Log Custom Exposures

Permanently log one or more Statsig gate, experiment, or dynamic-config exposures when automatic exposure logging is not being used.

Log Events

Permanently log one or more custom Statsig events for analytics and metric calculation in a single batch.

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. Claude Cowork 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.It takes 30 seconds.

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

Start building