Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
This skill performs an end-to-end smoke test of the local Stata-MCP server.
It checks installation, runs representative data and Stata commands, and reports
pass/fail status for each tool.
When to use
The user asks whether Stata-MCP is working.
The user wants to verify a new MCP server configuration.
The user says a tool is broken or unavailable.
The user asks for a smoke test, sanity check, or end-to-end test.
Before you start
Make sure the current working directory is the project root.
Confirm whether the project virtual environment exists at ./.venv/bin/stata-mcp.
If it does not exist, use the globally installed stata-mcp command instead.
Ensure ~/.statamcp/debug.toml exists and enables beta security.
Use .claude/skills/mcp-smoke-test/config/debug.example.toml as a template.
Step 1: Ensure the MCP server is registered
Check whether the MCP server stata-mcp-local-smoke-test is available by listing
Claude MCP servers:
claude mcp list
If stata-mcp-local-smoke-test is missing, add it with the debug configuration:
claude mcp add stata-mcp-local-smoke-test -s local -- $(pwd)/.venv/bin/stata-mcp -c ~/.statamcp/debug.toml
If ./.venv does not exist, use:
claude mcp add stata-mcp-local-smoke-test -s local -- stata-mcp -c ~/.statamcp/debug.toml
After adding, if the server is still not available, tell the user:
MCP server was added but is not yet visible. Please restart the Claude process
and then invoke the smoke test again.
Step 2: Run smoke tests
Run the preparation script. It clears cached summaries, locates or generates a
suitable auto.dta, and copies the boundary test files to /tmp: