Cisco Duo MCP

Cisco Duo + 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 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.

Works with your agent

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):

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.

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

Download 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

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

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, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-duo/install.ps1 | iex. Then authenticate per the README and run cisco-duo-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/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

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/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.

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/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.

Install for OpenClaw

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 the openclaw: frontmatter block.

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

Authenticate

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.

Work with one customer, or all of them

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.

Sync before you audit

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.

What this skill does

lockout fix, phone-swap and enrollment chase print a plan and change nothing until you add --apply.

Full command reference: [guide.md](