Casemgr MCP Server

CMMN case management with 184 MCP tools for cases, tasks, workflows, billing, and AI agents.

Remote serverstreamable-http

What is the Casemgr MCP server?

CMMN case management with 184 MCP tools for cases, tasks, workflows, billing, and AI agents. That is what the casemgr mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

It creates notes when it finds things, plans tasks when work appears, and marks them done. You review and edit. Persistent memory + semantic search across a graph of notes, tasks, and files.

A shared, persistent workspace for you and your AI agent — 184 MCP tools across a graph of notes, tasks, files, calendar, and agent presence.

The tools it exposes

The server publishes 6 tools. What each one is for:

  • Multi — agent task queue** — dispatch, claim, and complete work items across multiple agents
  • Event — driven workflows** — CMMN stages with sentry-gated execution and auto-lifecycle management
  • Variable — Required
  • CASEMGR_API_TOKEN — Yes (stdio)
  • CASEMGR_URL — No
  • Smithery — Install directly via Smithery — one-click setup for Claude Code, Cursor, Codex, and more

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: CASEMGR_API_TOKEN, CASEMGR_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Casemgr's toolset — Multi, Event, Variable and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mstang; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Multiagent task queue** — dispatch, claim, and complete work items across multiple agents
Eventdriven workflows** — CMMN stages with sentry-gated execution and auto-lifecycle management
VariableRequired
CASEMGR_API_TOKENYes (stdio)
CASEMGR_URLNo
SmitheryInstall directly via [Smithery](https://smithery.ai/servers/mstang/casemgr) — one-click setup for Claude Code, Cursor, Codex, and more.

How to install the Casemgr MCP server

{
  "mcpServers": {
    "casemgr": {
      "command": "npx",
      "args": ["-y", "casemgr-mcp"],
      "env": {
        "CASEMGR_API_TOKEN": "your-value",
        "CASEMGR_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CASEMGR_API_TOKENCredential the server authenticates with.Yes
CASEMGR_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Casemgr to Multi.
  • Use Casemgr to Event.
  • Use Casemgr to Variable.

Frequently asked questions

It connects Casemgr to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Multi, Event, Variable, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Casemgr directly.