Cisco Support APIs

Cisco Support MCP Server

A production-ready TypeScript MCP (Model Context Protocol) server for Cisco Support APIs with comprehensive security and dual transport support. This extensible server provides access to multiple Cisco Support APIs including Bug Search, Case Management, and End-of-Life information.

🚀 Current Features

• Multi-API Support: 8 Cisco Support APIs fully implemented (46 total tools)
• OAuth 2.1 Server: ✨ Production-grade authentication with fine-grained scope-based access control
• ElicitationRequest Support: Dynamic user interaction for gathering missing parameters
• Triple Auth Modes: stdio (no auth), Bearer token (simple), OAuth 2.1 (production)
• Configurable API Access: Enable only the Cisco Support APIs you have access to
• Specialized Prompts: 9 workflow prompts for guided Cisco support scenarios
• Dual Transport: stdio (local MCP clients) and HTTP (remote server with auth)
• OAuth2 Authentication: Automatic token management with Cisco API
• Real-time Updates: Server-Sent Events for HTTP mode
• TypeScript: Full type safety and MCP SDK integration
• Production Security: Helmet, CORS, input validation, PKCE, scope validation
• Docker Support: Containerized deployment with OAuth config volume mounts
• Comprehensive Logging: Structured logging with timestamps

📊 Supported Cisco APIs

The server supports the following Cisco Support APIs (configurable via SUPPORT_API environment variable):

API	Status	Tools	Description
Enhanced Analysis (enhanced_analysis)	⭐ RECOMMENDED	6 tools	Advanced analysis tools for comprehensive product assessment
Bug (bug)	✅ Complete	14 tools	Bug Search, Details, Product-specific searches + Enhanced tools
Case (case)	✅ Complete	4 tools	Support case management and operations
EoX (eox)	✅ Complete	4 tools	End of Life/Sale information and lifecycle planning
PSIRT (psirt)	✅ Complete	8 tools	Product Security Incident Response Team vulnerability data
Product (product)	✅ Complete	3 tools	Product details, specifications, and technical information
Software (software)	✅ Complete	6 tools	Software suggestions, releases, and upgrade recommendations
Serial (serial)	✅ Complete	3 tools	Serial number to coverage, warranty, and product information
RMA (rma)	✅ Complete	3 tools	Return Merchandise Authorization tracking and management
Smart Bonding (smart_bonding)	⚠️ EXPERIMENTAL	8 tools	Complete ticket lifecycle management and TSP codes (UNTESTED - requires special credentials)

Implementation Status: 8/8 Core APIs complete (100%) with 46 total tools + 1 experimental API (8 tools)

Configuration Examples:

• SUPPORT_API=enhanced_analysis - Enhanced analysis tools only (6 tools) ← RECOMMENDED for most users
• SUPPORT_API=bug - All Bug API tools including enhanced analysis (14 tools)
• SUPPORT_API=bug,case,eox,psirt - Core support APIs (28 tools)
• SUPPORT_API=bug,case,eox,psirt,product,software - All implemented APIs (39 tools)
• SUPPORT_API=all - All available APIs (includes 2 placeholder APIs)

Quick Start

NPX Installation (Recommended)

Start in stdio mode for Claude Desktop:

npx mcp-cisco-support

Start HTTP server with authentication:

npx mcp-cisco-support --http
# Token displayed in console for authentication

Generate Bearer token for HTTP mode:

npx mcp-cisco-support --generate-token

Get help and see all options:

npx mcp-cisco-support --help

Environment Setup

1. Generate authentication token (for HTTP mode):

   npx mcp-cisco-support --generate-token
   export MCP_BEARER_TOKEN=<generated_token>
   

2. Set Cisco API credentials:

   export CISCO_CLIENT_ID=your_client_id_here
   export CISCO_CLIENT_SECRET=your_client_secret_here
   export SUPPORT_API=bug,case,eox,psirt,product,software  # All implemented APIs (recommended)
   

3. Start the server:

   # For Claude Desktop (stdio mode)
   npx mcp-cisco-support
   
   # For HTTP access (with authentication)
   npx mcp-cisco-support --http
   

Local Development

git clone https://github.com/sieteunoseis/mcp-cisco-support.git
cd mcp-cisco-support
npm install
npm run build
npm start

