MCP server for Cisco Support APIs including Bug Search and future tools
MCP server for Cisco Support APIs including Bug Search and future tools. The mcp cisco support mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
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.
Installation on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
Product — Specific Searches**:API — StatusPrerequisites — 1. Get Cisco API Credentials: - Visit Cisco API Console - Create an application and get your Client ID andVerification — 1. Ask Claude about Cisco bugs: "Search for bugs related to memory leaks in Cisco switches"Configuration — 1. Obtain Credentials - Contact your Cisco Account Manager to request Smart Bonding API accessTroubleshooting — The Troubleshooting tool exposed by this serverDebugging — 1. Test the server manually: bash npx mcp-cisco-support This should start the server in stdio mode without errorsYou will need 8 environment variables: CISCO_CLIENT_ID, CISCO_CLIENT_SECRET, SUPPORT_API, CISCO_WEB_COOKIE, SMART_BONDING_CLIENT_ID, SMART_BONDING_CLIENT_SECRET, SMART_BONDING_ENV, MCP_BEARER_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Cisco Support's toolset — Product, API, Prerequisites and 4 more — is a fair guide to whether it matches your workflow. It is maintained by sieteunoseis; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Product | Specific Searches**: |
| API | Status |
| Prerequisites | 1. **Get Cisco API Credentials**: - Visit [Cisco API Console](https://apiconsole.cisco.com/) - Create an application and get your Client ID and Secret - Ensure the application has access to the Bug API |
| Verification | 1. **Ask Claude about Cisco bugs**: "Search for bugs related to memory leaks in Cisco switches" |
| Configuration | 1. **Obtain Credentials** - Contact your Cisco Account Manager to request Smart Bonding API access |
| Troubleshooting | The Troubleshooting tool exposed by this server. |
| Debugging | 1. **Test the server manually**: bash npx mcp-cisco-support This should start the server in stdio mode without errors. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CISCO_CLIENT_ID | Configuration value read at startup. | Optional |
| CISCO_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SUPPORT_API | Configuration value read at startup. | Optional |
| CISCO_WEB_COOKIE | Configuration value read at startup. | Optional |
| SMART_BONDING_CLIENT_ID | Configuration value read at startup. | Optional |
| SMART_BONDING_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SMART_BONDING_ENV | Configuration value read at startup. | Optional |
| MCP_BEARER_TOKEN | Credential the server authenticates with. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.