What is the key difference between Label Studio MCP Server and Discovery Engine?

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

How do I install Label Studio MCP Server or Discovery Engine 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 Label Studio MCP Server and Discovery Engine free or paid?

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

Which MCP server has more tools and community activity?

Label Studio MCP Server lists 2 tools with 3 views and 36 GitHub stars. Discovery Engine lists 6 tools with 4 views and 7 GitHub stars.

Can I use both Label Studio MCP Server and Discovery Engine 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

Label Studio MCP Server vs Discovery Engine

In-depth architectural comparison of the Label Studio MCP Server and Discovery Engine 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

Label Studio MCP Server

Data Science Tools · Local stdio

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

Discovery Engine

Data Science Tools · Local stdio

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

Verdict Summary: Choose Label Studio MCP Server if you need specialized Data Science Tools tools running via a local process. Choose Discovery Engine 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 Label Studio MCP Server 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: LABEL_STUDIO_API_KEY, LABEL_STUDIO_URL.
Primary tools included: model_version, score.

Explore Label Studio MCP Server Details

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.

Feature & Specification Comparison

Specification	Label Studio MCP Server HumanSignal Data Science Tools	Discovery Engine leap-laboratories Data Science Tools
Summary	Create, manage, and automate Label Studio projects, tasks, and predictions for data labeling workflows.	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.
Category & Scope

Tools & Capabilities Breakdown

Label Studio MCP Server Tools (2)

model_version

score

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

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

Label Studio MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "humansignal-label-studio-mcp-server": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/HumanSignal/label-studio-mcp-server",
        "mcp-label-studio"
      ],
      "env": {
        "LABEL_STUDIO_API_KEY": "YOUR_LABEL_STUDIO_API_KEY_HERE",
        "LABEL_STUDIO_URL": "YOUR_LABEL_STUDIO_URL_HERE"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Label Studio MCP Server More alternatives to Discovery Engine Data Science Tools category hub