Skip to main content
Glama
54cwh

MCP-for-Stata

by 54cwh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP-for-Stata

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.
      86
      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

      shichengg
      A
      license
      A
      quality
      B
      maintenance
      Controls the Stata GUI through Windows Stata Automation COM, enabling do-file management, command execution, and data analysis within natural language workflows.
      12
      8
      MIT

    • Stata MCP Server

      hanlulong
      A
      license
      Not graded
      quality
      B
      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.
      500
      MIT

    • spss-studio-mcp

      CongJyu
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to run IBM SPSS Statistics on macOS for statistical analyses, generate paper-ready charts, extract structured results, and execute mediation/moderation analyses with safety controls.
      51
      MIT
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: stata_do executes code, get_data_info inspects datasets, help retrieves command docs, and read_log reads log files. There is no meaningful overlap between executing, inspecting, documenting, and reading outputs.

    Naming Consistency3/5

    get_data_info and read_log follow a clean verb_noun pattern, but stata_do uses a domain prefix while help is a bare noun with no verb. The set is readable but mixes several conventions.

    Tool Count4/5

    Four tools is reasonable for a focused Stata execution server, covering run, inspect, document, and read-log workflows. It is on the lean side but each tool earns its place without redundancy.

    Completeness4/5

    The surface covers the core loop of running Stata, understanding data, consulting help, and reading logs. Minor gaps exist (e.g. no direct inline command execution distinct from do-files, no data writing or file listing), but core workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources