Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Cisco Support MCP Server

npm version License: MIT MCP Glama Cisco Code Exchange Docker CI Skills Buy Me A Coffee

MCP server for the Cisco Support APIs: bugs, security advisories (PSIRT), end-of-life (EoX), serial-number coverage, product info, software suggestions, TAC cases and RMAs.

  • 12 read-only tools, concise output by default, normalized paging, recorded against the live Cisco APIs

  • 6 workflow prompts and cisco:// resources

  • MCP Apps view: interactive tables in clients that support it (Claude, MCPJam, VS Code, …); plain text elsewhere

  • MCP 2026-07-28 (TypeScript SDK v2), and 2025-era clients too

  • stdio for local clients, stateless Streamable HTTP (--http) with bearer-token auth and rate limiting for remote use

  • npm (with provenance) and Docker (linux/amd64, linux/arm64)

Upgrading from 2.x? Tool names changed and several features were removed. See Upgrading to 3.0.

Quick start

  1. Create an app on the Cisco API Console and note its client ID and secret. Request access to each Cisco API you want (Bug, PSIRT, EoX, Serial Number to Information, Product Information, Software Suggestion, Case, RMA).

  2. Add the server to your MCP client. Claude Desktop (claude_desktop_config.json):

    {
      "mcpServers": {
        "cisco-support": {
          "command": "npx",
          "args": ["-y", "mcp-cisco-support"],
          "env": {
            "CISCO_CLIENT_ID": "your_client_id",
            "CISCO_CLIENT_SECRET": "your_client_secret"
          }
        }
      }
    }

    Config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart the client after editing.

  3. Ask things like:

    • "Which security advisories affect IOS XE 17.9.4, and what's the first fixed release?"

    • "Should I upgrade my C9300-48P from 17.15.4b? Compare with Cisco's suggested release."

    • "Check coverage and end-of-life for serials FJC29161RHS, FJC29161H2U."

    • "Open severity 1–2 bugs mentioning memory leak."

Requires Node.js 20+.

Related MCP server: Sloot MCP Server

Tools

Tool

What it does

bug_get

Bug details by ID (up to 5)

bug_search

Bugs by keyword, product ID, product series or product name; releases affected or fixed; several severities in one call

assess_upgrade

Current vs target release: open bugs on each, bugs the target fixes, advisories fixed / remaining / new, end-of-life. Defaults to Cisco's suggested release

psirt_get

Security advisory by advisory ID, CVE or bug ID

psirt_search

Advisories affecting an OS release (os_type + version), or by product, severity, year, latest, date range

eox_get

End-of-sale / end-of-support by product IDs, serials, software releases or announcement dates

device_lookup

Per serial number: contract coverage and warranty, product details and EoX

product_get

Product name, series, category, support page; optional MDF names

software_get

Cisco-suggested, latest, or compatible releases for a product

case_get

TAC cases by number (detailed adds notes and owner)

case_search

TAC cases by contract or user ID

rma_get

An RMA by number, or RMAs for a user ID

Exact releases: if you give a partial release ("17", "17.9") where Cisco needs an exact one (psirt_search, assess_upgrade), the server asks you to pick, first the train and then the release, using Cisco's list of known releases. For bug_search (with os_type) a train is valid, so it offers the exact releases and lets you keep the train. Clients without elicitation support get the candidates in the result, and the model asks you instead.

All tools are always listed. Results are concise unless response_format: "detailed"; list results include paging (total_records, next_page) and empty results include a hint. If your credentials aren't entitled to a Cisco API, its tools return "access denied (403) … not entitled to the X API". Arguments and examples: Available Tools.

Prompts

Prompt

Use it for

cisco-upgrade-planning

Go/no-go for a software upgrade (assess_upgrade, suggested release, remaining severe bugs)

cisco-known-issues

Open bugs (worst first) and advisories for a product or release, e.g. before a change window

cisco-incident-investigation

Match a symptom to known bugs, workarounds and fixed releases

cisco-security-advisory

Advisories affecting a release or product, with fix releases

cisco-lifecycle-planning

