Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Fix Duo MFA lockouts and see every MSP subaccount at once, from your AI agent.
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.
CISCO_DUO_API_HOST, CISCO_DUO_IKEY, CISCO_DUO_SKEY, CISCO_DUO_ACCOUNT_ID, CISCO_DUO_MCP_READ_ONLY, CISCO_DUO_BASE_URL, CISCO_DUO_MCP_HTTP_TOKEN, CISCO_DUO_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.
CISCO_DUO_ACCOUNT_ID envCISCO_DUO_MCP_READ_ONLY envCISCO_DUO_BASE_URL envCISCO_DUO_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: CISCO_DUO_API_HOST, CISCO_DUO_IKEY, CISCO_DUO_SKEY, CISCO_DUO_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.4) reached the registry 15 days ago.
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, ProAgentStore
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.
MCP-first control plane for ProAgentStore agents and private instances.
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 Cisco Duo
API. Not affiliated with, endorsed by, or sponsored by Cisco Systems, Inc.
Full skill page - install, outcomes, safety model.
Fix Duo MFA lockouts in one command and see every MSP subaccount at once, with signed Admin API calls. 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 run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also make changes with your credentials. Use the default stdio transport. If
you set up 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 Cisco Duo skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register cisco-duo-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add cisco-duo-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 cisco-duo-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs cisco-duo-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode 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 Cisco Duo MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Cisco Duo 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 cisco-duo@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Cisco Duo 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/cisco-duo/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-duo/install.ps1 | iex. Then authenticate per the README and runcisco-duo-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/cisco-duo/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-duo/install.sh)
The installer drops both cisco-duo-cli (the CLI) and cisco-duo-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
cisco-duo-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/cisco-duo/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-duo/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 cisco-duo@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/cisco-duo --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/cisco-duo --force
Hermes speaks MCP natively, so it can also use the cisco-duo-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the cisco-duo skill from https://github.com/servosity/msp-skills/tree/main/skills/cisco-duo. The skill defines how its required CLI (
cisco-duo-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.
In the Duo Admin Panel, go to Applications > Protect an Application > Admin API and create an Admin API application. An MSP creates it in the parent account and grants subaccount permissions. Copy its three values:
export CISCO_DUO_API_HOST="api-XXXXXXXX.duosecurity.com" # API hostname
export CISCO_DUO_IKEY=" " export CISCO_DUO_SKEY=" " cisco-duo-cli doctor
doctor checks the API host, then sends one signed read (GET /admin/v1/users?limit=1) and reports the credential as valid, rejected (HTTP 401), or scope-limited (HTTP 403: the application lacks Grant resource - Read). It exits 0 by default; scripts should add --fail-on error (fails on a rejected key) or --fail-on warn (also fails on a scope-limited one). The secret key only signs requests; it is never sent to Duo.
Grant only the permissions your workflow needs: read-only work needs Grant resource - Read, Grant read log and Grant read information; as an MSP, --account-id and the fleet commands also need Grant accounts - Read, and fleet summary's user-limit column needs Grant user limits - Read. Unlocking users, issuing bypass codes and swapping phones add Grant resource - Write. See governance.md.
As an MSP, add --account-id to any command (a subaccount ID, or its exact name from accounts list) or set CISCO_DUO_ACCOUNT_ID. The CLI looks the customer up in your parent account, sends the request to that customer's own API host, and keeps a separate local store per customer. That store is keyed by exactly what you pass, so pick one form per customer and stick to it (the account ID is safest): a sync run with the name and an audit run with the ID read different stores. fleet summary, fleet risk and fleet find-user always cover every customer.
audit bypass, audit stale and search read a local mirror. Populate it once per tenant:
cisco-duo-cli sync --resources users,admins,phones,bypass_codes --account-id DA9VZOC5X63I2W72NRP9
sync only reads from Duo and writes a SQLite file under your user account. The audits report complete=false when a resource they need was never synced or its last sync stopped part-way, so an empty result is never mistaken for a clean tenant. The lockout, phone-swap, fleet and failures commands always read live.
| Question your MSP keeps asking | Command |
|---|---|
| Why can't this user get through Duo, and which fix applies? | cisco-duo-cli lockout triage "jane@example.com" --account-id "Acme Corp" |
| Unlock them and give them a one-hour, single-use bypass code (preview first) | cisco-duo-cli lockout fix "jane@example.com" --account-id "Acme Corp" --bypass |
| They got a new phone number. Move their Duo to it. | cisco-duo-cli phone-swap "jane@example.com" --number +15551234567 --remove-old |
| Which customer is this person in? | cisco-duo-cli fleet find-user "jdoe@example.com" |
| Which customers have users in bypass, locked out, or never enrolled? | cisco-duo-cli fleet risk |
| Which customers are near their Duo user limit or low on telephony credits? | cisco-duo-cli fleet summary |
| Who in this tenant can skip MFA, and who issued their bypass codes? | cisco-duo-cli audit bypass --older-than 30d |
| Who is still unenrolled after a week? Re-send their enrollment emails. | cisco-duo-cli enrollment chase --older-than 7d --limit 25 |
| What failed or fraud-flagged logins happened this week, and for whom? | cisco-duo-cli failures --since 7d |
| Is my auth and connectivity actually working? | cisco-duo-cli doctor |
lockout fix, phone-swap and enrollment chase print a plan and change nothing until you add --apply.
Full command reference: [guide.md](
Only the beginning is shown; read the rest in the repo