Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Cisco Duo

by WYRE-AIversion 1.0.1i★ 1iRuns on your computerRepository ↗
Registry nameio.github.WYRE-AI/cisco-duo-mcp

How to install

What it does

MCP server for Cisco Duo's identity/MFA administration API.

  • Connects Runs on your computer
  • Account or key Needs DUO_SKEY, AUTH_MODE · 2 settings to fill in (DUO_IKEY, DUO_API_HOST)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity4/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score16/100

Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Cisco Duo. Follow https://mcp.popnx.com/i/wyre-ai-cisco-duo-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Cisco Duo for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "cisco-duo": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "DUO_IKEY", "-e", "DUO_SKEY", "-e", "DUO_API_HOST", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1" ], "env": { "DUO_IKEY": "your-value", "DUO_SKEY": "your-value", "DUO_API_HOST": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Cisco Duo tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Cisco Duo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Cisco Duo site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • DUO_IKEY Duo 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_API_HOST This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "cisco-duo": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "DUO_IKEY",
            "-e",
            "DUO_SKEY",
            "-e",
            "DUO_API_HOST",
            "-e",
            "AUTH_MODE",
            "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
          ],
          "env": {
            "DUO_IKEY": "your-value",
            "DUO_SKEY": "your-value",
            "DUO_API_HOST": "your-value",
            "AUTH_MODE": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Cisco Duo and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Cisco Duo or shows a Cisco Duo tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Cisco Duo yet

Cisco Duo runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Cisco Duo

  • You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)
  • You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)
  • You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Cisco Duo for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user cisco-duo --env DUO_IKEY=your-value --env DUO_SKEY=your-value --env DUO_API_HOST=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e AUTH_MODE ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Cisco Duo tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Cisco Duo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Cisco Duo site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • DUO_IKEY Duo 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_API_HOST This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user cisco-duo --env DUO_IKEY=your-value --env DUO_SKEY=your-value --env DUO_API_HOST=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e AUTH_MODE ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Cisco Duo listed as connected

  7. Try it

    Use Cisco Duo and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Cisco Duo or shows a Cisco Duo tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Cisco Duo for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "cisco-duo": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "DUO_IKEY", "-e", "DUO_SKEY", "-e", "DUO_API_HOST", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1" ], "env": { "DUO_IKEY": "your-value", "DUO_SKEY": "your-value", "DUO_API_HOST": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Cisco Duo tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Cisco Duo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Cisco Duo site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • DUO_IKEY Duo 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_API_HOST This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Cisco Duo settings, DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Cisco Duo and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Cisco Duo or shows a Cisco Duo tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Cisco Duo key (create it on the maker’s site) · 2 setting(s) to fill in (DUO_IKEY, DUO_API_HOST) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Cisco Duo for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "cisco-duo": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "DUO_IKEY", "-e", "DUO_SKEY", "-e", "DUO_API_HOST", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1" ], "env": { "DUO_IKEY": "your-value", "DUO_SKEY": "your-value", "DUO_API_HOST": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Cisco Duo tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Cisco Duo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Cisco Duo site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • DUO_IKEY Duo 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_API_HOST This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Cisco Duo settings, DUO_SKEY, AUTH_MODE, DUO_IKEY, DUO_API_HOST is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Cisco Duo and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Cisco Duo or shows a Cisco Duo tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Cisco Duo💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user cisco-duo --env DUO_IKEY=your-value --env DUO_SKEY=your-value --env DUO_API_HOST=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e AUTH_MODE ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "cisco-duo": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ],
      "env": {
        "DUO_IKEY": "your-value",
        "DUO_SKEY": "your-value",
        "DUO_API_HOST": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "cisco-duo": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ],
      "env": {
        "DUO_IKEY": "your-value",
        "DUO_SKEY": "your-value",
        "DUO_API_HOST": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "cisco-duo": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ],
      "env": {
        "DUO_IKEY": "your-value",
        "DUO_SKEY": "your-value",
        "DUO_API_HOST": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

Values you fill in

  • DUO_IKEY required env
    Duo 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_SKEY secret required env
    Duo secret key - HMAC-SHA512 signing key for every request. Bearer-equivalent for this integration's admin scope.
  • DUO_API_HOST required env
    This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.
  • MCP_TRANSPORT env
    Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE secret required env
    Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL env
    Log verbosity: debug, info, warn, error

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
1.0.1
Categoryi
Other
Published to registryi
Nov 4, 2026
Code last changedi
Nov 13, 2026
Maker
WYRE-AI
Packages
oci: ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account WYRE-AI, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 6 days ago

  • ! Caution

    Has a licence

    GitHub could not identify the licence type; open the file to check

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wyre-ai-cisco-duo-mcp.svg)](https://mcp.popnx.com/en/servers/wyre-ai-cisco-duo-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 86% of the other 20749 servers in this category
  • Published to the registry more recently than 75% of the other 20749 servers in this category
  • Basic checks equal to or better than 46% of the other 20749 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cisco Duo safe?

It passed 2 of 3 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.

What keys or codes does it need?

You need to fill in: DUO_SKEY, AUTH_MODE

Does it run on my computer or in the cloud?

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

Is it still maintained?

The GitHub repo last changed 6 days ago, and the latest version (1.0.1) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Cisco Duo
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks2/34/44/44/41/44/4
LicenseNOASSERTIONAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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.

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, duo_client_python.

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:

FieldDescription
ikeyIntegration key - identifies the integration. Sent as the Basic-auth username. Not secret.
skeySecret key - the HMAC-SHA512 signing key. Bearer-equivalent for this integration's admin scope; never sent over the wire itself, never logged.
apiHostThis account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com. Not secret.

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. This connector is GET-only, so the body hash is always the digest of the empty string, and no additional X-Duo-* signed headers are used, so the header hash is always the digest of the empty string too.

In gateway mode the three fields arrive per-request via X-Duo-Ikey / X-Duo-Skey / X-Duo-Api-Host headers, injected by the Conduit gateway. In local/stdio mode they're read once from DUO_IKEY / DUO_SKEY / DUO_API_HOST.

What the credential itself can do vs. what this connector calls. This connector's code is read-only by construction (see Scope, below), but that describes this codebase, not Duo's server-side enforcement. Duo Admin API integrations carry their own independently-configured permission grants (Grant Read Resource, Grant Write Resource, Grant Read Log, Grant Read Settings, Grant Write Settings, etc., set in the Duo Admin Panel when the integration is created) and Duo does enforce these server-side - an integration without Grant Write Resource gets a real authorization error from Duo itself on any write attempt, confirmed against Duo's docs and community reports of exactly that failure mode. This connector never exercises anything beyond read permissions, but the ikey/skey pair a customer supplies is only as narrowly scoped as the permissions they granted that integration in Duo - if a customer grants this integration Grant Write Resource (unnecessary for this connector), the credential itself would be capable of writes even though this connector's code never calls one. Recommend granting this integration only `Grant Read Resource` (and `Grant Read Log` if the log tools are wanted) in Duo's Admin Panel - least-privilege at the credential level, on top of this connector's own code-level restriction.

Defensive field-stripping: Duo's Integrations endpoints are known to echo secret-shaped fields in some read responses, and the API has no machine-readable schema to verify this exhaustively per integration type. Every response from every tool in this connector - not just Integrations - passes through stripSecretFields() before it ever reaches the model: any object key matching /secret|skey/i, at any depth, is dropped. This is a blanket safety net on top of, not instead of, the endpoint-level exclusions below.

Configuration

Env varDescription
DUO_IKEYDuo integration key.
DUO_SKEYDuo secret key (HMAC-SHA512 signing secret).
DUO_API_HOSTThis account's Duo API hostname.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (default, reads the vars above) or gateway (credentials arrive per-request via X-Duo-Ikey/X-Duo-Skey/X-Duo-Api-Host headers, injected by the Conduit gateway).
CONDUIT_S2S_SECRETWhen set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request.
LOG_LEVELdebug \info (default) \warn \error.
Request limits
  • HTTP request bodies are capped at 256 KiB (262144 bytes). After the X-Gateway-S2S check passes, a Content-Length above the cap returns 413 with a JSON-RPC error; bodies without Content-Length are capped by the MCP SDK transport. Unauthenticated requests still get 401 first.
  • tools/call arguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return an isError tool result and are never dispatched.

These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).

