SAS Viya

Name: SAS Viya
Author: sassoftware

de sassoftwareversión 1.19.1i★ –iSe ejecuta en tu computadora

Nombre en el registroio.github.sassoftware/sas-mcp-server

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en tu computadora
Transporte: stdio
Categoría: Otros
Debes completar: VIYA_ENDPOINT

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
Debes completar tú: VIYA_ENDPOINT, SSL_VERIFY, CLIENT_ID, COMPUTE_CONTEXT_NAME, MCP_TIERS, MCP_READ_ONLY, MCP_APPS, MCP_STATELESS_HTTP, VIYA_CLIENT_TIMEOUT

Necesitas

DockerDocker instalado

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
      }
    }
  }
}

Ejecuta esto en tu 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

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

VIYA_ENDPOINT obligatorio 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.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub sassoftware, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
– No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
– No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 32520 servidores de esta categoría
Publicado en el registro más recientemente que el 83% de los otros 32520 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 32520 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro SAS Viya?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: VIYA_ENDPOINT

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.19.1) llegó al registro hace 7 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Toggl 2.0

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

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

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses

Instalar

Remote Desktop Commander

de desktop-commander

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

Se ejecuta en la nube★ 211Actualizado ayer

Instalar

Toggl 2.0

de toggl

Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.

Se ejecuta en tu computadoraActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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

Solo se muestra el principio; lee el resto en el repo

SAS Viya

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

Toggl 2.0

README del creador

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