Stata-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stata_doB | Execute 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_infoA | Get 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. |
| helpA | Retrieve 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_logA | Read a Stata log file (.log or .smcl) and return its content. Supports full, core, and dict output formats. Use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: executing do-files, reading log output, inspecting data, and retrieving command documentation. There is no overlap in purpose, so an agent can easily select the right tool.
Three tools follow a clear verb_noun pattern (read_log, get_data_info, stata_do), though 'stata_do' is slightly awkward as a noun_verb inversion. 'help' is a single verb, deviating from the pattern, but the overall naming remains predictable and readable.
With 4 tools covering the core workflow of running Stata analysis and inspecting outputs, the count feels appropriately scoped. It is on the lower end but not thin, as each tool addresses a substantial step.
The tool set covers the main lifecycle: execute a do-file, inspect its log, examine data, and get help for commands. Missing operations like dataset writing or interactive command execution are minor and can be worked around by using do-files.