mcp-cisco-support
Query and investigate Cisco support data through 12 read-only tools, workflow prompts, and cisco:// resources.
Look up or search Cisco bugs by ID, keyword, product, series/name, release, severity, and status.
Get or search PSIRT security advisories by advisory ID, CVE, bug ID, OS/release, product, severity, year, latest, or date range.
Retrieve end-of-sale/end-of-support data by product IDs, serial numbers, software releases, or announcement dates.
Look up devices by serial number for contract coverage, warranty, product details, and EoX.
Get Cisco product information, support pages, and MDF names.
Get Cisco-suggested, latest, or compatible software releases.
Retrieve or search TAC cases by case number, contract, user ID, status, and date.
Get RMAs by number or list them by user ID, date, and status.
Assess software upgrades against bugs, advisories, end-of-life data, and Cisco's suggested release.
Use workflow prompts, resources, MCP Apps interactive tables, and stdio or authenticated HTTP modes.
Provides access to Cisco Support APIs including Bug Search, Case Management, End-of-Life information, PSIRT security vulnerability data, Product information, and Software recommendations through 33 tools across 6 different Cisco APIs.
Offers alternative endpoint compatibility for N8N integration, allowing the MCP server to be used with N8N automation workflows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-cisco-support search for bugs affecting Cisco Catalyst 9300 switches"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cisco Support MCP Server
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://resourcesMCP 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 usenpm (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
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).
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.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 details by ID (up to 5) |
| Bugs by keyword, product ID, product series or product name; releases affected or fixed; several severities in one call |
| 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 |
| Security advisory by advisory ID, CVE or bug ID |
| Advisories affecting an OS release ( |
| End-of-sale / end-of-support by product IDs, serials, software releases or announcement dates |
| Per serial number: contract coverage and warranty, product details and EoX |
| Product name, series, category, support page; optional MDF names |
| Cisco-suggested, latest, or compatible releases for a product |
| TAC cases by number ( |
| TAC cases by contract or user ID |
| 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 |
| Go/no-go for a software upgrade ( |
| Open bugs (worst first) and advisories for a product or release, e.g. before a change window |
| Match a symptom to known bugs, workarounds and fixed releases |
| Advisories affecting a release or product, with fix releases |
| End-of-life dates, migration products and contract coverage |
| 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 |
|
|
|
|
|
|
|
|
| 20 most recent advisories |
| 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/mcpEndpoint | Method | Notes |
| POST | Streamable HTTP, stateless; |
| 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:latestThe image starts in HTTP mode on 0.0.0.0:3000. Tags: latest, vX.Y.Z. More: Docker Deployment.
Configuration
Variable | Default | Purpose |
| (required) | Cisco API Console app credentials |
| random, printed once | Bearer token for HTTP mode |
|
| HTTP listen address ( |
| localhost only | Extra browser origins allowed to call |
|
| HTTP requests per minute per client (bearer token, or IP without auth); |
|
|
|
|
| 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-supportOr 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.mdThe 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:
Links
License
MIT, see LICENSE.
Available Tools
12 toolsassess_upgradeAssess a Cisco software upgradeARead-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 IDARead-only
Get Cisco bug (CDETS) details by ID, e.g. CSCwh87343. Up to 5 IDs.
Inputs: bug_ids (required), response_format.
bug_searchSearch Cisco bugsARead-only
Search Cisco bugs by exactly one of keyword, product_id, product_series or product_name. With releases, returns bugs affecting (or fixed in) those releases. Pass several severities to search them in one call.
Inputs: page, status, keyword, os_type, +9 more.
case_getGet Cisco TAC casesARead-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.
case_searchSearch Cisco TAC casesARead-only
Find Cisco TAC cases by exactly one of contract_ids or user_ids. Cisco returns at most 90 days per search.
Inputs: page, sort_by, user_ids, status_flag, +4 more.
device_lookupLook up Cisco devices by serial numberARead-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 datesARead-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 informationARead-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 advisoryARead-only
Get Cisco PSIRT security advisories by exactly one of advisory_id, cve or bug_id.
Inputs: cve, bug_id, advisory_id, response_format.
psirt_searchSearch Cisco security advisoriesARead-only
Find Cisco security advisories. Use os_type + version to answer "is this software version vulnerable?" (advisories affecting that release, with first fixed releases; add severity to keep only e.g. critical). Other modes: product, severity, year, latest, or a first-published date range.
Inputs: page, year, latest, os_type, +7 more.
rma_getGet Cisco RMAsARead-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 recommendationsBRead-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
Scored across 12 tools
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.
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.
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.
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
Related MCP Connectors
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
MCP server for the Vulners.com API
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
Related MCP Servers
- AlicenseCqualityFmaintenanceA TypeScript-based MCP server that provides integration with the Qase test management platform, allowing you to manage projects, test cases, runs, results, plans, suites, and shared steps.2612MIT
- AlicenseNot gradedqualityDmaintenanceA 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
- -licenseNot gradedqualityNot gradedmaintenanceA 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-
- AlicenseAqualityNot gradedmaintenanceA 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.429 npm-