SAS Viya

Name: SAS Viya
Author: sassoftware

by sassoftwareversion 1.19.1i★ –iRuns on your computer

Registry nameio.github.sassoftware/sas-mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: VIYA_ENDPOINT

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: VIYA_ENDPOINT, SSL_VERIFY, CLIENT_ID, COMPUTE_CONTEXT_NAME, MCP_TIERS, MCP_READ_ONLY, MCP_APPS, MCP_STATELESS_HTTP, VIYA_CLIENT_TIMEOUT

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sas": {
      "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.19.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value",
        "SSL_VERIFY": "your-value",
        "CLIENT_ID": "your-value",
        "COMPUTE_CONTEXT_NAME": "your-value",
        "MCP_TIERS": "your-value",
        "MCP_READ_ONLY": "your-value",
        "MCP_APPS": "your-value",
        "MCP_STATELESS_HTTP": "your-value",
        "VIYA_CLIENT_TIMEOUT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sas --env VIYA_ENDPOINT=your-value --env SSL_VERIFY=your-value --env CLIENT_ID=your-value --env COMPUTE_CONTEXT_NAME=your-value --env MCP_TIERS=your-value --env MCP_READ_ONLY=your-value --env MCP_APPS=your-value --env MCP_STATELESS_HTTP=your-value --env VIYA_CLIENT_TIMEOUT=your-value -- 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.19.1 app-stdio

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sas": {
      "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.19.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value",
        "SSL_VERIFY": "your-value",
        "CLIENT_ID": "your-value",
        "COMPUTE_CONTEXT_NAME": "your-value",
        "MCP_TIERS": "your-value",
        "MCP_READ_ONLY": "your-value",
        "MCP_APPS": "your-value",
        "MCP_STATELESS_HTTP": "your-value",
        "VIYA_CLIENT_TIMEOUT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sas": {
      "type": "stdio",
      "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.19.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value",
        "SSL_VERIFY": "your-value",
        "CLIENT_ID": "your-value",
        "COMPUTE_CONTEXT_NAME": "your-value",
        "MCP_TIERS": "your-value",
        "MCP_READ_ONLY": "your-value",
        "MCP_APPS": "your-value",
        "MCP_STATELESS_HTTP": "your-value",
        "VIYA_CLIENT_TIMEOUT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

VIYA_ENDPOINT required env
Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.
SSL_VERIFY env
Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate.
CLIENT_ID env
SASLogon OAuth client id used for the token refresh exchange.
COMPUTE_CONTEXT_NAME env
Compute context that backs SAS code execution.
MCP_TIERS env
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 Workbe…
MCP_READ_ONLY env
Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS.
MCP_APPS env
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 env
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 env
Timeout in seconds for every SAS Viya REST call the tools make.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sassoftware, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32545 servers in this category
Published to the registry more recently than 82% of the other 32545 servers in this category
Basic checks equal to or better than 100% of the other 32545 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SAS Viya safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: VIYA_ENDPOINT

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.19.1) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Python MCP

by Files-com

Local-only Python MCP server for the Files.com API.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

SAS Viya MCP Server

A Model Context Protocol (MCP) server for executing SAS code, training AutoML projects, scoring models and so much more for SAS Viya environments.

Features

115 tools across 11 selectable tiers, spanning the Analytics Life Cycle on SAS Viya
Interactive views (MCP Apps) for data, SAS logs and glossary editing in clients that render them — Claude, ChatGPT, Microsoft 365 Copilot, VS Code, Cursor
Prompt Templates for improving your SAS Code
OAuth2 authentication with PKCE flow
HTTP-based MCP server compatible with MCP clients

Articles & Videos

Here you can find getting articles on how to use and integrate the SAS MCP Server in different tools and what to build with it:

Getting Started

Prerequisites

Required
Python 3.12+
uv 0.8+
SAS Viya environment with compute service
Which tools work on which Viya release (LTS 2024.09 to Stable 2026.10): see COMPATIBILITY.md
Setup the Viya environment for MCP
See configuration.md

Optional
Docker: refer to container setup
Kubernetes: sample manifests (Contour or nginx) and a Helm chart in deploy/

Installation

Clone the repository:

git clone <repository-url>

cd sas-mcp-server

Install dependencies

uv sync

NOTE: This will by default create a virtual environment called .venv in the project's root directory.

If for some reason the virtual environment is not created, please run uv venv and then re-run uv sync.

Run uv sync again after each git pull, with every MCP client that uses this checkout closed. The stdio client configurations below start the server with uv run --no-sync, so they never sync .venv themselves: on Windows, a sync while another copy of the server is running fails on its locked .exe and the server does not start (see TROUBLESHOOTING.md).

Usage

Configure environment variables:

cp .env.sample .env

Edit .env and set

VIYA_ENDPOINT=https://your-viya-server.com

Start the MCP server (see Choosing a deployment mode below):

Option A: HTTP mode (pre-run the server, connect from MCP client)

uv run app

The server will be available at http://localhost:8134/mcp by default. Authentication is handled via OAuth2 PKCE flow in the browser.

Option B: Stdio mode (MCP client starts the server on demand)

Authenticate once. Two equivalent options:

# Option B1 — if you have the SAS Viya CLI installed:

sas-viya auth loginCode

Option B2 — built-in helper, no external CLI needed (Viya 2022.11+):

uv run sas-mcp-login

Both flows write an access token to a local cache (~/.sas/credentials.json and ~/.sas-mcp-server/credentials.json respectively); the stdio server reads whichever it finds. When the token expires, re-run the same command.

Then configure your MCP client to launch the server directly (see below).

Option C: Docker / Podman (containerized deployment)

Pull the pre-built image from GitHub Container Registry:

docker pull ghcr.io/sassoftware/sas-mcp-server:latest

docker run -e VIYA_ENDPOINT=https://your-viya-server.com -p 8134:8134 ghcr.io/sassoftware/sas-mcp-server:latest

Or build locally from source:

docker build -t sas-mcp-server .

docker run -e VIYA_ENDPOINT=https://your-viya-server.com -p 8134:8134 sas-mcp-server

Available image tags:

latest — most recent tagged release
. . (e.g. 1.0.0) — specific release
. (e.g. 1.0) — latest patch of a minor release
edge — tip of main (unreleased, for testing)
sha- — pinned to a specific commit

Programmatic clients with a pre-existing Viya token

If your caller already holds a Viya access token (e.g. an automation script that obtained one via the SAS Viya CLI), start the HTTP-mode server with ALLOW_RAW_BEARER=true and pass the token directly:

curl -H "Authorization: Bearer $VIYA_TOKEN" http://localhost:8134/mcp ...

The server validates the token against Viya's JWKS and uses it upstream as-is, bypassing the MCP JWT swap. The default OAuth2 PKCE flow keeps working alongside — both client types share the same /mcp endpoint.

If your Viya APIs are intentionally exposed without auth (for example, a local/dev Compute API endpoint), set VIYA_AUTH=false to bypass all SASLogon/OAuth flows in both HTTP and stdio modes. In this mode the server sends upstream requests without an Authorization header.

If your compute deployment does not expose /compute/contexts and only supports a fixed session, set COMPUTE_SESSION_ID= . The compute tools will use that session directly instead of creating context-backed sessions.

Choosing a deployment mode

	HTTP	Stdio	Docker	Kubernetes
How it runs	Long-running server you start separately	MCP client spawns it on demand	Containerized HTTP server	Containerized, behind an ingress
Authentication	OAuth2 PKCE flow (browser popup)	Cached token via `sas-viya` CLI or `sas-mcp-login`	OAuth2 PKCE flow (browser popup)	PKCE and/or raw Viya bearer token
Best for	Multi-user or shared setups; production-like environments	Single-user local development; quick experimentation	Team deployments; CI/CD; environments without Python installed	Shared/organisational deployments alongside Viya
Requires	Python + uv	Python + uv (+ optional `sas-viya` CLI)	Docker or Podman only	A cluster, an ingress controller, a TLS secret
Credentials stored?	No — user authenticates interactively	No — only an access token (not a password) is cached	No — user authenticates interactively	No — a signing key in a `Secret`; users authenticate themselves
MCP client config	Point client to `http://localhost:8134/mcp`	Client runs `uv run app-stdio`	Point client to `http://host:8134/mcp`	Point client to `https:// /mcp`

Quick guidance:

Starting out or exploring? Use stdio — one sas-viya auth loginCode or uv run sas-mcp-login, then your MCP client manages the server lifecycle.
Need secure, interactive auth? Use HTTP — no stored passwords, each user authenticates via browser.
Deploying for a team or on a server? Use Docker — portable, no Python dependency on the host, easy to integrate with orchestrators.
Running it for a whole organisation? Use Kubernetes — sample manifests and a Helm chart are in deploy/, including the routing the OAuth flow needs for either Contour (the chart's default, and the only one that can mount the server under a path prefix on an existing hostname) or ingress-nginx.
Using Gemini CLI? Use stdio — Gemini CLI does not support HTTP mode or browser-based OAuth. See Gemini CLI configuration.
Integrating with Microsoft 365 Copilot? Use Kubernetes (or any remote HTTPS deployment) — Copilot declarative agents only reach remotely hosted MCP servers. A ready-to-sideload agent package and walkthrough are in examples/m365-copilot/.
Adding it to a Microsoft Copilot Studio agent? Same remote HTTPS deployment, plus MCP_TOOL_RENAME=catalog_=infocat_ — Copilot Studio's agent runtime fails on tool names that start with catalog_. The steps are in examples/copilot-studio/.
Not sure which Microsoft route fits? examples/microsoft-copilot.md compares the declarative agent and the Copilot Studio agent, and shows the settings for one deployment that serves both.
Installing from a client's server catalogue? That path runs the published container in stdio mode (app-stdio), not as an HTTP server, so it authenticates from your ~/.sas token cache — which has to be mounted into the container at /app/.sas.

Limiting exposed tools (tiers)

Tools are grouped into numbered tiers. By default the server exposes all of them; set MCP_TIERS to expose only a subset — handy for keeping a client's tool list small and focused, or hiding capabilities a deployment shouldn't offer. Accepts ranges and comma lists (e.g. MCP_TIERS=0-4 or MCP_TIERS=0,1,6,7); unset means all tiers.

Tier	Group
0	Compute Contexts & Code Execution
1	Data Discovery
2	Data Operations & Files
3	Reports & Visualization
4	Batch Jobs & Async Execution
5	Automated Machine Learning
6	Model Management & Scoring
7	Decisioning Foundation (SAS Intelligent Decisioning)
8	Workbench (Execute Code Only)
9	Business Glossary (SAS Data Governance)
10	Decisioning Advanced (SAS Intelligent Decisioning) — needs Tier 7

# Example: expose only compute/discovery/data-ops and reporting

MCP_TIERS=0-3 uv run app

Read-only mode

Set MCP_READ_ONLY=true to expose only tools that neither change server-side state nor cause server-side work — 57 of the 115 tools. Withheld tools are never registered, so they are absent from the client's tool list entirely: the model cannot see them, so it cannot attempt them.

This is a filter over the tiers, not a tier of its own — the read/write split cuts across every tier (Tier 3 has both get_report and delete_report). The two settings compose:

# Every read tool, all tiers

MCP_READ_ONLY=true uv run app

Read tools of the reporting and decisioning tiers only

MCP_TIERS=3,7 MCP_READ_ONLY=true uv run app

The definition is strict: a tool qualifies only if it can neither write nor start work. Beyond the obvious create/update/delete tools, that withholds:

Withheld	Why
`execute_sas_code`, `submit_batch_job`	Run arbitrary code — can perform any operation, including deletes
`score_data`, `catalog_run_agent`, `catalog_run_adhoc_analysis`	Start server-side jobs and leave run records, though they return data
`promote_table_to_memory`	Mutates CAS in-memory state

| cancel_job, reset_compute_session | Destroy som

Only the beginning is shown; read the rest in the repo

SAS Viya

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Python MCP

README from the maker

SAS Viya MCP Server

Features

Articles & Videos

Getting Started

Prerequisites

Installation

Usage

Option B2 — built-in helper, no external CLI needed (Viya 2022.11+):

Choosing a deployment mode

Limiting exposed tools (tiers)

Read-only mode

Read tools of the reporting and decisioning tiers only