What is the key difference between Discovery Engine and Growthbook MCP?

Discovery Engine belongs to the Data Science Tools category with local stdio execution, while Growthbook MCP belongs to the Data Science Tools category with local stdio execution.

How do I install Discovery Engine or Growthbook MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Discovery Engine and Growthbook MCP free or paid?

Discovery Engine operates under a Freemium model (API Key required). Growthbook MCP operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Discovery Engine lists 6 tools with 4 views and 7 GitHub stars. Growthbook MCP lists 4 tools with 3 views and 24 GitHub stars.

Can I use both Discovery Engine and Growthbook MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Discovery Engine vs Growthbook MCP

In-depth architectural comparison of the Discovery Engine and Growthbook 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

Discovery Engine

Data Science Tools · Local stdio

Quality: 52/100 (Good) | Auth: API Key required

Growthbook MCP

Data Science Tools · Local stdio

Quality: 67/100 (Great) | Auth: API Key required

Verdict Summary: Choose Discovery Engine if you need specialized Data Science Tools tools running via a local process. Choose Growthbook 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 Discovery Engine 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 (Freemium).
You have access to required keys: DISCOVERY_API_KEY.
Primary tools included: Feature interaction and subgroup discovery, Hold-out validation with FDR-corrected p-values, Effect sizes, support counts, and novelty classifications.

Explore Discovery Engine Details

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.

Feature & Specification Comparison

Specification	Discovery Engine leap-laboratories Data Science Tools	Growthbook MCP growthbook Data Science Tools
Summary	Superhuman exploratory data analysis that finds the feature interactions and subgroup effects that LLMs and manual exploration miss — with p-values, effect sizes, and literature citations. Data goes in, validated insights come out. Free for public data.	Tools for creating and interacting with GrowthBook feature flags and experiments.
Category & Scope

Tools & Capabilities Breakdown

Discovery Engine Tools (6)

Feature interaction and subgroup discovery

Hold-out validation with FDR-corrected p-values

Effect sizes, support counts, and novelty classifications

Academic literature citations for returned patterns

Asynchronous analysis submission and status tracking

Interactive report URLs and generated summaries

Growthbook MCP Tools (4)

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).

Discovery Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "leap-laboratories-discovery-engine": {
      "command": "uvx",
      "args": [
        "discovery-engine-api"
      ],
      "env": {
        "DISCOVERY_API_KEY": "YOUR_DISCOVERY_API_KEY_HERE"
      }
    }
  }
}

Growthbook MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "growthbook-growthbook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@growthbook/mcp"
      ],
      "env": {
        "GB_API_KEY": "YOUR_GB_API_KEY_HERE",
        "GB_API_URL": "YOUR_GB_API_URL_HERE",
        "GB_MCP_TRANSPORT": "YOUR_GB_MCP_TRANSPORT_HERE",
        "GB_MCP_PORT": "YOUR_GB_MCP_PORT_HERE",
        "GB_MCP_HOST": "YOUR_GB_MCP_HOST_HERE",
        "GB_MCP_URL": "YOUR_GB_MCP_URL_HERE",
        "GB_OAUTH_ISSUER": "YOUR_GB_OAUTH_ISSUER_HERE",
        "GB_SKILLS_ENABLED": "YOUR_GB_SKILLS_ENABLED_HERE"
      }
    }
  }
}

Frequently Asked Questions

Discovery Engine is categorized under Data Science Tools and uses a local stdio subprocess. In contrast, Growthbook MCP belongs to Data Science Tools using local stdio subprocess. Select Discovery Engine when you need capabilities focused on data science tools and Growthbook MCP when you require tools for data science tools.

More alternatives to Discovery Engine More alternatives to Growthbook MCP Data Science Tools category hub Canonical compare URL