Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Riverside API surface as MCP tools.
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.
RIVERSIDE_FM_BASE_URL, RIVERSIDE_FM_NO_CONFIG_WRITE, RIVERSIDE_FM_MCP_READ_ONLY, RIVERSIDE_FM_NO_LOCAL_DATA, RIVERSIDE_FM_MCP_HTTP_TOKEN, RIVERSIDE_FM_SKIP_TLS_VERIFY, RIVERSIDE_FM_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.
RIVERSIDE_FM_BASE_URL envRIVERSIDE_FM_NO_CONFIG_WRITE envRIVERSIDE_FM_MCP_READ_ONLY envRIVERSIDE_FM_NO_LOCAL_DATA envRIVERSIDE_FM_SKIP_TLS_VERIFY envRIVERSIDE_FM_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE 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 7, 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: RIVERSIDE_FM_MCP_HTTP_TOKEN
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.6) 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: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
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 Riverside
API. Not affiliated with, endorsed by, or sponsored by RiversideFM, Inc..
Full skill page - install, outcomes, safety model.
Riverside API surface as MCP tools. 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.
Security note (until this connector is reprinted). Do not put this
connector behind the
supergatewaybridge or any other stdio-to-HTTP bridge,
not even on localhost. The bridge adds no password, so anyone who can reach
its port can use the MCP tools with your credentials. Use the default stdio
transport. If you set up a bridge or a tunnel for a remote agent, shut it
down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Riverside skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register riverside-fm-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add riverside-fm-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 riverside-fm-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs riverside-fm-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server. This connector speaks stdio only, and the bridge it would need is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it 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.
.mcpbDownload Riverside MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Riverside 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 riverside-fm@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Riverside 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/riverside-fm/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/riverside-fm/install.ps1 | iex. Then authenticate per the README and runriverside-fm-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/riverside-fm/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/riverside-fm/install.sh)
The installer drops both riverside-fm-cli (the CLI) and riverside-fm-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
riverside-fm-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/riverside-fm/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/riverside-fm/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 riverside-fm@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/riverside-fm --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/riverside-fm --force
Hermes speaks MCP natively, so it can also use the riverside-fm-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the riverside-fm skill from https://github.com/servosity/msp-skills/tree/main/skills/riverside-fm. The skill defines how its required CLI (
riverside-fm-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.
See mcp-install.md for the credentials riverside-fm-cli needs.
| Question you keep asking | Command |
|---|---|
| Back up everything in a studio to disk? | riverside-fm-cli bulk export --studio my-studio --out ./archive |
| Get the most useful asset for one recording in a single shot? | riverside-fm-cli grab --out ./dl |
| Find a quote across my whole transcript archive? | riverside-fm-cli search "network effects" --json |
| Turn a transcript into captions for a web player? | riverside-fm-cli transcripts convert --format srt --out ep.srt |
| Who talked the most in this episode? | riverside-fm-cli transcripts talktime --json |
| Which takes in a studio are fully ready to edit? | riverside-fm-cli ready --studio my-studio |
| Pull every Magic Clip for a project with fresh URLs? | riverside-fm-cli clips harvest --project 69fcda9fba030a19ae93a526 --download --out ./clips |
| Refresh expiring CloudFront media links before they die? | riverside-fm-cli media refresh --project 69fcda9fba030a19ae93a526 --prefetch --out ./media |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Riverside integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "find the episode where we mentioned that customer story across two years of a weekly show" or "archive every take in this studio before we cancel the plan."
This skill syncs Riverside into a local SQLite mirror with full-text search. Aggregate questions become one local query: instant, offline, and the AI sees the answer, not the raw data. Compound commands like bulk export, clips harvest, and search join across studios, projects, takes, transcripts, and clip-assets - work a stateless API wrapper can't do.
Riverside records studio-quality podcast and video, but getting your own content back out is a manual slog. There is no bulk export: every transcript, audio track, and video file comes out one click at a time, per take, down the Studio then Project then Take path. Back up a fifty-episode show and you face hundreds of clicks. The friction is real enough that podcasters in community groups - such as the Podcasting subreddit and the podcast-host Facebook groups - keep asking how to "batch download Riverside recordings" to archive a series or free up storage. And the official API that would fix it is gated behind a custom-priced Business plan, so Pro, Live, and Webinar accounts get no supported way to back up, search, or re-format their own recordings.
This skill closes that gap:
See pain-point.md for the longer narrative.
Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way riverside-fm-mcp runs, and shares MCP configuration with Codex (OpenAI): add riverside-fm-mcp under Settings > MCP servers as a STDIO serve
Only the beginning is shown; read the rest in the repo