Statbel Be vs Stata MCP

A side-by-side look at the Statbel Be and Stata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Statbel Be logoStatbel BeData Science Tools · Local subprocess (stdio)Statbel — Statistics Belgium (be.STAT / bestat) open data MCP.57GoodAuth: not declaredStata MCP logoStata MCPData Science Tools · Local subprocess (stdio)Let LLM help you achieve your regression analysis with Stata57GoodAuth: no auth required

Verdict: choose Statbel Be 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?

Statbel Be logoChoose Statbel Be when

  • You need dedicated capabilities in the Data Science Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like list_views, get_view, list_datasets.
Explore Statbel Be

Stata MCP logoChoose 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.
Explore Stata MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStatbel Be logoStatbel BeStata MCP logoStata MCP
CategoryData Science ToolsData Science Tools
Quality signal57/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0267
Directory activity 1 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools44

Tools & capabilities

Statbel Be tools 4

  • list_viewsBrowse/search Statbel (Statistics Belgium, be.STAT) saved statistical views. Each view is a pre-built table over a dataset and carries a single locale (nl/fr/de/en). Returns id, name, locale, dataSourceId and publish dates. Filter by case-insensitive substring of the view name (matches in any language).
  • get_viewMetadata for one Statbel view by its id (a UUID, e.g. from list_views). Returns the view object: name, locale, dataSourceId (the underlying dataset), and publish/change dates. To get the dataset description in all available languages, pass the returned dataSourceId to get_dataset.
  • list_datasetsBrowse/search Statbel datasets (be.STAT "datasources"). Each dataset has a `name` code (e.g. "IM_EAF_HOUSE_SALES_IDX"), a `descriptions` map with one entry per supported language (nl/fr/de/en), a category id, supportedLocales, and last-update timestamps. Filter by case-insensitive substring matched against the dataset code and all-language descriptions.
  • get_datasetMultilingual metadata for one Statbel dataset by its id (a UUID, e.g. the dataSourceId from a view). Returns the dataset code `name`, the `descriptions` map (nl/fr/de/en text), supportedLocales, defaultLocale, category id and update dates.

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.

Statbel Be

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "statbel-be": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-statbel-be"
      ]
    }
  }
}

Stata MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "stata-mcp": {
      "command": "uvx",
      "args": [
        "stata-mcp"
      ]
    }
  }
}

Frequently asked questions

Statbel Be 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 Statbel Be 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.

Statbel Be 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 statbel-be and stata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Statbel Be has a quality signal of 57/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.