End-of-life dates, migration products and contract coverage

cisco-case-investigation

A TAC case with its notes, linked bugs and RMAs

Most prompts accept a serial number instead of a product; the model then starts with device_lookup. Details: MCP Prompts.

Resources and MCP Apps

URI

Returns

cisco://bugs/{bug_id}

bug_get output

cisco://products/{product_id}

product_get output

cisco://security/advisories/{advisory_id}

psirt_get output

cisco://security/cve/{cve_id}

psirt_get output

cisco://security/advisories/recent

20 most recent advisories

cisco://security/advisories/critical

Most recent critical advisories

Clients that support MCP Apps render bug_get, bug_search, psirt_get, psirt_search, device_lookup and assess_upgrade results as interactive tables (filters, Cisco links, next page). Other clients get the same text output. See MCP Apps.

assess_upgrade (C9300-48P, 17.15.4b → 17.18.4) and bug_search rendered in Claude Desktop.

HTTP mode

export CISCO_CLIENT_ID=... CISCO_CLIENT_SECRET=...
export MCP_BEARER_TOKEN=$(openssl rand -hex 16)   # or: npx mcp-cisco-support --generate-token
npx mcp-cisco-support --http          # http://127.0.0.1:3000/mcp

Endpoint

Method

Notes

/mcp

POST

Streamable HTTP, stateless; Authorization: Bearer <token>

/health, /

GET

No auth

