Metamodel vs Stata MCP
A side-by-side look at the Metamodel and Stata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Metamodel 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 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.
Choose Stata MCP 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.
- You want tools like
stata_do, get_data_info, help.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 267 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 3 | 4 |
| Full listing | View Metamodel | View Stata MCP |
Tools & capabilities
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.
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.
Metamodel
{
"mcpServers": {
"metamodel-2": {
"command": "npx",
"args": [
"-y",
"metamodel-mcp"
]
}
}
}
Stata MCP
{
"mcpServers": {
"stata-mcp": {
"command": "uvx",
"args": [
"stata-mcp"
]
}
}
}
Frequently asked questions
Metamodel 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 Metamodel 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.
Metamodel has no declared pricing — check the project's own site. Stata MCP is listed as free. Auth: no auth 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 metamodel-2 and stata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Metamodel has a quality signal of 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Stata MCP has 57/100 (Good) with 7 views, 0 installs and 267 GitHub stars.