Add Statsig third-party MCP plugin - #369
Open
SamSokolin wants to merge 1 commit into
Open
Conversation
Package Statsig's official hosted MCP (https://api.statsig.com/v1/mcp) as a marketplace plugin using Streamable HTTP with OAuth user login and no API keys. Related to EXTY-1365 Co-authored-by: Sam Sokolin <SamSokolin@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Packages Statsig's official remote MCP server as a marketplace / Grok Bot connector plugin at
third_party/statsig/, following the existing third-party OAuth HTTP pattern (Attio #339, Clay, Intercom, Calendly).Related to EXTY-1365 (https://linear.app/anysphere/issue/EXTY-1365/agents-have-no-single-reliable-path-to-read-statsig) — that ticket covers broader skill routing; this PR is the public HTTP connector packaging slice.
Originating ask: xai-fte Slack, channel C0BQKE29LNP, thread p1789255395993009.
What's in the plugin
mcp.json— URL-only Streamable HTTP config pointing at Statsig's hosted endpoint. Auth is OAuth; Cursor handles the sign-in on first use. No secrets, client IDs, or env templates.{ "mcpServers": { "statsig": { "type": "http", "url": "https://api.statsig.com/v1/mcp" } } }.cursor-plugin/plugin.json—name: statsig,category: integrations, author Cursor / plugins@cursor.com, homepage → https://docs.statsig.com/integrations/mcp/cursor,mcpServers: ./mcp.json. Fields mirror Attio's manifest.README.md— install steps, MCP config, prerequisites (Statsig org owner must enable Personal Console API Keys for the user's role; OAuth only supports those), capabilities table, notes.LICENSE(MIT),CHANGELOG.md(1.0.0).assets/logo.png— Statsig's official hexagon mark from thestatsig-ioGitHub org, resized to 192×192 RGBA PNG like Attio.Registration
statsigentry to.cursor-plugin/marketplace.json.statsigrow to the rootREADME.mdplugins table.Not included (by design)
npx mcp-remote/ Console API key stdio alternative — the docs list it as a fallback, but this plugin ships the recommended OAuth HTTP setup only.Verification
third_party/statsig, no marketplace entry).npm install --no-save ajv ajv-formats && node scripts/validate-plugins.mjs→All plugins validated successfully.