Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port for HTTP mode | 3000 |
| NODE_ENV | No | Node environment (development/production) | development |
| SUPPORT_API | No | Enable specific Cisco Support APIs (comma-separated list) | bug |
| CISCO_CLIENT_ID | Yes | Your Cisco API Client ID for OAuth2 authentication | |
| MCP_BEARER_TOKEN | No | Custom Bearer token for HTTP authentication (HTTP mode only) | |
| CISCO_CLIENT_SECRET | Yes | Your Cisco API Client Secret for OAuth2 authentication | |
| DANGEROUSLY_OMIT_AUTH | No | Disables HTTP authentication entirely (development/testing only) |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cisco-high-severity-search | Search for high-severity bugs (severity 3 or higher) for specific products - handles API limitation requiring separate searches |
| cisco-incident-investigation | Investigate Cisco bugs related to specific incident symptoms and errors |
| cisco-upgrade-planning | Research known issues and bugs before upgrading Cisco software or hardware |
| cisco-maintenance-prep | Prepare for maintenance windows by identifying potential issues and bugs |
| cisco-security-advisory | Research security-related bugs and vulnerabilities for Cisco products |
| cisco-known-issues | Check for known issues in specific Cisco software releases or products |
| cisco-smart-search | Intelligent search strategy with automatic refinement and comprehensive analysis. Uses multiple search techniques and provides web search guidance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bug_details | Get details for up to 5 specific bug IDs |
| search_bugs_by_keyword | Search for bugs using keywords in descriptions and headlines. Use this when searching by general terms, symptoms, or when product-specific tools are not applicable. IMPORTANT: severity parameter returns ONLY that specific level. For "severity 3 or higher" searches, use multi_severity_search tool instead. |
| search_bugs_by_product_id | Search bugs by specific base product ID (e.g., C9200-24P). Use when you have an exact Cisco product ID. For general product searches by name, consider using keyword search instead. |
| search_bugs_by_product_and_release | Search bugs by specific product ID and software releases. CRITICAL: Use "software_releases" parameter with comma-separated values like "17.9.1,17.12.3" to search up to 75 versions in ONE API call. NEVER make multiple separate calls for different versions - the API supports multiple versions in a single request. Use this when you have an exact product ID and want to filter by specific software versions. For product series searches, use search_bugs_by_product_series_affected instead. |
| search_bugs_by_product_series_affected | Search bugs by product series and affected releases. This endpoint accepts full product series names like "Cisco 4000 Series Integrated Services Routers". IMPORTANT: Use Cisco API version format without leading zeros (17.9.6 not 17.09.06). |
| search_bugs_by_product_series_fixed | Search bugs by product series and fixed releases. This endpoint accepts full product series names like "Cisco 4000 Series Integrated Services Routers". IMPORTANT: Use Cisco API version format without leading zeros (17.9.6 not 17.09.06). |
| search_bugs_by_product_name_affected | Search bugs by full product name and affected releases. NOTE: Requires FULL descriptive product names (like "Cisco 4431 Integrated Services Router") not product IDs. Use search_bugs_by_product_id for product IDs like ISR4431. |
| search_bugs_by_product_name_fixed | Search bugs by full product name and fixed releases. NOTE: Requires FULL descriptive product names (like "Cisco 4431 Integrated Services Router") not product IDs. Use search_bugs_by_product_id for product IDs like ISR4431. |
| smart_search_strategy | Analyzes search queries and suggests optimal search approaches based on input patterns. Provides strategic guidance for finding bugs effectively. |
| progressive_bug_search | Automatically tries multiple search strategies, starting specific and broadening scope if needed. Handles version normalization and product ID variations. |
| multi_severity_search | RECOMMENDED for multi-severity searches: Automatically searches multiple severity levels and combines results. Use this when you need "severity 3 or higher", "high severity bugs", or any range of severities. Handles the API limitation that requires separate calls for each severity level. |
| comprehensive_analysis | BEST FOR DETAILED ANALYSIS: Combines bug database search with web search guidance for EoL information. Provides complete product analysis including known issues, lifecycle status, and actionable recommendations. Ideal for failover issues, configuration problems, and product reliability concerns. |
| compare_software_versions | Compare bugs, CVEs, and recommendations between two software versions on the same product. Analyzes differences in known issues, security vulnerabilities, and provides upgrade recommendations. |
| product_name_resolver | Resolves product IDs to full product names and provides web search strategies. Helps convert technical product codes to searchable terms. |