SAS Viya MCP Server

SAS Viya is an MCP integration. Execute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0.

Packages and local setup

The published oci package is ghcr.io/sassoftware/sas-mcp-server:1.18.0. Its declared MCP transport is stdio.

The package declares VIYA_ENDPOINT (required): Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.; SSL_VERIFY: Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate.; CLIENT_ID: SASLogon OAuth client id used for the token refresh exchange.; COMPUTE_CONTEXT_NAME: Compute context that backs SAS code execution.; MCP_TIERS: Expose only some tool tiers, e.g. 0-4 or 0,1,7. Empty exposes all 92 tools. Tiers: 0 Compute, 1 Data Discovery, 2 Data Operations, 3 Reports, 4 Batch Jobs, 5 AutoML, 6 Models, 7 Decisioning, 8 Workbench, 9 Business Glossary.; MCP_READ_ONLY: Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS.; MCP_APPS: Register interactive views (MCP Apps) for the data, SAS log and glossary tools. Additive: text-only clients are unaffected. Set false to register none.; MCP_STATELESS_HTTP: Serve HTTP requests without an MCP session. Needed by clients that speak only the sessionless 2026-07-28 protocol revision (claude.ai custom connectors); the legacy handshake works either way.; VIYA_CLIENT_TIMEOUT: Timeout in seconds for every SAS Viya REST call the tools make..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.18.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.