SAS Viya

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:

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

Añadir a Cursor (se abre en una pestaña nueva)

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

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

Install in VS Code (se abre en una pestaña nueva)

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:

{
  "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):

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

[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.

Insignia para README

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

<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>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

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

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

iframe

<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>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, comando de instalación, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

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

Qué significa cada campo