Cisco Support MCP Server

What it is

A TypeScript MCP server covering eight Cisco Support APIs, with 46 tools between them. Which of those tools exist is decided by the SUPPORT_API environment variable, so a deployment can expose bug search alone or the whole ecosystem. It handles the Cisco OAuth2 token exchange itself, and runs either as a local stdio server or as an HTTP server with bearer-token or OAuth 2.1 authentication in front of it.

What you get

• Bug search from several angles — keyword, product ID, product and release, affected or fixed product series and names — plus detail by bug ID — search_bugs_by_keyword, search_bugs_by_product_id, search_bugs_by_product_and_release, search_bugs_by_product_series_affected, search_bugs_by_product_series_fixed, search_bugs_by_product_name_affected, search_bugs_by_product_name_fixed, get_bug_details
• Search strategies for when the obvious query returns nothing: a strategy recommender, a progressive search, a multi-severity sweep, a comprehensive analysis and a product-name resolver — smart_search_strategy, progressive_bug_search, multi_severity_search, comprehensive_analysis, product_name_resolver
• PSIRT security advisories by ID, CVE, severity, bug ID, year, first-published date, or simply the latest — get_all_security_advisories, get_security_advisory_by_id, get_security_advisory_by_cve, get_security_advisories_by_severity, get_security_advisory_by_bug_id, get_latest_security_advisories, get_security_advisories_by_year, get_security_advisories_by_first_published
• End-of-life and end-of-sale by date, product ID, serial number or software release — get_eox_by_date, get_eox_by_product_id, get_eox_by_serial_number, get_eox_by_software_release
• Support cases summarised, detailed, and searched by contract or by user — get_case_summary, get_case_details, search_cases_by_contract, search_cases_by_user
• Product and serial lookups: product info by serial numbers or product IDs, and MDF information — get_product_info_by_serial_numbers, get_product_info_by_product_ids, get_product_mdf_info_by_product_ids
• Software suggestions, releases and compatibility by product ID or MDF ID — get_software_suggestions_by_product_ids, get_software_releases_by_product_ids, get_compatible_software_by_product_id, get_software_suggestions_by_mdf_ids, get_software_releases_by_mdf_ids, get_compatible_software_by_mdf_id
• Nine specialised workflow prompts for guided Cisco support scenarios

Requirements

Cisco API credentials from the Cisco API Console: CISCO_CLIENT_ID and CISCO_CLIENT_SECRET, with the application granted access to the APIs you intend to use. The OAuth2 token exchange with Cisco is handled for you. Run it with npx mcp-cisco-support for stdio, or npx mcp-cisco-support --http for the HTTP server with authentication; npx mcp-cisco-support --generate-token produces a bearer token you export as MCP_BEARER_TOKEN. SUPPORT_API is a comma-separated list of API names — enhanced_analysis alone is the README's recommendation for most users at 6 tools, bug,case,eox,psirt gives 28, and bug,case,eox,psirt,product,software gives 39. A Docker image is published at ghcr.io/sieteunoseis/mcp-cisco-support. The Smart Bonding API is marked experimental and untested, and needs special credentials.

Setup effort

One command plus credentials — npx -y mcp-cisco-support, then supply credentials

Tools you get

The project says 46; its docs name 33. SUPPORT_API decides which tools load: the README counts 6 for enhanced_analysis (its recommendation for most users), 14 for bug (the default), 28 for bug,case,eox,psirt and 39 for bug,case,eox,psirt,product,software.

Requires

• npx on PATH
• CISCO_CLIENT_ID in your environment
• CISCO_CLIENT_SECRET in your environment

Where it runs

The documented client runs the server on your machine.