STATA-MCP Repro
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 |
|---|---|
| project_statusC | Inspect selected project, Stata, backend, and capabilities. |
| project_initC | Initialize one project with a human-readable relative artifact path. |
| plan_prepareC | Create or update a privacy-safe draft analysis plan. |
| plan_approveB | Freeze a ready analysis plan with explicit approval evidence. |
| run_prepareA | Create an immutable, descriptively named run without executing it. |
| run_executeB | Execute one prepared run synchronously or in the background. |
| run_statusB | Read durable lifecycle state and provenance paths for one run. |
| run_controlB | Request cancellation of one active background run. |
| data_inspectB | Inspect dataset metadata, missingness, labels, and bounded previews. |
| artifact_readA | Read one bounded text or image artifact belonging to a run. |
| results_getB | Return typed structured results bound to one finalized run. |
| graph_getB | List run graphs or read one bounded, verified graph payload. |
| stata_helpB | Retrieve Stata command documentation through licensed local Stata. |
| stata_doC | Deprecated: prepare and execute a project-local run. |
| get_data_infoC | Deprecated: use data_inspect. |
| helpB | Deprecated: use stata_help. |
| read_logC | Deprecated: use artifact_read. |
| write_dofileC | Deprecated: use run_prepare. |
| append_dofileD | Deprecated: create an immutable child run with run_prepare. |
| read_fileD | Deprecated: use artifact_read. |
| load_figureC | Deprecated: use artifact_read. |
| mk_dirD | Removed: initialize a project once; server owns artifact directories. |
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 22 tools
Active tools have distinct purposes across planning, project management, run lifecycle, data inspection, and output retrieval. Deprecated tools are clearly labeled with redirecting messages, so misselection is unlikely despite some overlap in names.
All tools use snake_case, but there is a clear split: active tools favor object_verb naming (e.g., run_prepare, data_inspect) while deprecated tools use verb_object naming (e.g., write_dofile, read_file). This mixed pattern reduces readability, though deprecated markers mitigate confusion.
The total of 22 tools is heavy, and 9 of them are deprecated, artificially inflating the surface. The active 13 tools form a well-scoped set, but the obsolete entries should be removed to bring the count into an ideal range.
The active tool chain covers the full reproducibility lifecycle: plan preparation and approval, project initialization, run preparation/execution/monitoring, and artifact retrieval. Minor gaps like lack of list operations for runs or projects are workable.