Aurora vs Discovery Engine
A side-by-side look at the Aurora and Discovery Engine 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 Aurora for data science tools work as a local process; choose Discovery Engine 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 Aurora when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Discovery Engine | |
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 40/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | DISCOVERY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Aurora | View Discovery Engine |
Tools & capabilities
Aurora tools
No tool names declared yet. Check the project README from the listing page.
Discovery Engine tools
No tool names declared yet. Check the project README from the listing page.
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.
Aurora
{
"mcpServers": {
"aurora": {
"command": "uvx",
"args": [
"aurora-mcp"
]
}
}
}
Discovery Engine
{
"mcpServers": {
"leap-laboratories-discovery-engine": {
"command": "uvx",
"args": [
"discovery-engine-api"
],
"env": {
"DISCOVERY_API_KEY": "YOUR_DISCOVERY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Aurora is categorized under Data Science Tools and uses a local stdio subprocess. Discovery Engine belongs to Data Science Tools and uses a local stdio subprocess. Pick Aurora for data science tools work and Discovery Engine 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.
Aurora has no declared pricing — check the project's own site. Discovery Engine is listed as freemium — a free tier with paid plans. Auth: api key required. 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 aurora and leap-laboratories-discovery-engine as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aurora has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. Discovery Engine has 55/100 (Good) with 5 views, 0 installs and 7 GitHub stars.