Dingo vs Metamodel
A side-by-side look at the Dingo and Metamodel MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dingo for data science tools work as a local process; choose Metamodel 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 Dingo when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Metamodel when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
metamodel_list_projects, metamodel_get_schema, metamodel_compute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 60/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 759 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Dingo | View Metamodel |
Tools & capabilities
Dingo tools
No tool names declared yet. Check the project README from the listing page.
Metamodel tools 3
metamodel_list_projectsBrowse available calculators and engineering models. Returns project names, descriptions, publish tokens, and model names.metamodel_get_schemaDiscover inputs and outputs for a specific project. Returns model names, input parameters (with types, defaults, validation rules), output fields, and formulas.metamodel_computeRun a computation with input values. Send inputs once — they're auto-routed to the correct model by property name. Outputs from all models are returned, including cross-model cascading.
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.
Dingo
{
"mcpServers": {
"dataeval-dingo": {
"command": "uvx",
"args": [
"dingo-python"
]
}
}
}
Metamodel
{
"mcpServers": {
"metamodel-2": {
"command": "npx",
"args": [
"-y",
"metamodel-mcp"
]
}
}
}
Frequently asked questions
Dingo is categorized under Data Science Tools and uses a local stdio subprocess. Metamodel belongs to Data Science Tools and uses a local stdio subprocess. Pick Dingo for data science tools work and Metamodel 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.
Dingo is listed as free. Auth: no auth required. Metamodel 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 dataeval-dingo and metamodel-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dingo has a quality signal of 60/100 (Good) with 5 views, 0 installs and 759 GitHub stars. Metamodel has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.