Tools

All 22 tools are read-only and classified isAdmin: true in Conduit's VENDOR_TOOL_CONFIG regardless of verb - this is identity/MFA administration data (PII: phone numbers, email, device OS, and enrolled-factor details), sensitive even as a plain read.

Users
  • duo_list_users - list users, optionally filtered by exact username.
  • duo_get_user - get full detail for a user.
  • duo_list_user_groups - list the groups a user belongs to.
  • duo_list_user_phones - list the phones enrolled to a user.
  • duo_list_user_tokens - list the hardware tokens enrolled to a user.
  • duo_list_user_webauthn_credentials - list a user's WebAuthn credentials.
  • duo_list_user_u2f_tokens - list a user's legacy U2F security keys.
Phones
  • duo_list_phones - list phones, optionally filtered by number/extension.
  • duo_get_phone - get full detail for a phone.
Tokens
  • duo_list_hardware_tokens - list hardware tokens (HOTP/TOTP/YubiKey).
  • duo_get_hardware_token - get full detail for a hardware token.
  • duo_list_desktop_tokens - list Duo Desktop tokens.
  • duo_get_desktop_token - get full detail for a Duo Desktop token.
Groups
  • duo_list_groups - list groups.
  • duo_get_group - get full detail for a group.
  • duo_list_group_users - list the users belonging to a group.
