M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGrowthBook MCP ServerOfficial GrowthBook MCP server: skill loader + authenticated API passthroughGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS60 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions9 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams already using GrowthBook who want agents to manage flags and experiments
  • MCP users who want an authenticated, auditable API passthrough
  • Operators of self-hosted instances
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users without GrowthBook
  • Read-only browsing without a GrowthBook API key
  • Environments that cannot tolerate agent-driven mutating API calls
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • GB_API_KEY: a GrowthBook API key or personal access token (required, secret)
  • GB_API_URL: API base URL (optional, defaults to https://api.growthbook.io)
  • GB_HTTP_HEADER_*: extra request headers (e.g. Cloudflare Access tokens)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • growthbook_call_api is a generic passthrough; POST/PUT/PATCH/DELETE can mutate data, and the confirm-with-user rule is soft guidance, not a hard gate
  • The API key is a sensitive credential that can act on the whole account if leaked
  • HTTP mode should run on a trusted network or loopback; multi-tenant or public deployments should be fronted by your own gateway/auth
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools315