Growthbook MCP vs Gnomon MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Growthbook MCP vs Gnomon MCP
In-depth architectural comparison of the Growthbook MCP and Gnomon MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Growthbook MCP
Data Science Tools · Local stdio
Quality: 67/100 (Great) | Auth: API Key required
Gnomon MCP
Data Science Tools · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Growthbook MCP if you need specialized Data Science Tools tools running via a local process. Choose Gnomon MCP if your workspace requires Data Science Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Growthbook MCP when:
You need dedicated capabilities in the Data Science Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: GB_API_KEY, GB_API_URL, GB_MCP_TRANSPORT, GB_MCP_PORT, GB_MCP_HOST, GB_MCP_URL, GB_OAUTH_ISSUER, GB_SKILLS_ENABLED.
Tools for creating and interacting with GrowthBook feature flags and experiments.
Deterministic batch tools so LLM agents stop next-token-guessing dates and math. Rich now() snapshot (18 fields), calendar(ops) batch dispatcher (diff/until/since/add/weekday/businessdays, natural-language parsing), calc(expressions) Python eval with math+stats pre-loaded, and Pint-based unit conversion. One wiring for dates + math + units. Listed in the official MCP Server Registry. uvx gnomon-mcp.
Category & Scope
Tools & Capabilities Breakdown
Growthbook MCP Tools (4)
growthbook_api_read
Make an authenticated GET request to the GrowthBook REST API. Use path (+ optional query string) exactly as shown in skill workflows that mention gb-call GET. Paths typically start with /api/v1/ or /api/v2/. Returns the raw response body on success. Queries the GrowthBook REST API — see https://docs.growthbook.io/api (OpenAPI: https://api.growthbook.io/api/v1/openapi.yaml).
growthbook_api_write
Make an authenticated mutating request (POST, PUT, PATCH, or DELETE) to the GrowthBook REST API. Use method + path (+ optional JSON body) exactly as shown in skill workflows that mention gb-call with those methods. Paths typically start with /api/v1/ or /api/v2/. Returns the raw response body on success. Mutates the GrowthBook REST API — see https://docs.growthbook.io/api (OpenAPI: https://api.growthbook.io/api/v1/openapi.yaml).
growthbook_list_skills
List available GrowthBook agent skills (name + description). Use growthbook_read_skill to load the full workflow for a skill before acting. Skills encode how to accomplish GrowthBook tasks well; use growthbook_api_read / growthbook_api_write to execute the REST calls they describe.
growthbook_read_skill
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Growthbook MCP is categorized under Data Science Tools and uses a local stdio subprocess. In contrast, Gnomon MCP belongs to Data Science Tools using local stdio subprocess. Select Growthbook MCP when you need capabilities focused on data science tools and Gnomon MCP when you require tools for data science tools.
Return the full markdown content of a GrowthBook skill by name (from growthbook_list_skills). Follow the skill's workflow; when it shows `gb-call <METHOD> <PATH> [body]`, use growthbook_api_read for GET and growthbook_api_write for POST/PUT/PATCH/DELETE.