Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Operate and monitor Rewst RPA across every client org: automation health, failures, ROI, and drift.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
REWST_BASE_URL, REWST_API_TOKEN, REWST_MCP_HTTP_TOKEN, REWST_MCP_READ_ONLY, REWST_NO_LOCAL_DATA, REWST_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILEValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
REWST_BASE_URL envREWST_MCP_READ_ONLY envREWST_NO_LOCAL_DATA envREWST_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: REWST_API_TOKEN, REWST_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.8) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Rewst skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register rewst-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add rewst-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add rewst-mcp to mcp.json under the servers key, then pick Agent mode. |
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.
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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionrewst-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 setREWST_CLI_PATHto 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rewst/install.ps1 | iex. Then authenticate per the README and runrewst-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
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= .
| Question your MSP keeps asking | Command |
|---|---|
| Is automation healthy for this client right now? | rewst-cli health --org --since 24h --agent |
| Which workflows failed for this org overnight? | rewst-cli failures --org --since 12h --agent |
| Which workflows have gone dormant (no runs in 30 days)? | rewst-cli dormant --org --days 30 --agent |
| How much time did automation save this client? | rewst-cli roi --org --since 30d --agent |
| What does one org have that another is missing? | rewst-cli drift --org --against --agent |
| Which managed sub-orgs are missing an integration pack? | rewst-cli coverage --parent --pack microsoft --agent |
| Which org ids can my token see? | rewst-cli orgs --agent |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
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.
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 presentfailures --org --since 12h - the recent failed runs, newest first - the triage queue, not every executiondormant --org --days 30 - workflows that stopped running after a trigger or integration brokeroi --org --since 30d - humanSecondsSaved aggregated into hours saved, for a QBRdrift --org --against - what one tenant has that another is missing (variOnly the beginning is shown; read the rest in the repo