Discovery Engine vs Stata MCP
A side-by-side look at the Discovery Engine and Stata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Discovery EngineData Science Tools · Local subprocess (stdio)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.55GoodAuth: api key requiredVerdict: choose Discovery Engine for data science tools work as a local process; choose Stata MCP for data science tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Discovery Engine when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DISCOVERY_API_KEY.
Choose Stata MCP when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
stata_do, get_data_info, help.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Discovery Engine | |
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | DISCOVERY_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 265 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Discovery Engine | View Stata MCP |
Tools & capabilities
Discovery Engine tools
No tool names declared yet. Check the project README from the listing page.
Stata MCP tools 4
stata_doExecute a Stata do-file and return the execution log. Accepts a do-file path, runs it via the configured Stata executable, and can optionally read log content only when return-code errors are detected. Use when you need to run Stata commands, perform regression or statistical analysis, or execute a do-file.get_data_infoGet descriptive statistics and a data preview for a supported data file (.dta, .csv, .tsv, .psv, .xlsx, .xls, .sav, .zsav). Returns overview, variable details, and optional head rows filtered by requested variables. Use when you need to understand a dataset or have no prior knowledge of the data.helpRetrieve documentation and usage information for a Stata command. Use when you need to understand a command's syntax, options, or troubleshoot errors before running it.read_logRead a Stata log file (.log or .smcl) and return its content. Supports full, core, and dict output formats. Use `lines` to return only the first/last N lines.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Discovery Engine
{
"mcpServers": {
"leap-laboratories-discovery-engine": {
"command": "uvx",
"args": [
"discovery-engine-api"
],
"env": {
"DISCOVERY_API_KEY": "YOUR_DISCOVERY_API_KEY_HERE"
}
}
}
}
Stata MCP
{
"mcpServers": {
"stata-mcp": {
"command": "uvx",
"args": [
"stata-mcp"
]
}
}
}
Frequently asked questions
Discovery Engine is categorized under Data Science Tools and uses a local stdio subprocess. Stata MCP belongs to Data Science Tools and uses a local stdio subprocess. Pick Discovery Engine for data science tools work and Stata MCP for data science tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Discovery Engine is listed as freemium — a free tier with paid plans. Auth: api key required. Stata MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add leap-laboratories-discovery-engine and stata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Discovery Engine has a quality signal of 55/100 (Good) with 5 views, 0 installs and 7 GitHub stars. Stata MCP has 53/100 (Good) with 1 views, 0 installs and 265 GitHub stars.