Cisco Crosswork Workflow Manager MCP endpoint
Crosswork Workflow Manager 2.1 ships a first-party MCP endpoint as part of its northbound REST API. Cisco documents it in the CWM API reference as POST /mcp on the CWM base path /crosswork/cwm/v2, handling MCP over JSON-RPC 2.0. Because Crosswork is a customer-deployed product, the endpoint runs on the customer's own CWM host, not on a Cisco-operated URL — an agent can reach it over HTTPS, but only after the customer has deployed CWM and minted a JWT.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport http-jsonrpc
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.