Connect Statsig to Cursor
Give Cursor governed access to Statsig’s 93 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Statsig to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve Statsig in Runlayer
Add Statsig from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cursor to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Statsig’s 93 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to Statsig
Sign in the way Statsig requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Statsig from Cursor
Statsig’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
93 Statsig tools in Cursor
Runlayer policy decides which of these Cursor users can call.
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).
Control
What Runlayer can see and stop in Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every Statsig call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more