Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldGrowthBookWatchlist candidateContext7 MCPMCP100 Selected
Task fit
Best for
  • GrowthBook teams that want a small MCP surface for skills plus authenticated GrowthBook API operations.
  • Current library and API documentation inside coding agents
  • Read-only technical lookup with a small two-tool surface
  • Users who want remote or local npx connection options
Not ideal for
  • Users who expect a large purpose-built tool set or a hard technical confirmation gate before every mutation.
  • Private internal documentation not indexed by Context7
  • Guaranteed authoritative answers without checking the cited upstream docs
  • Offline-only development
Avoid when
  • Do not rely on prompt/instruction-level confirmation guidance as a hard security boundary for POST/PUT/PATCH/DELETE API calls.
  • Your policy prohibits sending formulated documentation queries to a hosted service
  • You require complete or guaranteed-correct community-contributed documentation
  • You cannot keep an API key out of shared configuration
Provenance
Provenance details

First-party MCP

io.github.growthbook · Publisher source ↗

First-party MCP

Upstash · Publisher source ↗

Maintenance
Maintenance details

Stale

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Aug 11, 2026

Popularity evidence
GitHub starsNot documented

60,740

GitHub stars · checked 2026-08-14T18:46:26.000Z

Package downloads / 30 daysNo reliable download data

3,916,841

package downloads / 30 days · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • npm: package downloads: 3,916,841Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHTTP mode supports OAuth; stdio mode can use a GrowthBook API key/personal access token.Remote MCP accepts CONTEXT7_API_KEY as an HTTP header. The local package accepts --api-key. The CLI can use OAuth to generate an API key; unauthenticated documentation commands may have lower limits.
CostGrowthBook plan/API usage and model/provider costs apply.A free API key and free usage are documented, with higher-rate or team/enterprise offerings potentially requiring a paid plan. Applicable limits should be checked in the current Context7 dashboard.
PermissionsThe generic API call can reach operations allowed by the credential, including mutations. Publisher guidance asks agents to confirm mutations, but this is not a hard security gate.The MCP surface resolves library identifiers and queries documentation. It does not require repository or filesystem write access for the documented hosted mode.
Data handlingGrowthBook feature flag/experiment/project data and API payloads can flow to the AI client/provider.Context7 states that formulated queries are sent to its API while full prompts, source code, and conversation history are not transmitted; its tool descriptions instruct clients to remove secrets, personal data, and proprietary code.
Limitations
Tradeoffs
  • Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Selected.
  • An API key is recommended for higher limits, adding account and secret management.
  • Context7 says it sends formulated queries rather than full prompts or source code, but queries still leave the client.
  • Community-contributed projects can be incomplete or inaccurate and should be checked against primary documentation.
Risk contextBroad API passthrough under one tool can make mutating authority less obvious than a purpose-specific tool inventory.Primary risks are query disclosure, stale or inaccurate indexed documentation, and accidental API-key exposure. Keep queries free of proprietary details and verify consequential advice against first-party library documentation.
Evidence date
Editorial review2026-09-13T00:00:00Z2026-07-24
Candidate evidence2026-09-13T00:00:00Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →