4,000+ servers built on vurb.ts
Vinkius

Statsig MCP Server for ClineGive Cline instant access to 12 tools to Check Gate, Create Dynamic Config, Create Gate, and more

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Statsig through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The Statsig MCP Server for Cline is a standout in the Developer Tools category — giving your AI agent 12 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "statsig": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Statsig and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Statsig
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Statsig MCP Server

Connect your Statsig project to any AI agent to manage feature rollouts and product experiments through natural conversation.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Statsig tool calls without waiting for prompts between steps. Connect 12 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

What you can do

  • Feature Gates — Evaluate if a feature is enabled for a specific user or list all project gates
  • Dynamic Configs — Fetch JSON configurations and experiments to control app behavior without code changes
  • Event Logging — Log custom events for real-time analytics and metric calculation
  • Gate Management — Create, update, or delete feature gates directly via the Console API
  • Layer Inspection — Evaluate layers and retrieve parameter values for specific users

The Statsig MCP Server exposes 12 tools through the Vinkius. Connect it to Cline in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Statsig tools available for Cline

When Cline connects to Statsig through Vinkius, your AI agent gets direct access to every tool listed below — spanning feature-flags, ab-testing, product-experimentation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

check

Check gate on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user

create

Create dynamic config on Statsig

Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config

create

Create gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate

delete

Delete gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate

get

Get config on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment

get

Get dynamic config on Statsig

Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config

get

Get gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate

get

Get layer on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer

list

List dynamic configs on Statsig

Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project

list

List gates on Statsig

Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project

log

Log event on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation

update

Update gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate

Connect Statsig to Cline via MCP

Follow these steps to wire Statsig into Cline. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using Statsig

Ask Cline: "Using Statsig, help me...". 12 tools available

Why Use Cline with the Statsig MCP Server

Cline provides unique advantages when paired with Statsig through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Statsig + Cline Use Cases

Practical scenarios where Cline combined with the Statsig MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Statsig and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Statsig tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Statsig and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Statsig for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Statsig in Cline

Ready-to-use prompts you can give your Cline agent to start working with Statsig immediately.

01

"Check if the gate 'new_checkout_flow' is enabled for user 'user_99'."

02

"List all feature gates in my Statsig project."

03

"Create a new feature gate named 'mobile_redesign' with description 'Testing new UI'."

Troubleshooting Statsig MCP Server with Cline

Common issues when connecting Statsig to Cline through Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Statsig + Cline FAQ

Common questions about integrating Statsig MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →