Cisco Duo
● Activeio.github.WYRE-AI/cisco-duo-mcp
MCP server for Cisco Duo's identity/MFA administration API.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"cisco-duo-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.2"
],
"env": {
"DUO_IKEY": "<your DUO_IKEY>",
"DUO_SKEY": "<your DUO_SKEY>",
"DUO_API_HOST": "<your DUO_API_HOST>",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}
}claude mcp add --env DUO_IKEY='<your DUO_IKEY>' --env DUO_SKEY='<your DUO_SKEY>' --env DUO_API_HOST='<your DUO_API_HOST>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info --transport stdio cisco-duo-mcp -- docker run -i --rm ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.2codex mcp add cisco-duo-mcp --env DUO_IKEY='<your DUO_IKEY>' --env DUO_SKEY='<your DUO_SKEY>' --env DUO_API_HOST='<your DUO_API_HOST>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info -- docker run -i --rm ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.2code --add-mcp '{"name":"cisco-duo-mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.2"],"env":{"DUO_IKEY":"<your DUO_IKEY>","DUO_SKEY":"<your DUO_SKEY>","DUO_API_HOST":"<your DUO_API_HOST>","MCP_TRANSPORT":"stdio","AUTH_MODE":"env","LOG_LEVEL":"info"}}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
- DUO_IKEYrequiredDuo integration key (Basic-auth username for the v5 signed-request scheme). Not secret on its own, but paired with DUO_SKEY it authenticates as this integration.
- DUO_SKEYrequiredsecretDuo secret key - HMAC-SHA512 signing key for every request. Bearer-equivalent for this integration's admin scope.
- DUO_API_HOSTrequiredThis account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.
- MCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
- AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
- LOG_LEVELLog verbosity: debug, info, warn, error
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Security & Identity
- Version
- 1.0.2
- Registry
- active
- Published
- 11/20/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Mostly fine: Cisco Duo is maintained.
- Maintained
- Active
- Last commit 9 days ago (Nov 12, 2026), 2 open issues.
- Official registry
- Active
- Published as io.github.WYRE-AI/cisco-duo-mcp in the official MCP registry, version 1.0.2.
- Source
- No licence found
- Public repository, but GitHub reports no recognised licence (1 stars). Check the README before shipping it in a product.
- Runs
- On your machine
- A local Docker package started by your client; it can reach whatever your user account can.
- Credentials
- 3 required
- Declared environment variables: DUO_IKEY, DUO_SKEY, DUO_API_HOST. They stay on your machine; the config on this page shows where each goes.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.
On GitHub
read Nov 17, 2026- Stars
- 1
- Forks
- 0
- Last push
- Nov 12, 2026
- License
- Other
TypeScript
From the README
Cisco Duo MCP Server MCP server for Cisco Duo's identity/MFA administration API - read-only visibility into users, their enrolled MFA methods, phones, hardware and desktop tokens, groups, integrations, and the authentication/administrator/telephony logs, for AI assistants and the WYRE Conduit gateway. Duo has no machine-readable OpenAPI spec; every endpoint in this connector was manually verified against Duo's published docs (Admin API, Auth API) and cross-checked against Duo's own reference client, duoclientpython. Authentication Duo authenticates with a signed-request scheme, not OAuth2 and not a bearer token. This connector implements Duo Auth Signature v5 (HMAC-SHA512) - the current recommended method - not the legacy v2 (HMAC-SHA1) scheme. Three credential fields are required: Every request is signed fresh, per call, in src/client.ts's signV5Get(). The 7-line canonical string (date, method, host, path, sorted query params, SHA-512 body hash, SHA-512 signed-headers hash) is joined with \n and HMAC-SHA512-signed with skey; the hex signature is sent as Authorization: Basic base64(ikey:signature) alongside a Date header carrying the exact same RFC 2822 timestamp that was signed.…
Read the full README on GitHub →Alternatives to Cisco Duo
All Cisco Duo alternatives →Best Security & Identity servers →The most-starred Security & Identity servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| Handsy AI | 5,215 | Nov 2026 | Local / not checked |
| HOL Guard | 1,118 | Nov 2026 | Local / not checked |
| SonarQube MCP Server | 689 | Nov 2026 | Local / not checked |
| MCP Ssh Manager | 545 | Nov 2026 | Local / not checked |
| Security Detections | 529 | Nov 2026 | Local / not checked |
Cisco Duo: questions people ask
- Is Cisco Duo a remote or a local MCP server?
- According to its entry in the official MCP registry, Cisco Duo ships as a local package (Docker) that your client starts on your machine.
- Does Cisco Duo need an API key?
- Its registry entry declares 3 required environment variables: DUO_IKEY, DUO_SKEY, DUO_API_HOST. The config on this page shows where each goes.
- Is Cisco Duo safe to use?
- Mostly fine: Cisco Duo is maintained. In detail — maintained: Active; official registry: Active; source: No licence found; runs: On your machine; credentials: 3 required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is Cisco Duo still maintained?
- Active: the repository's last commit 9 days ago. Last push Nov 12, 2026, 1 GitHub stars, Other licence. Read from GitHub on Nov 17, 2026.
- How do I add Cisco Duo to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More from WYRE-AI
All 78 servers by WYRE-AI →- AutotaskMCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.Business & CRM★ 64
- ConnectWise ManageMCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more.Business & CRM★ 32
- NinjaOneMCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.Business & CRM★ 32
- IT GlueMCP server for IT Glue — organizations, configurations, passwords, flexible assets, and documents.Security & Identity★ 18
More Security & Identity servers
Browse all Security & Identity →ESET PROTECT
WYRE-AI
MCP server for ESET PROTECT's ESET Connect API - device, EDR, vulnerability, patch, and user data.
Hudu
WYRE-AI
MCP server for Hudu IT documentation — companies, assets, articles, passwords, and procedures.
IT Glue
WYRE-AI
MCP server for IT Glue — organizations, configurations, passwords, flexible assets, and documents.
Keeper Secrets Manager
WYRE-AI
Read-only multitenant Streamable HTTP bridge over Keeper Secrets Manager's MCP server.
KnowBe4
WYRE-AI
MCP server for KnowBe4 security awareness training — users, groups, training, phishing campaigns.
Mimecast
WYRE-AI
MCP server for Mimecast email security: message queue, held messages, domains, and threats.
Add the badge to your site
Show visitors that Cisco Duo is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-wyre-ai-cisco-duo-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Cisco Duo — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-wyre-ai-cisco-duo-mcp?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-wyre-ai-cisco-duo-mcp) [](https://serverdex.io/install/vscode/io-github-wyre-ai-cisco-duo-mcp) [](https://serverdex.io/install/claude-code/io-github-wyre-ai-cisco-duo-mcp)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-wyre-ai-cisco-duo-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-wyre-ai-cisco-duo-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-wyre-ai-cisco-duo-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).