A community-driven registry for Claude, Cursor, Windsurf, Cline & more. Not affiliated with Anthropic.
Are you the author? Sign in to claim
A VS Code compatible extension (Cursor, Windsurf, Antigravity etc.) that allows Stata code to be run directly from the e
Stata Workbench is unified agentic toolkit for Stata development. The toolkit gives AI agents native control over Stata - run commands, inspect variables, export graphs, and build more quickly and reliably than native Stata alone. Built as a VS Code extension (Cursor, Windsurf, Antigravity), so your agent works inside your editor. Powered by mcp-stata. Featured in
News.
Built by Thomas Monk, London School of Economics.
Run Stata without leaving your editor. Execute code, see output, and view graphs - all within VS Code. No switching windows, no copying and pasting between your do-file editor and an AI chat.
For solo work: A modern IDE for Stata—autocomplete, syntax highlighting, multiple cursors, and an AI assistant that can run commands, inspect your variables, and debug errors directly.
For collaboration: Co-authors work in the same environment they use for other code. Shared editor settings, consistent formatting, and AI assistants that understand your project structure.
For teaching: Students learn Stata with the same tools they'll use for everything else - inline errors, an integrated terminal, and an AI that can explain what went wrong.
Install directly from the marketplace listings by searching for Stata Workbench in the Extensions view.
Offline fallback:
Ctrl+Shift+P or Cmd+Shift+P on Mac) and select Extensions: Install from VSIX....Install the Stata Workbench extension.
Open a .do file in VS Code (or a compatible editor).
Run Stata: Run Selection/Line (press the play button on the top right). The Stata Terminal panel opens automatically the first time you run a command. You can interact with this as you would a standard Stata terminal.
Run:
sysuse auto, clear
summarize
Output appears as output cards in the panel.
Run:
scatter price mpg
A Graph artifact card appears - click it to open the generated graph.
Open the Data Browser panel to view your data live.
Stata Terminal panel showing output cards and a graph artifact.
Data Browser allows for a live view of your data, with filtering and sorting.
mcp-stata toolkit. If it is not found, you will be prompted to run the installation script.Stata Workbench is a unified agentic toolkit for Stata development, providing a rich IDE experience with deep AI integration:
stata-workbench.viewData): High-performance view of millions of rows (~20x faster with Apache Arrow) with live filtering and sorting.stata-workbench.runSelection): Executes the selected code or current line via MCP tool run_command with normalized output and graphs.stata-workbench.runFile): Runs the entire .do file via MCP tool run_do_file.stata_manage_session action="detect"): Returns Stata version, flavor, and OS metadata.stata_inspect_data action="lint"): Static analysis of .do and .ado files to identify style violations and potential errors.gtools, and other modern Stata features instead of legacy anti-patterns.scripts/setup_toolkit.py): Automated registration for Claude Desktop, Codex, VS Code, and Cursor in one command.mcp.json) across your favorite AI editors.stata-workbench.cancelRequest): Live request states with one-click cancellation.stata-workbench.testMcpServer): Quick smoke checks to verify your Stata connection..do, .ado, .mata, Dyndoc Markdown, and Dyndoc LaTeX.stata-workbench.installMcpCli): Bootstraps the mcp-stata toolkit locally when it is missing from the environment.Stata Workbench output channel for persistent reference.For a detailed breakdown of all capabilities, see FEATURES.md.
stataMcp.requestTimeoutMs (default 100000): timeout for MCP requests.stataMcp.autoRevealOutput (default false): automatically show the output channel after runs.stataMcp.autoConfigureMcp (default true): automatically add/update the mcp-stata server entry in your host MCP config (mcp.json).stataMcp.configureClaudeCode (default false): register mcp-stata via claude mcp add-json at user scope. Ensures both Claude Code CLI and VS Code extension see the server. Requires claude on PATH.stataMcp.configureCodex (default false): also configure Codex CLI and VS Code extension MCP settings.stataMcp.codexConfigPath (default ~/.codex/config.toml): path to Codex MCP config. Supports ~ and ${workspaceFolder}.stataMcp.runFileWorkingDirectory (default empty): working directory when running .do files. Supports an absolute path, ~, ${workspaceFolder} or ${fileDir}; empty uses the .do file's folder.stataMcp.setupTimeoutSeconds (default 60): timeout (seconds) for Stata initialization.stataMcp.noReloadOnClear (default false): disable reloading startup/profile do files after clear all/program drop.stataMcp.maxOutputLines (default 0): limit Stata output to N lines (0 = unlimited). Useful for reducing token usage with AI agents.stataMcp.runFileBehavior (default runDirtyFile): choose whether 'Run File' should run the current editor content (including unsaved changes) or the version saved on disk.stataMcp.defaultVariableLimit (default 100): default number of variables to select when opening the Data Browser (0 = all). Useful for huge datasets.MCP configuration is synced on extension load and when you toggle the relevant settings. When a setting is enabled, the extension adds or updates the mcp-stata entry in that config. When you turn the setting off, the extension removes the mcp_stata entry cleanly.
| When | Behaviour |
|---|---|
| Extension loads | Adds/updates mcp-stata in each enabled config target |
| Setting toggled ON | Adds/updates mcp-stata in that config |
| Setting toggled OFF | Removes mcp_stata from that config |
The extension detects your editor and writes to the appropriate config file(s).
mcp.json with Stata MCP server entrymcp-stata installer.stataMcp.configureClaudeCode is enabledstataMcp.configureCodex is enabledConfig file locations:
| Editor | macOS | Windows | Linux |
|---|---|---|---|
| VS Code | ~/Library/Application Support/Code/User/mcp.json | %APPDATA%/Code/User/mcp.json | ~/.config/Code/User/mcp.json |
| VS Code Insiders | ~/Library/Application Support/Code - Insiders/User/mcp.json | %APPDATA%/Code - Insiders/User/mcp.json | ~/.config/Code - Insiders/User/mcp.json |
| Cursor | ~/.cursor/mcp.json | %USERPROFILE%/.cursor/mcp.json | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | %USERPROFILE%/.codeium/windsurf/mcp_config.json | ~/.codeium/windsurf/mcp_config.json |
| Windsurf Next | ~/.codeium/windsurf-next/mcp_config.json | %USERPROFILE%/.codeium/windsurf-next/mcp_config.json | ~/.codeium/windsurf-next/mcp_config.json |
| Antigravity | ~/Library/Application Support/Antigravity/User/mcp.json | %APPDATA%/Antigravity/User/mcp.json | ~/.antigravity/mcp.json |
| Claude Code CLI & extension | Via claude mcp add-json (user scope) | same | same |
| Codex CLI & extension | stataMcp.codexConfigPath (default ~/.codex/config.toml) | same | same |
If you want to manage the file yourself, here is the content to add. User-level mcp.json:
{
"servers": {
"mcp_stata": {
"type": "stdio",
"command": "uvx",
"args": ["--refresh", "--refresh-package", "mcp-stata", "--from", "mcp-stata@latest", "mcp-stata"]
}
}
}
claude mcp add-json so both CLI and extension share the same config. Ensure claude is on PATH and stataMcp.configureClaudeCode is enabled. Restart the Claude Code panel after changes..do file, click the ... menu in the editor title bar and enable the Stata Workbench icons to make them visible.mcp-stata manually with curl -LsSf https://mcp-stata-install.tdmonk.com/install.sh | bash (macOS/Linux) or irm irm https://mcp-stata-install.tdmonk.com/install.ps1 | iex | iex (Windows).stataMcp.requestTimeoutMs.Stata: Cancel Current Request from the command palette.Automatic removal: Turn off stataMcp.autoConfigureMcp, stataMcp.configureClaudeCode, or stataMcp.configureCodex in settings; the extension removes the mcp_stata entry immediately.
Manual removal: Edit the config file and delete the relevant entry:
servers.mcp_statamcpServers.mcp_stataclaude mcp remove mcp_stata, or turn off stataMcp.configureClaudeCode to auto-remove[mcp_servers.mcp_stata] and [mcp_servers.mcp_stata.env] from ~/.codex/config.tomlThis extension uses Sentry to collect error and performance data to improve reliability. No personal data is collected. You can disable telemetry by setting "stata-workbench.telemetry.enabled": false in your VS Code settings.
Portions of this file are derived from stata-mcp (MIT License), language-stata by Kyle Barron (MIT License), and vscode-stata by Kyle Butts (MIT License). See license_extras for the full license texts. Do check their projects out!
MCP server integration for DaVinci Resolve Studio
mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, and diagnos
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots