SAS Viya

Name: SAS Viya
Author: sassoftware

by sassoftwareversion 1.20.1i★ 68iRuns on your computer

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

How to install

What it does

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

Connects Runs on your computer
Account or key No key needed · 1 setting to fill in (VIYA_ENDPOINT)
Category Developer tools

Install

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

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Install Docker
One time only; it works for every server that needs Docker
Open the Docker download page ↗
Done
2
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
- VIYA_ENDPOINT Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.
Descriptions are as written by the maker.
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "sas": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VIYA_ENDPOINT",
        "ghcr.io/sassoftware/sas-mcp-server:1.20.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value"
      }
    }
  }
}

Done

Quit Claude and open it again
Done
Try it
Use SAS Viya and tell me what you can do for me, then show me one thing
✓ If Claude says it is using SAS Viya or shows a SAS Viya tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

SSL_VERIFY Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate. · default true
CLIENT_ID SASLogon OAuth client id used for the token refresh exchange. · default sas-mcp
COMPUTE_CONTEXT_NAME Compute context that backs SAS code execution. · default SAS Job Execution compute context
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 Workbe…
MCP_READ_ONLY Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS. · default false
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. · default true
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. · default false
VIYA_CLIENT_TIMEOUT Timeout in seconds for every SAS Viya REST call the tools make. · default 300

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect SAS Viya yet

SAS Viya runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect SAS Viya

Steps for Claude →1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)
Steps for Cursor →1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)
Steps for VS Code →1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)

Install Docker
One time only; it works for every server that needs Docker
Open the Docker download page ↗
Done
2
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
- VIYA_ENDPOINT Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.
Descriptions are as written by the maker.
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --scope user sas --env VIYA_ENDPOINT=your-value -- docker run -i --rm -e VIYA_ENDPOINT ghcr.io/sassoftware/sas-mcp-server:1.20.1 app-stdio

Done

Type /mcp in Claude Code
You should see SAS Viya listed as connected
Done
Try it
Use SAS Viya and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using SAS Viya or shows a SAS Viya tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

SSL_VERIFY Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate. · default true
CLIENT_ID SASLogon OAuth client id used for the token refresh exchange. · default sas-mcp
COMPUTE_CONTEXT_NAME Compute context that backs SAS code execution. · default SAS Job Execution compute context
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 Workbe…
MCP_READ_ONLY Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS. · default false
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. · default true
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. · default false
VIYA_CLIENT_TIMEOUT Timeout in seconds for every SAS Viya REST call the tools make. · default 300

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)

Install Docker
One time only; it works for every server that needs Docker
Open the Docker download page ↗
Done
2
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
- VIYA_ENDPOINT Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.
Descriptions are as written by the maker.
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Fill in your key
In the SAS Viya settings, VIYA_ENDPOINT is empty; add your key and save
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use SAS Viya and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using SAS Viya or shows a SAS Viya tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

SSL_VERIFY Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate. · default true
CLIENT_ID SASLogon OAuth client id used for the token refresh exchange. · default sas-mcp
COMPUTE_CONTEXT_NAME Compute context that backs SAS code execution. · default SAS Job Execution compute context
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 Workbe…
MCP_READ_ONLY Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS. · default false
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. · default true
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. · default false
VIYA_CLIENT_TIMEOUT Timeout in seconds for every SAS Viya REST call the tools make. · default 300

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

1 setting(s) to fill in (VIYA_ENDPOINT) · Install Docker on your computer first (one time)

Install Docker
One time only; it works for every server that needs Docker
Open the Docker download page ↗
Done
2
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
- VIYA_ENDPOINT Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.
Descriptions are as written by the maker.
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Fill in your key
In the SAS Viya settings, VIYA_ENDPOINT is empty; add your key and save
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use SAS Viya and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using SAS Viya or shows a SAS Viya tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

SSL_VERIFY Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate. · default true
CLIENT_ID SASLogon OAuth client id used for the token refresh exchange. · default sas-mcp
COMPUTE_CONTEXT_NAME Compute context that backs SAS code execution. · default SAS Job Execution compute context
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 Workbe…
MCP_READ_ONLY Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS. · default false
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. · default true
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. · default false
VIYA_CLIENT_TIMEOUT Timeout in seconds for every SAS Viya REST call the tools make. · default 300

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use SAS Viya💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user sas --env VIYA_ENDPOINT=your-value -- docker run -i --rm -e VIYA_ENDPOINT ghcr.io/sassoftware/sas-mcp-server:1.20.1 app-stdio

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "sas": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VIYA_ENDPOINT",
        "ghcr.io/sassoftware/sas-mcp-server:1.20.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sas": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VIYA_ENDPOINT",
        "ghcr.io/sassoftware/sas-mcp-server:1.20.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sas": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VIYA_ENDPOINT",
        "ghcr.io/sassoftware/sas-mcp-server:1.20.1",
        "app-stdio"
      ],
      "env": {
        "VIYA_ENDPOINT": "your-value"
      }
    }
  }
}

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.

Descriptions are as written by the maker.

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

At a glance

GitHub stars i: 68
Downloads per weeki: Not on npm/PyPI
Licence i: Apache-2.0
Connection: Runs on your computer
Transport: stdio
Latest versioni: 1.20.1
Categoryi: Developer tools
Published to registryi: Nov 13, 2026
Code last changedi: Nov 13, 2026
Maker: sassoftware
Packages: oci: ghcr.io/sassoftware/sas-mcp-server:1.20.1
Repo: sassoftware/sas-mcp-server
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

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 14, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sassoftware, which owns the repo
✓ Pass
Still maintained
Code last changed yesterday
✓ Pass
Has a licence
Uses Apache-2.0
– 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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 96% of the other 5882 servers in this category
Published to the registry more recently than 97% of the other 5882 servers in this category
Basic checks equal to or better than 100% of the other 5882 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 3 of 3 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 yesterday, and the latest version (1.20.1) reached the registry yesterday.

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: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

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

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

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 457.7KUpdated 2 days ago

Runs on your computer

Install

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 11 days ago

Computer or cloud

Install

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.4KUpdated 6 months ago

Runs on your computer

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

What it does

Install

Install Docker

Fill in 1 setting(s)

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Docker

Fill in 1 setting(s)

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Docker

Fill in 1 setting(s)

Click this button to open Cursor

Fill in your key

Open the AI chat in Cursor in Agent mode

Try it

Install Docker

Fill in 1 setting(s)

Click this button to open VS Code

Fill in your key

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

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

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Others in the same category

REA

GitHub

Serena MCP: the IDE for your agent

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