SAS MCP Server
OfficialRelated Servers
Alternatives to SAS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExecutes Python code with safety constraints and manages Python packages through the Model Context Protocol.6 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables secure cloud-based execution of code across 14+ programming languages within a sandboxed environment. It supports file management, standard input/output handling, and automatic generation of visual artifacts like plots and charts.MIT
- AlicenseNot gradedqualityAmaintenanceEnables secure remote command execution and bidirectional file transfers on SSH servers through the Model Context Protocol. It features robust security controls including command whitelisting, credential isolation, and support for multiple SSH connection profiles.1,646 npm989ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI to execute RPA applications and workflows through the Model Context Protocol, supporting both local and cloud modes.5 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables governed, audit-traced AI access to a curated knowledge base through the Model Context Protocol, with OAuth 2.1 authentication and policy enforcement for secure, compliant queries.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables users to execute notebook cells, manage environments, and validate workbooks via MCP, facilitating reproducible machine-learning answers.MIT
TDQS
Scored across 115 tools
Many tools are clearly separated by domain and action, but the generic decisioning tools overlap substantially with the business-rules-specific tools (list/get/delete/lock/revision variants), and register_ml_champion_model vs publish_ml_champion_model is easy to confuse. The detailed descriptions help, but the set still presents multiple valid-looking paths for the same underlying operations.
Tool names consistently use snake_case verb_noun patterns such as list_*, get_*, create_*, update_*, delete_*, validate_*, and publish_*. Domain prefixes like catalog_ and names like catalog_search_helper are predictable variations rather than a break in convention.
At 115 tools, this is far beyond the 50+ threshold where tool selection becomes a serious burden. Even for a broad SAS Viya platform, this surface is large enough that it should be split into multiple scoped servers or tool groups.
Coverage is very broad: decisioning, business rules, MAS scoring, reports, jobs, AutoML/model repository, glossary/catalog, CAS/compute data, files, and uploads all have meaningful lifecycle operations. Minor gaps remain, such as file deletion, CAS table deletion, sparse model-repository operations beyond listing/register/publish, and some revision getters.