Skip to main content
Glama
horizonial

stata-mcp

by horizonial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to stata-mcp

No user-submitted related servers found.

    Related Servers

    • Stata MCP Server

      tmonk
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents to a local Stata installation, enabling execution of Stata code, data inspection, graph generation, and result verification through natural language interactions.
      597 PyPI
      90
      AGPL 3.0

    • MCP-for-Stata

      54cwh
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to invoke a local Stata installation, including a Windows Stata build under Wine on Linux and macOS, for regression analysis, econometrics, paper replication, and empirical research with command guards, resource monitoring, and automatic log capture.
      4
      2
      AGPL 3.0

    • Stata Executor MCP

      JinYuKiKK0
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables an agent to execute Stata do scripts or inline commands locally and retrieve structured results including status, error diagnostics, and output text for consumption by the model.
      1
      -

    • Stata MCP Server

      hanlulong
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a bridge between Stata statistical software and code editors like VS Code and Cursor, enabling users to run Stata commands directly from the editor, view output in real-time, and get AI-powered assistance with Stata coding.
      519
      MIT

    • STATA-MCP Repro

      taewat07
      A
      license
      C
      quality
      D
      maintenance
      Provides project-local, reproducible Stata execution for humans and AI agents, with immutable run artifacts, provenance tracking, planning gates, and a shared dashboard.
      22
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool maps to a distinct activity—executing code, loading data, inspecting data, viewing rows, retrieving results, exporting graphs, getting help, and managing sessions/tasks. There is minor potential confusion between inspect_data and get_results since both can return summary-like structured output, but the descriptions clarify the intended use.

    Naming Consistency3/5

    The consistent stata_ prefix and snake_case help, but the pattern is mixed: most tools use verb_noun (stata_load_data, stata_inspect_data, stata_export_graph), while others are noun phrases (stata_data_rows, stata_session_history, stata_task_status). This makes the set slightly less predictable.

    Tool Count5/5

    Ten tools is well-scoped for a Stata MCP server, covering command execution, data access, session management, help, and output export without redundancy or bloat. Each tool earns its place in the analysis workflow.

    Completeness4/5

    The tool surface covers the core Stata workflow—load data, inspect it, run commands, retrieve results, export graphs, get help, and manage tasks/sessions. A few optional additions like saving/exporting datasets or managing working directories are absent, but agents can work around these with stata_run, so there are no major dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources