Developer · Local MCP server
SAS Viya
Execute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sassoftware/sas-mcp-server- Version
- 1.18.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- sassoftware (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sassoftware) · how
- Repository
- github.com/sassoftware/sas-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | ghcr.io/sassoftware/sas-mcp-server:1.18.0 | - | stdio |
How to connect SAS Viya
SAS Viya runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/sassoftware/sas-mcp-server:1.18.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e VIYA_ENDPOINT -e SSL_VERIFY -e CLIENT_ID -e COMPUTE_CONTEXT_NAME -e MCP_TIERS -e MCP_READ_ONLY -e MCP_APPS -e MCP_STATELESS_HTTP -e VIYA_CLIENT_TIMEOUT ghcr.io/sassoftware/sas-mcp-server:1.18.0. It reads these environment variables: VIYA_ENDPOINT (required), SSL_VERIFY, CLIENT_ID, COMPUTE_CONTEXT_NAME, MCP_TIERS, MCP_READ_ONLY, MCP_APPS, MCP_STATELESS_HTTP and VIYA_CLIENT_TIMEOUT; set them in the client's configuration for this server. Required arguments: -v.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"sas-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VIYA_ENDPOINT",
"-e",
"SSL_VERIFY",
"-e",
"CLIENT_ID",
"-e",
"COMPUTE_CONTEXT_NAME",
"-e",
"MCP_TIERS",
"-e",
"MCP_READ_ONLY",
"-e",
"MCP_APPS",
"-e",
"MCP_STATELESS_HTTP",
"-e",
"VIYA_CLIENT_TIMEOUT",
"ghcr.io/sassoftware/sas-mcp-server:1.18.0"
],
"env": {
"VIYA_ENDPOINT": "<value>",
"SSL_VERIFY": "<value>",
"CLIENT_ID": "<value>",
"COMPUTE_CONTEXT_NAME": "<value>",
"MCP_TIERS": "<value>",
"MCP_READ_ONLY": "<value>",
"MCP_APPS": "<value>",
"MCP_STATELESS_HTTP": "<value>",
"VIYA_CLIENT_TIMEOUT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SAP ABAP MCPDevelop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents. | Local · stdio |
| Sap Abap SqlChecks and fixes ABAP Open SQL for SAP's ADT data-preview console. Connects to nothing. | Local · stdio |
| Sap Adt MCPGive Claude live access to SAP ABAP via ADT: read, search, check, test, and edit objects. | Local · stdio |
| sapiom MCPLocal Sapiom developer MCP for authoring, testing, deploying, and inspecting agents. | Local · stdio |
| SaSame MCP Observatory + Gold Rush TownNo-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM. | Remote · HTTPLive check: ✓ handshake |
| SavantoAI MCP-SERVERManage your Savanto store from your AI: catalog, content, prompts, and analytics, by chat. | Remote & Local · HTTP, stdioLive check: sign-in required |
| SBOMApp - SBOM Generator & Vulnerability ScannerGenerate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos. | Remote · HTTPLive check: ✗ no handshake |
| ScalingoManage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant. | Remote · HTTPLive check: ✓ handshake |