mcp-cisco-support

# Cisco API OAuth2 Configuration (Standard Support APIs) CISCO_CLIENT_ID=your_client_id_here CISCO_CLIENT_SECRET=your_client_secret_here # Product Autocomplete Configuration (Optional) # Required for cisco://products/autocomplete/* MCP resources # Extract from your browser after logging in to https://bst.cloudapps.cisco.com/ # Cookie typically valid for 24 hours - refresh daily for continued access # # How to get your cookie: # 1. Log in to https://bst.cloudapps.cisco.com/ # 2. Open browser DevTools (F12) # 3. Go to Application/Storage > Cookies # 4. Copy all cookies in format: JSESSIONID=...; OptanonConsent=...; ... # # Security: Never commit this cookie to git - treat it like a password # CISCO_WEB_COOKIE="JSESSIONID=...; OptanonConsent=...; ..." # ⚠️ EXPERIMENTAL: Smart Bonding API Configuration (UNTESTED) # Contact your Cisco Account Manager to obtain Smart Bonding API credentials # Uses different OAuth2 endpoint: https://cloudsso.cisco.com/as/token.oauth2 # SMART_BONDING_CLIENT_ID=your_smart_bonding_client_id # SMART_BONDING_CLIENT_SECRET=your_smart_bonding_client_secret # SMART_BONDING_ENV=production # or 'staging' for test environment # Server Configuration PORT=3000 NODE_ENV=development # API Support Configuration # Comma-separated list of APIs to enable: enhanced_analysis,bug,case,eox,psirt,product,software,serial,rma,smart_bonding # Use 'enhanced_analysis' for simplified deployment (recommended), 'all' for everything, or 'bug' for basic # Note: Users must have appropriate Cisco API access for each enabled API # # Examples: # SUPPORT_API=enhanced_analysis # Enhanced analysis tools only (6 tools) - RECOMMENDED # SUPPORT_API=bug # All Bug API tools (14 tools including enhanced) # SUPPORT_API=bug,case # Bug and Case APIs # SUPPORT_API=bug,case,eox,psirt # Core support APIs # SUPPORT_API=bug,case,eox,psirt,product,software,serial,rma # All implemented APIs (46 tools) # SUPPORT_API=smart_bonding # ⚠️ EXPERIMENTAL: Smart Bonding API only (UNTESTED) # SUPPORT_API=all # All available APIs (excludes smart_bonding) # # ✅ Currently implemented (8/8 APIs - 100% complete): # enhanced_analysis (6 tools), bug (14 tools), case (4 tools), eox (4 tools), psirt (8 tools), product (3 tools), software (6 tools), serial (3 tools), rma (3 tools) # ⚠️ EXPERIMENTAL/UNTESTED (1 API): # smart_bonding (8 tools) - Complete ticket lifecycle management - Requires special credentials from Cisco Account Manager SUPPORT_API=enhanced_analysis # Response Format Configuration # TOON Format is enabled by default for improved readability and structure # Set to 'true' to disable TOON format and return native JSON responses instead # DISABLE_TOON_FORMAT=false # HTTP Authentication Configuration (for --http mode only) # Authentication Type: 'bearer' (default) or 'oauth2.1' # - bearer: Simple bearer token authentication (recommended for most use cases) # - oauth2.1: Full OAuth 2.1 with PKCE (for advanced authorization scenarios) AUTH_TYPE=bearer # Bearer Token Authentication (when AUTH_TYPE=bearer) # Custom Bearer token for HTTP authentication (optional - generates random token if not set) # Generate a token with: npx mcp-cisco-support --generate-token # MCP_BEARER_TOKEN=your_custom_token_here # OAuth 2.1 Configuration (when AUTH_TYPE=oauth2.1) # Issuer URL for OAuth 2.1 server (defaults to http://localhost:PORT) # OAUTH2_ISSUER_URL=https://your-server.com # # Path to OAuth clients configuration file (defaults to config/oauth-clients.json) # OAUTH_CLIENTS_CONFIG=config/oauth-clients.json # # Path to OAuth secrets file - OPTIONAL (defaults to config/oauth-secrets.json) # Separates client secrets from main config for better security # OAUTH_SECRETS_CONFIG=config/oauth-secrets.json # SECURITY WARNING: Setting this to 'true' disables HTTP authentication entirely # Only use in development/testing environments behind secure networks # DANGEROUSLY_OMIT_AUTH=true