Integrations (metadata only)
  • duo_list_integrations - list configured integrations.
  • duo_get_integration - get full metadata for an integration.
Logs
  • duo_get_authentication_log - the authentication log (v2), time-filterable.
  • duo_get_administrator_log - the administrator action log (v1).
  • duo_get_telephony_log - the telephony (call/SMS credit) log (v2).
Auth
  • duo_check_credentials - validate credentials and Auth API connectivity. Side-effect-free; does not initiate any MFA transaction.

Scope

This is a deliberately narrow, read-only v1 surface, built for an identity/MFA administration product where the wrong endpoint is unusually consequential. src/client.ts implements exactly one HTTP verb function (doGet) - there is no doPost/doPut/doDelete anywhere in this codebase, so every exclusion below is structurally enforced, not just documented. src/__tests__/tool-set.test.ts pins the exact 22-tool set and asserts no tool name matches /bypass|delete|disassociate|deactivate|revoke|enroll/i.

Hard-excluded (credential-exposing) - never implemented:

  • GET /admin/v1/users/{user_id}/bypass_codes (get_user_bypass_codes) - returns live, usable MFA-bypass codes. Even as a read, this is the single most sensitive primitive in the API and is excluded alongside its generator, not treated as a safe list/detail read.
  • POST /admin/v1/users/{user_id}/bypass_codes (add_user_bypass_codes) - generates bypass codes.

Hard-excluded (provisioning/mutation) - never implemented:

  • DELETE /admin/v1/users/{user_id}, DELETE /admin/v1/phones/{phone_id}, DELETE /admin/v1/tokens/{token_id}, DELETE /admin/v1/desktoptokens/{desktoptoken_id}, DELETE /admin/v1/groups/{group_id}, DELETE /admin/v3/integrations/{integration_key} - all object deletes.
  • DELETE /admin/v1/users/{user_id}/phones/{phone_id} (delete_user_phone), DELETE /admin/v1/users/{user_id}/tokens/{token_id} (delete_user_token) - disassociate operations.
  • POST /admin/v1/users/{user_id}/phones (add_user_phone), POST /admin/v1/users/{user_id}/tokens (add_user_token) - associate operations.
  • POST /admin/v1/users, POST /admin/v1/phones, POST /admin/v1/tokens (all add_*_token variants), POST /admin/v1/desktoptokens, POST /admin/v1/groups, POST /admin/v3/integrations - all object creates.
  • POST/PUT update endpoints for every object type above (update_phone, update_token, resync_hotp_token, update_desktoptoken, activate_desktoptoken, update_group, integration config updates) and any policy-write endpoint (POST /admin/v1/settings).
  • POST /auth/v2/preauth, POST /auth/v2/auth, POST /auth/v2/enroll, POST /auth/v2/enroll_status - Auth API endpoints that trigger a real user-facing MFA transaction or create an identity.

Out of v1 scope (not credential/provisioning, just not part of this connector's read surface - could be added later as a deliberate follow-up):

  • GET /auth/v2/ping - unauthenticated API liveness check, no admin-relevant data.
  • GET /auth/v2/auth_status - a poll for a live /auth transaction's status; no standalone utility without the excluded /auth//preauth endpoints.
  • GET /admin/v1/admins - the Duo administrator roster (distinct from end-user accounts). Not part of the task's requested tool categories (user/phone/token/group listing+detail, logs, integration metadata, auth-status checks).
  • GET /admin/v1/billing/*, GET /admin/v1/info/summary, GET /admin/v1/settings - account summary/billing/settings reads.
  • GET /admin/v1/users/directorysync - directory sync listing.
  • Accounts API (MSP) - deprecated by Cisco as of 2026-06-11; subaccount management folded into the Admin API's billing endpoints. No separate surface exists to implement.
  • Device API (Trusted Endpoints device cache) - uses a separate mkey/skey credential pair scoped per management-system integration, a different credential model than the account-level ikey/skey this connector is built around. Not implemented in v1; would need its own deliberate credential-shape decision if added.

They can be added as a follow-up if there's demand, after a deliberate scope decision - not by default.

Development

npm install

npm run build npm test npm run lint # tsc --noEmit

Docker

docker build -t cisco-duo-mcp .

docker run -p 8080:8080 -e DUO_IKEY=... -e DUO_SKEY=... -e DUO_API_HOST=... cisco-duo-mcp