Claude Desktop Integration

Prerequisites

1. Get Cisco API Credentials:

   • Visit Cisco API Console
   • Create an application and get your Client ID and Secret
   • Ensure the application has access to the Bug API

2. Install Claude Desktop:

   • Download from Claude.ai
   • Make sure you're using a recent version that supports MCP

Step-by-Step Setup

1. Locate Claude Desktop Config File:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Create or Edit the Config File:

   {
     "mcpServers": {
       "cisco-support": {
         "command": "npx",
         "args": ["-y", "mcp-cisco-support"],
         "env": {
           "CISCO_CLIENT_ID": "your_client_id_here",
           "CISCO_CLIENT_SECRET": "your_client_secret_here",
           "SUPPORT_API": "bug,product"
         }
       }
     }
   }
   

   Note: The -y flag automatically accepts package installation, which is required for Claude Desktop since it runs in the background without user interaction.

   Optional Environment Variables:

   Configure which APIs to enable with SUPPORT_API:

   • "enhanced_analysis" - Enhanced analysis tools only (recommended for most users)
   • "bug" - Bug API only (default)
   • "bug,product" - Bug + Product APIs (enables product autocomplete)
   • "all" - All available APIs
   • "bug,case,eox" - Multiple specific APIs

   Product Autocomplete (optional, requires SUPPORT_API to include product):

   "env": {
     "CISCO_CLIENT_ID": "your_client_id_here",
     "CISCO_CLIENT_SECRET": "your_client_secret_here",
     "SUPPORT_API": "bug,product",
     "CISCO_WEB_COOKIE": "JSESSIONID=...; OptanonConsent=..."
   }
   

   See the Product Autocomplete section for setup instructions.

3. Replace Your Credentials:

   • Replace your_client_id_here with your actual Cisco Client ID
   • Replace your_client_secret_here with your actual Cisco Client Secret

4. Restart Claude Desktop:

   • Close Claude Desktop completely
   • Reopen the application
   • The MCP server will be automatically loaded

Verification

After setup, you should be able to:

1. Ask Claude about Cisco bugs:

   "Search for bugs related to memory leaks in Cisco switches"
   

2. Get specific bug details:

   "Get details for Cisco bug CSCab12345"
   

3. Search by product:

   "Find bugs affecting Cisco Catalyst 3560 switches"
   

Example Usage in Claude Desktop

Once configured, you can ask Claude questions like:

• Basic Bug Search:

  • "Search for recent bugs related to 'crash' in Cisco products"
  • "Find open bugs with severity 1 or 2"
  • "Show me bugs modified in the last 30 days"

• Product-Specific Searches:

  • "Find bugs for product ID C9200-24P"
  • "Search for bugs in Cisco Catalyst 9200 Series affecting release 17.5.1"
  • "Show bugs fixed in software release 17.5.2"

• Bug Details:

  • "Get full details for bug CSCab12345"
  • "Show me information about bugs CSCab12345,CSCcd67890"

• Advanced Filtering:

  • "Find resolved bugs with severity 3 modified after 2023-01-01"
  • "Search for bugs in 'Cisco ASR 9000 Series' sorted by severity"
  • "Can you show me all the cisco bugs in the last 30 days for the product Cisco Unified Communications Manager (CallManager)?" (uses keyword search)
  • "Find bugs for Cisco Unified Communications Manager affecting releases 14.0 and 15.0" (uses product series search)

Claude will use the appropriate MCP tools to fetch real-time data from Cisco's Bug API and provide comprehensive responses with the latest information.

MCP Prompts

The server includes 10+ specialized prompts for guided Cisco support workflows:

• 🔍 cisco-high-severity-search - Search high-severity bugs by product or serial number
• 🚨 cisco-incident-investigation - Investigate symptoms and errors
• 🔄 cisco-upgrade-planning - Research issues before upgrades
• 🔧 cisco-maintenance-prep - Prepare for maintenance windows
• 🔒 cisco-security-advisory - Research security vulnerabilities
• ⚠️ cisco-known-issues - Check for software release issues
• 📋 cisco-case-investigation - Investigate support cas

---

README truncated. View full README on GitHub.