We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

SAS Viya

MCP server by SAS Software

Run SAS code and work with Compute, CAS, models, reports and decisioning on a SAS Viya environment.

Runs locally (Runs on your machine: its page has the install command)Runs with docker

Install SAS Viya

Runs on your machine. Your client starts it with this command:

docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0

Needs Docker on your computer. The setup steps below show where the command goes in each client.

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

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/sas-viya

About

Connects an assistant to a SAS Viya environment and exposes 92 tools across the analytics lifecycle. Tools are grouped in 10 tiers: Compute, Data Discovery, Data Operations, Reports, Batch Jobs, AutoML, Models, Decisioning, Workbench and Business Glossary. It also offers prompt templates for improving SAS code and interactive views for data, SAS logs and glossary editing in clients that render them.

It is self-hosted: run the container image ghcr.io/sassoftware/sas-mcp-server, or run it from source with Python 3.12+ and uv, in HTTP or stdio mode. It needs the VIYA_ENDPOINT of your SAS Viya environment with the compute service. Users sign in through SASLogon with OAuth 2.0 PKCE, or a cached token in stdio mode.

What you can do

  • Execute SAS code on a Viya Compute context
  • Discover and operate on data in Compute and CAS
  • Work with reports and batch jobs
  • Train AutoML projects and score models
  • Use decisioning and business glossary tools
  • Limit exposed tools by tier or read-only mode
  • View data and SAS logs in interactive views

Tools

SAS Viya lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • Run this SAS code on Viya and show me the log

  • List the CAS tables available in my Viya environment

  • Train an AutoML project on my customer churn data

  • Score this dataset with the model registered in Viya

Set up

Every client starts SAS Viya on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio sas-viya --env "VIYA_ENDPOINT=<YOUR_VIYA_ENDPOINT>" -- docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0
  1. Start Claude Code and type /mcp. sas-viya should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "sas-viya": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "VIYA_ENDPOINT",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<YOUR_VIYA_ENDPOINT>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Docker on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Docker on your computer. Replace the placeholders with your own values.

VS Code

Or from a terminal:

code --add-mcp '{"name":"sas-viya","type":"stdio","command":"docker","args":["run","-e","VIYA_ENDPOINT","-i","--rm","ghcr.io/sassoftware/sas-mcp-server:1.18.0"],"env":{"VIYA_ENDPOINT":"<YOUR_VIYA_ENDPOINT>"}}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "sas-viya": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-e",
        "VIYA_ENDPOINT",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<YOUR_VIYA_ENDPOINT>"
      }
    }
  }
}

Needs Docker on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "sas-viya": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "VIYA_ENDPOINT",
        "-i",
        "--rm",
        "ghcr.io/sassoftware/sas-mcp-server:1.18.0"
      ],
      "env": {
        "VIYA_ENDPOINT": "<YOUR_VIYA_ENDPOINT>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

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

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.sas-viya]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/sassoftware/sas-mcp-server:1.18.0"]
env = { VIYA_ENDPOINT = "<YOUR_VIYA_ENDPOINT>" }

Needs Docker on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "VIYA_ENDPOINT=<YOUR_VIYA_ENDPOINT>" sas-viya docker -- run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Docker on your computer. Replace the placeholders with your own values.

Embed

Show SAS Viya in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![SAS Viya on mcp.tc](https://mcp.tc/i/sas-viya/badge.svg)](https://mcp.tc/i/sas-viya)
HTML
<a href="https://mcp.tc/i/sas-viya"><img src="https://mcp.tc/i/sas-viya/badge.svg" alt="SAS Viya on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/sas-viya.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/sas-viya" title="SAS Viya on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/sas-viya.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SAS Viya card to your site.

Markdown
Add the mcp.tc card for SAS Viya, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/sas-viya.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="sas-viya"><a href="https://mcp.tc/i/sas-viya">SAS Viya on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![SAS Viya on mcp.tc](https://mcp.tc/i/sas-viya/badge.svg)](https://mcp.tc/i/sas-viya)
```

Reference: https://mcp.tc/embed

Change history

It runs on your computer and has no package we can follow. Edits by its owner show up here.

Follow SAS Viya and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/sas-viya into my MCP client?

No. SAS Viya runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0.

Does SAS Viya need an API key?

No. It reads VIYA_ENDPOINT from its environment; the setup steps show where to set it.

Is SAS Viya a remote or a local server?

Local. Your client starts it as a process on your computer with docker run -i --rm ghcr.io/sassoftware/sas-mcp-server:1.18.0, which needs Docker.

What can SAS Viya do?

You can execute SAS code on a Viya Compute context, discover and operate on data in Compute and CAS and work with reports and batch jobs.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to SAS Viya?

Partly. SAS Viya runs on your computer and has no package we can follow, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read SAS Viya’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with SAS Software. This page was built from SAS Viya’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.