Skip to main content
Glama

Related Servers

Alternatives to MCP-for-Stata

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI agents to a local Stata installation so they can run Stata commands and .do files, inspect datasets and codebooks, export graphs, look up help, and verify stored r()/e() results with structured error reporting.
      AGPL 3.0
    • 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM/agent applications to execute Stata code, load and inspect data, obtain structured regression results and graphs, and manage background tasks through the Model Context Protocol.
      10
      MIT
    • 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
    • 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
      7
      MIT

    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

    ActivityMaintained
    ResponsivenessNo issues