Rewst MCP

Rewst + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Rewst

API. Not affiliated with, endorsed by, or sponsored by Rewst, Inc..

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Operate and monitor Rewst RPA across every client org from the terminal or your AI agent: workflow execution health, failure triage, automation ROI, dormant-workflow cleanup, cross-org config drift, and integration-pack coverage - the multi-tenant answers the web console makes you assemble one org at a time. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs rewst-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion rewst-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set REWST_CLI_PATH to an existing binary). Details: #331.

Download Rewst MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Rewst release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install rewst@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Rewst Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.ps1 | iex. Then authenticate per the README and run rewst-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.sh)

The installer drops both rewst-cli (the CLI) and rewst-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

rewst-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update rewst@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/rewst --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/rewst --force

Hermes speaks MCP natively, so it can also use the rewst-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the rewst skill from https://github.com/servosity/msp-skills/tree/main/skills/rewst. The skill defines how its required CLI (rewst-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the API token the CLI needs (from an API client you create in the Rewst console):

REWST_API_TOKEN=<value> rewst-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error. The US endpoint (https://api.rewst.io) is the default; for EU/AU or another region, also set REWST_BASE_URL= .

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Rewst's only surface is a GraphQL gateway - no first-party CLI, no terminal access, no cross-tenant view. Most integrations just forward a query and hand back raw GraphQL nodes. That's fine for one record. It dies when you're asking "is automation healthy across all 40 of my clients" or "which workflows failed overnight, in which tenant".

This skill adds the cross-org rollups Rewst's gateway has no single endpoint for. orgs, health, failures, dormant, roi, drift and coverage send real GraphQL queries and aggregate across organizations, workflows, executions, variables and packs live - and your AI sees the answer, not a page of GraphQL JSON. A Rewst answer that is refused, errored or missing a value is reported as a failure, never as empty or zero data.

Known limitation of this build: the typed entity commands (organizations, workflows, org-variables and the rest, plus sync) are generated as REST-shaped calls the Rewst GraphQL gateway refuses, so they fail with an HTTP 400 or a GraphQL error. Use the seven commands above and doctor, which are the ones that reach Rewst today.

The pain this closes

Rewst is the automation layer a lot of MSPs now run service delivery on - and its only surface is a GraphQL gateway and a web app. On r/msp and in the Rewst community, the recurring theme is operational blindness at scale: an automation that quietly stopped firing, a workflow that's been failing for a week in one client and nobody noticed, a pack that reached 18 of 20 tenants. The data exists, but answering "is automation healthy for this client?" means opening the web app and reading execution history org by org. For an MSP, Rewst automations ARE the service - a failed workflow is a ticket that didn't get created.

This skill answers those questions directly:

• health --org - succeeded/failed/running counts plus time saved, with an unhealthy verdict when failures are present
• failures --org --since 12h - the recent failed runs, newest first - the triage queue, not every execution
• dormant --org --days 30 - workflows that stopped running after a trigger or integration broke
• roi --org --since 30d - humanSecondsSaved aggregated into hours saved, for a QBR
• drift --org --against - what one tenant has that another is missing (vari