SAS Viya

Name: SAS Viya
Author: sassoftware

作者：sassoftware版本 1.19.1i★ –i在你的电脑上运行

注册名称io.github.sassoftware/sas-mcp-server

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：VIYA_ENDPOINT

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： VIYA_ENDPOINT, SSL_VERIFY, CLIENT_ID, COMPUTE_CONTEXT_NAME, MCP_TIERS, MCP_READ_ONLY, MCP_APPS, MCP_STATELESS_HTTP, VIYA_CLIENT_TIMEOUT

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

VIYA_ENDPOINT 必填 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 sassoftware 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32545 个服务器的 0%
发布到注册中心的时间比此分类中其他 32545 个服务器的 82% 更新
基础检查结果等于或优于此分类中其他 32545 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

SAS Viya 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：VIYA_ENDPOINT

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.19.1）于7天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Python MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

Python MCP

作者：Files-com

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

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读