Stata MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATA_PATH | Yes | Stata executable path, e.g., /Applications/Stata/StataBE.app/Contents/MacOS/StataBE | |
| STATA_WORKSPACE | Yes | Stata working directory, e.g., /Users/username/Documents/Stata |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browse_do_filesA | 지정된 디렉토리의 do 파일 목록 조회 |
| read_do_fileC | 로컬 컴퓨터의 do 파일 읽기 |
| write_do_fileC | do 파일 생성 또는 덮어쓰기 |
| edit_do_fileC | do 파일의 특정 부분 편집 |
| generate_do_templateB | LLM을 활용한 do 파일 템플릿 생성 |
| run_do_fileC | Stata에서 do 파일 실행 |
| run_do_selected_linesB | do 파일의 선택된 라인들만 실행 |
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 7 tools
Each tool targets a distinct aspect of do file management: browsing directories, reading, writing, editing, generating templates, and running files or selected lines. There is minimal overlap between tools, and their purposes are clear from names and descriptions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., browse_do_files, run_do_file, generate_do_template). Naming conventions are uniform and predictable across the entire set.
With 7 tools, the server is well-scoped for its purpose of managing and executing Stata do files. Each tool covers a necessary function without redundancy or bloat.
The tool surface covers the full lifecycle of do file work: discover, view, create, edit, template, and run (both full and partial). There are no obvious gaps that would prevent an agent from completing typical Stata workflows.