Cisco Support

You can run the Cisco Support MCP Server locally to access multiple Cisco Support APIs through a single MCP interface. It offers stdio and HTTP transport options, production-grade authentication, and real-time updates, making it easier to build tooling, automation, or conversational assistants that work with Cisco bug tracking, case management, and lifecycle data.

How to use

Start by running the MCP server in stdio mode to work locally with Claude Desktop or other MCP clients. You configure the server with your Cisco API credentials and enable the specific APIs you have access to. Once running, you can list available tools, call individual tools for searches and details, and use the interactive prompts to guide complex queries. If you need remote access, you can also run the server in HTTP mode with bearer token authentication to securely expose the MCP endpoint to other services.

How to install

Prerequisites you need before installing: Node.js 18 or newer and a modern shell. You will also need Cisco API credentials (Client ID and Client Secret) and, if you plan to use product autocomplete, a Cisco web cookie for product data access.

# 1) Ensure Node.js is installed (v18+)
node -v
npm -v

# 2) Install the MCP server locally (no global install required for stdio mode usage)
npx mcp-cisco-support

# Optional: start in HTTP mode with authentication
npx mcp-cisco-support --http

Configuration and environment

Configure which Cisco APIs to enable and provide your Cisco credentials. The server uses environment variables for sensitive information and API scope control.

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

Notes on authentication modes

The server supports production-grade OAuth 2.1 authentication for secure access control, as well as a simple stdio mode that does not require authentication for local development. In HTTP mode, you obtain a token and supply it with requests to access protected endpoints.

Starting and verifying the server

Start the server in stdio mode to begin using MCP locally. For remote HTTP access, start in HTTP mode and follow token-based authentication prompts.