Stateless means no sessions: any request can be sent on its own, and several instances can sit behind a load balancer. There is no OAuth; /.well-known/* returns 404 so clients fall back to the bearer token (external IdP support: #14).

curl -s -X POST http://127.0.0.1:3000/mcp \
  -H "Authorization: Bearer $MCP_BEARER_TOKEN" \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"psirt_search","arguments":{"os_type":"iosxe","version":"17.9.4"}}}'

Docker

docker run -d -p 3000:3000 \
  -e CISCO_CLIENT_ID=your_id -e CISCO_CLIENT_SECRET=your_secret \
  -e MCP_BEARER_TOKEN=your_token \
  ghcr.io/sieteunoseis/mcp-cisco-support:latest

The image starts in HTTP mode on 0.0.0.0:3000. Tags: latest, vX.Y.Z. More: Docker Deployment.

Configuration

Variable

Default

Purpose

CISCO_CLIENT_ID, CISCO_CLIENT_SECRET

(required)

Cisco API Console app credentials

MCP_BEARER_TOKEN

random, printed once

Bearer token for HTTP mode

PORT / HOST

3000 / 127.0.0.1

HTTP listen address (0.0.0.0 in Docker)

MCP_ALLOWED_ORIGINS

localhost only

Extra browser origins allowed to call /mcp (comma-separated)

MCP_RATE_LIMIT

120

HTTP requests per minute per client (bearer token, or IP without auth); 0 disables

DISABLE_GCF_FORMAT

false

true returns JSON instead of compact GCF text

DANGEROUSLY_OMIT_AUTH

false

Disable HTTP auth (local testing only)

Security notes: Security Guide. Problems: Troubleshooting.

AI Agent Skill (optional)

The cisco-support-mcp skill teaches an agent to use these tools well: which tool answers which question, Cisco's input formats, and what to do with the server's status results (exact-release questions, 403s, the MCP Apps view).

npx skills add sieteunoseis/mcp-cisco-support

Or copy it by hand (Claude Code):

mkdir -p ~/.claude/skills/cisco-support-mcp
curl -fsSL https://raw.githubusercontent.com/sieteunoseis/mcp-cisco-support/main/skills/cisco-support-mcp/SKILL.md \
  -o ~/.claude/skills/cisco-support-mcp/SKILL.md

The server works without it; the skill just helps the agent pick tools and arguments.

Development

npm ci
npm test            # unit, protocol and HTTP tests (Cisco responses from tests/fixtures/cisco)
npm run build       # dist/index.js
npm run dev         # stdio, auto-reload   (npm run dev:http for HTTP)

Live integration tests are opt-in: RUN_INTEGRATION=1 CISCO_CLIENT_ID=... CISCO_CLIENT_SECRET=... npm test. Code layout, verified Cisco API behaviour, fixtures and the release process: CLAUDE.md and Development Guide.

Support

If you find this project helpful, consider supporting development:

Buy Me A Coffee

License

MIT, see LICENSE.

Available Tools

12 tools
assess_upgradeAssess a Cisco software upgradeA
Read-only

Compare a current and target release for a product: open bugs on each, bugs the target fixes, and (with os_type) security advisories fixed, remaining and new; plus hardware end-of-life. Without target_version, uses Cisco's suggested release.

Inputs: product_id (required), current_version (required), os_type, max_severity, +2 more.

bug_getGet Cisco bugs by IDA
Read-only

Get Cisco bug (CDETS) details by ID, e.g. CSCwh87343. Up to 5 IDs.

Inputs: bug_ids (required), response_format.

case_getGet Cisco TAC casesA
Read-only

Get Cisco TAC support cases by number. response_format "detailed" adds notes, owner and contact (one API call per case).

Inputs: case_ids (required), response_format.

device_lookupLook up Cisco devices by serial numberA
Read-only

For each serial number: contract coverage and warranty, product details, and end-of-life dates, in one call. Up to 20 serials.

Inputs: serial_numbers (required), include, response_format.

eox_getGet Cisco end-of-life datesA
Read-only

End-of-sale / end-of-support dates by exactly one of product_ids, serial_numbers, software_releases, or an announcement date range (start_date + end_date).

Inputs: page, end_date, page_size, start_date, +4 more.

product_getGet Cisco product informationA
Read-only

Product name, series, category and support page for product IDs. include_mdf adds the MDF (Cisco software download tree) names used by software_get.

Inputs: product_ids (required), include_mdf, response_format.

psirt_getGet a Cisco security advisoryA
Read-only

Get Cisco PSIRT security advisories by exactly one of advisory_id, cve or bug_id.

Inputs: cve, bug_id, advisory_id, response_format.

rma_getGet Cisco RMAsA
Read-only

Get a Cisco RMA (return) by rma_number, or list RMAs for a Cisco.com user_id (optionally filtered by date and status).

Inputs: page, status, to_date, user_id, +3 more.

software_getGet Cisco software recommendationsB
Read-only

Cisco suggested software for products. view: "suggested" (Cisco-recommended releases, default), "releases" (latest releases), or "compatible" (releases compatible with one product, optionally from current_release).

Inputs: page, view, mdf_ids, product_ids, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools are mostly cleanly separated by resource and action: bug/case/psirt search versus get, product/software/EoX/RMA lookups, and aggregate workflows like assess_upgrade and device_lookup. The main possible overlap is between aggregate tools and narrower lookup tools, but descriptions make the intended boundaries clear.

    Naming Consistency4/5

    Most tools follow a consistent snake_case resource_action pattern such as bug_get, case_search, psirt_get, eox_get, and software_get. assess_upgrade is the main deviation with an action_resource order, but overall the convention remains predictable.

    Tool Count5/5

    Twelve tools is well-scoped for a Cisco support server covering bugs, cases, security advisories, products, software, EoX, RMAs, and device lookups. Each tool earns its place, and the set is neither thin nor bloated.

    Completeness5/5

    The surface provides broad read-only coverage across Cisco support workflows, including search and retrieval for bugs, cases, PSIRT advisories, products, software, EoX, RMAs, contracts, warranty, and upgrade assessment. There are no obvious lifecycle gaps for the apparent read-only support-assistance domain.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript MCP server implementation using Express.js that provides basic tools like echo, time retrieval, and calculator functionality. Features session management, RESTful API endpoints, and Server-Sent Events for streamable communication.
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.
      547 npm
      -
    • A
      license
      A
      quality
      Not graded
      maintenance
      A production-ready TypeScript template for building MCP servers with dual transport support (stdio/HTTP), OAuth 2.1 foundations, SQLite caching, observability, and security features including PII sanitization and rate limiting.
      4
      29 npm
      -