How do I install SAS Viya?

Install via Claude Code (local): 1. Install Claude Code CLI 2. Copy the command below, replace with real env values, then run in terminal 3. See Environment variables below if listed Example: claude mcp add sas-mcp-server --env VIYA_ENDPOINT= -- docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0

What is SAS Viya good for?

SAS Viya is a fit for: Code review & GitHub, Cursor essentials. See AgentHub scenario pages for pairings.

SAS Viya MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.sassoftware/sas-mcp-server · v1.18.0

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

Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Execute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0. SAS Viya is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHub Cursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04

Install Snippets TestedCLI & JSON config syntax verified

Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications

Origin Registry ActiveSourced from official-mcp-registry

Verified ClientsClaude Code、Claude Desktop、Cursor 等

Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Score 90/100

Copy by platform

Choose your platform

Open or create .cursor/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets (see Environment variables below)
Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

VIYA_ENDPOINT

Required

SSL_VERIFY

CLIENT_ID

COMPUTE_CONTEXT_NAME

MCP_TIERS

MCP_READ_ONLY

MCP_APPS

MCP_STATELESS_HTTP

VIYA_CLIENT_TIMEOUT

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.

Click to copy snippet

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Setup tutorial

Open the SAS Viya page and confirm this MCP Server (source: MCP Registry).
Copy the Cursor, Claude Code, or VS Code snippet.
Merge it into mcpServers and replace env placeholders with real secrets.
Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

Install Claude Code CLI
Copy the command below, replace <placeholders> with real env values, then run in terminal
See Environment variables below if listed

claude mcp add sas-mcp-server --env VIYA_ENDPOINT=<VIYA_ENDPOINT> -- docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0

Cursor — .cursor/mcp.json (local)

Open or create .cursor/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets (see Environment variables below)
Save, then Cmd+Shift+P → Reload Window

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

VS Code — .vscode/mcp.json (local)

Install GitHub Copilot in VS Code with MCP support
Open or create .vscode/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets
Save and Developer: Reload Window

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
Click Copy config and merge under mcpServers
Replace <placeholders> in env with real secrets
Fully quit and restart Claude Desktop

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Trae — .trae/mcp.json (local)

Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
Click Copy config and merge mcpServers
Replace <placeholders> in env with real secrets
Save and reload Trae

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Cherry Studio — MCP settings (local)

Cherry Studio → Settings → MCP Servers → Add (STDIO)
Or import JSON: click Copy config and merge mcpServers
Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
Enable the server and check tools load

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Tongyi Lingma — MCP config (local)

Lingma Settings → MCP → + → STDIO or config file
Click Copy config and merge mcpServers
Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
Confirm connected before using tools in agent chat

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Windsurf — mcp_config.json (local)

Edit ~/.codeium/windsurf/mcp_config.json
Click Copy config and merge mcpServers (stdio same as Cursor)
Replace <placeholders> in env, save, refresh Cascade

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Cline — MCP Servers (local)

Cline panel → Settings → MCP Servers
Click Copy config and merge
Replace <placeholders> in env, then save

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
Or Plugins → MCP Servers → Configure MCP and paste the JSON below
Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
Save, restart WorkBuddy, confirm connector status is green

{
  "mcpServers": {
    "sas-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<VIYA_ENDPOINT>"
      }
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for SAS Viya

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for SAS Viya?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet

# Check binary path in terminal:
which npx
node -v

Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

SAS Viya requires environment variables (VIYA_ENDPOINT). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet

// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "VIYA_ENDPOINT": "your_actual_key_here"
  }
}

Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

SAS Viya Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready

fn: sas_mcp_serverExecute the core tool interface of SAS Viya

Request ArgumentsJSON Schema

{
  "target": "SAS Viya",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}

💡Parameters generated dynamically by Agent runtime

Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For

PR review
Changelog generation
Cross-repo issue search

When NOT to Use

Replacing human security audit
Unauthorized repo access

Recommended Workflow Pairing:View Scenario →

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like this Search similar Pick by scenario Prompt playbooks MCP hands-on Reviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

Preview

HTML

<a href="https://myagenthub.cn/p/io.github.sassoftware/sas-mcp-server" title="Listed on AgentHub: SAS Viya" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.sassoftware/sas-mcp-server?lang=en" alt="Listed on AgentHub: SAS Viya" height="20" style="border:0"/>
</a>

Markdown (GitHub README)

[![Listed on AgentHub: SAS Viya](https://myagenthub.cn/badge/io.github.sassoftware/sas-mcp-server?lang=en)](https://myagenthub.cn/p/io.github.sassoftware/sas-mcp-server)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.sassoftware/sas-mcp-server",
  "type": "mcp-server",
  "version": "1.18.0",
  "displayName": "SAS Viya",
  "description": "Execute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0.",
  "repository": {
    "url": "https://github.com/sassoftware/sas-mcp-server",
    "source": "github"
  },
  "distribution": {
    "packages": [
      {
        "registryType": "oci",
        "identifier": "ghcr.io/sassoftware/sas-mcp-server:1.18.0",
        "runtimeHint": "docker",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "VIYA_ENDPOINT",
            "description": "Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.",
            "isRequired": true
          },
          {
            "name": "SSL_VERIFY",
            "description": "Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate."
          },
          {
            "name": "CLIENT_ID",
            "description": "SASLogon OAuth client id used for the token refresh exchange."
          },
          {
            "name": "COMPUTE_CONTEXT_NAME",
            "description": "Compute context that backs SAS code execution."
          },
          {
            "name": "MCP_TIERS",
            "description": "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 Workbench, 9 Business Glossary."
          },
          {
            "name": "MCP_READ_ONLY",
            "description": "Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS."
          },
          {
            "name": "MCP_APPS",
            "description": "Register interactive views (MCP Apps) for the data, SAS log and glossary tools. Additive: text-only clients are unaffected. Set false to register none."
          },
          {
            "name": "MCP_STATELESS_HTTP",
            "description": "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."
          },
          {
            "name": "VIYA_CLIENT_TIMEOUT",
            "description": "Timeout in seconds for every SAS Viya REST call the tools make."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.sassoftware/sas-mcp-server",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.sassoftware%2Fsas-mcp-server/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}