The casemgr-mcp is a stdio-to-HTTP bridge for the CaseMgr MCP server, allowing MCP clients that support stdio transport to connect to CaseMgr's hosted endpoint.
From the registry: Shared workspace your AI agent writes to. 184 tools, persistent memory, semantic search.
$ npm install -g casemgr-mcpPlease install the `casemgr-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Get a CaseMgr API token** — Get an API token from casemgr.systems (https://casemgr.systems/tokens)
- **Install globally** — Install casemgr-mcp globally via npm Run: `npm install -g casemgr-mcp`
Canonical MCP server config (stdio transport):
- command: `casemgr-mcp`
- args: []
- required environment variables:
- `CASEMGR_API_TOKEN`: API token from casemgr.systems/tokens (example: `<your-casemgr-api-token>`)
- optional environment variables:
- `CASEMGR_URL`: MCP endpoint URL (for self-hosted instances) (example: `https://casemgr.systems/mcp`)
Note: Stdio-to-HTTP bridge for CaseMgr's hosted MCP server (184 tools for CMMN case management). Claude Code can skip the bridge and use https://casemgr.systems/mcp directly with Bearer auth.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CASEMGR_API_TOKENrequiredAPI token from casemgr.systems/tokensAtlassian Rovo MCP Server