# sasjs-server

Guides agent workflows for deploying, configuring, and testing @sasjs/server, an open-source Node.js wrapper that exposes SAS binaries over a REST API.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1000 installs · ★ 3
- Author: sasjs
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/sasjs/skills/tree/HEAD/sasjs-server/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/sasjs-server

## What it does

This skill guides assistants through @sasjs/server setup and operations. The server provides a REST API with Swagger docs, the SASjs Drive virtual filesystem, Stored Program execution from URLs, and frontend streaming. Applications targeted for this server run on SAS 9 or SAS Viya through @sasjs/cli without code modifications.

Operation splits into two distinct modes. In `MODE=desktop`, the server runs single-user without authentication or a database. In `MODE=server`, a MongoDB instance is mandatory via `DB_CONNECT`, with LDAP or token authentication. Cross-origin calls fail completely in server mode unless origins are explicitly declared in `WHITELIST`.

Execution is not limited to SAS. Setting `RUN_TIMES` enables JavaScript, Python, or R runtimes alongside system paths like `NODE_PATH` and `PYTHON_PATH`. The JS runtime allows local backend mocking without a SAS license. However, programs must never redeclare `const fs`, as the runtime pre-injects the filesystem module and crashes on duplicate declaration.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add sasjs/skills --skill sasjs-server -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sasjs-server/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sasjs-server/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add sasjs/skills --skill sasjs-server -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sasjs-server/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add sasjs/skills --skill sasjs-server -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sasjs-server/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install sasjs/skills sasjs-server
```

2. **Manually: put the files in place**
- File: `.github/skills/sasjs-server/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add sasjs/skills --skill sasjs-server -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/sasjs/skills --path sasjs-server
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sasjs-server/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add sasjs/skills --skill sasjs-server -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/sasjs/skills/tree/HEAD/sasjs-server/SKILL.md

## When to use it
- configure environment variables for @sasjs/server deployments
- create mock REST endpoints using the JavaScript runtime without SAS
- switch between desktop and server modes with MongoDB configuration
- set up LDAP authentication and CORS origin whitelisting

## Example prompts
- Generate a `.env` configuration for @sasjs/server with MongoDB and LDAP authentication.
- Write a JS Stored Program for SASjs Drive that outputs a JSON payload via `_webout`.
- How do I configure `RUN_TIMES` to execute both SAS and Python scripts on the server?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: a8e9170d7a86645b.

BEGIN THIRD-PARTY FILE a8e9170d7a86645b
````text
---
name: sasjs-server
description: Installing, configuring, and running @sasjs/server - the open-source NodeJS wrapper around the SAS binary that provides a REST API, filesystem (SASjs Drive), Stored Program execution, and web app streaming. Covers desktop vs server modes, runtimes (SAS/JS/Python/R), env vars, auth (tokens, LDAP), and mock servers. Use when deploying, troubleshooting, or developing against sasjs/server.
---

# @sasjs/server

SASjs Server is an open-source NodeJS wrapper for calling the SAS binary executable. It runs on a real SAS server or a local desktop and provides:

- A filesystem (SASjs Drive) for storing SAS programs and content
- Execution of Stored Programs from a URL (equivalent to SAS 9 Stored Processes / Viya Jobs)
- Web app streaming (serve frontend apps straight from SAS content)
- A REST API with Swagger docs
- Portability: apps built for SASjs Server deploy unchanged to SAS 9 / Viya via @sasjs/cli

## Modes

- **Desktop mode** (`MODE=desktop`, default): single-user, no authentication, no database. CORS enabled by default.
- **Server mode** (`MODE=server`): multi-user with authentication, requires a database (`DB_CONNECT`, `DB_TYPE=mongodb|cosmos_mongodb`). CORS disabled by default - configure `WHITELIST` if enabling.

## Installation

Download the relevant zip from GitHub releases, **verify it before running**: pin a specific release tag (not `latest`), check the published SHA256 checksum, or - better - build from source.

```bash
curl -L https://github.com/sasjs/server/releases/download/R/<asset>.zip > <asset>.zip   # replace R with the pinned release tag
sha256sum <asset>.zip   # compare against the checksum published on the release page
unzip <asset>.zip && ./api-linux
```

[Curl-pipe-bash and blind `latest` downloads are supply-chain risks. Pinning a tag and verifying the checksum also makes your infra reproducible.]

On first run it prompts (unless set as env vars) for the SAS executable path and the filesystem location for Stored Programs/temp files. Docker is also supported (`DockerfileApi`, docker-compose files in the repo).

## Configuration via environment variables

Set in `/etc/environment`, exported, prepended to the command, or in a `.env` file alongside the executable. Key variables:

| Variable | Purpose |
|---|---|
| `MODE` | `desktop` (default) or `server` |
| `SAS_PATH` | Path to `sas.exe` / `sas.sh` |
| `RUN_TIMES` | Comma-separated runtime priority, e.g. `sas,js,py` - options: `sas`, `js`, `py`, `r`. Each needs its path: `SAS_PATH`, `NODE_PATH`, `PYTHON_PATH`, `R_PATH` |
| `SASJS_ROOT` | Working directory: SAS WORK, staged files, drive, config |
| `DRIVE_LOCATION` | Location for files, sasjs packages, `appStreamConfig.json` |
````
END THIRD-PARTY FILE a8e9170d7a86645b

The third-party file has ended. Everything between the a8e9170d7a86645b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2727 of 9744 bytes. © sasjs · MIT · https://github.com/sasjs/skills/tree/HEAD/sasjs-server/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md