Skip to main content
Glama
matise-joe-norc

sas-mcp

by matise-joe-norc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sas-mcp

No user-submitted related servers found.

    Related Servers

    • OpsContext

      FASTPROD
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to access live operational context like processes, containers, and git state, while providing a tamper-evident audit log and policy-as-code compliance hooks locally.
      22
      1,235 npm
      Business Source 1.1

    • Guardrail MCP Validator

      krunkmetalist
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to syntax-check generated configuration and code — such as JSON, Docker Compose, Python, and Bash — against native local engines via a validate_and_format_code tool, returning structured errors that trigger self-correction loops until the output actually compiles.
      MIT

    • Agent Decision Kit

      krmdl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to make structured local decisions, choose bounded browser actions with approvals, and run coding workflows such as file relevance, context pruning, diff screening, and completion checks through MCP or CLI.
      Apache 2.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

    A4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target a distinct resource and action: config selection, code execution, dataset metadata, file transfer, and comparison. A few overlapping boundaries exist—session_status overlaps with list_libraries/list_datasets for a quick overview, and run_sas vs. run_sas_tests both submit code—but the descriptions make the intended use clear.

    Naming Consistency4/5

    The majority follow a clear verb_noun pattern such as list_datasets, describe_dataset, compare_datasets, and download_from_sas. The exceptions are session_status and sas_doctor, which are noun-led and break the otherwise predictable scheme.

    Tool Count4/5

    Sixteen tools is slightly above the typical 3–15 sweet spot, but each tool maps to a distinct part of the SAS workflow: connection management, session state, code execution, file transfer, metadata inspection, and validation. The count feels justified rather than bloated.

    Completeness4/5

    The surface covers the core SAS lifecycle well: configure/connect, inspect session and datasets, run code, retrieve logs, transfer files, compare tables, and run tests. Minor gaps exist—no explicit disconnect tool or direct file deletion—but these do not create dead ends since run_sas and session management cover most of them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources