Labsco
MCP SERVER

CaseMgr MCP

by mstang

A workspace your agent writes to and you edit — notes, tasks, files and calendar in one graph, with semantic search across everything either of you wrote.

Team Wikis & Documentation Platforms
Summary
Both sides write to the same records.

That is the design decision the rest follows from. An agent memory the human cannot edit drifts and cannot be corrected; a document the agent cannot write to goes stale. Here the notes, tasks and files are one graph with two authors, which is why the session-resume behaviour is useful rather than merely persistent. The cost is size — 184 tools is a lot of context, so this is a workspace server to run as your main one rather than one of six.

What it is

The stdio-to-HTTP bridge for CaseMgr, a shared persistent workspace for you and an AI agent. The premise is that nothing is ephemeral: the agent creates notes when it finds things, plans tasks when work appears, and marks them done; you review and edit the same records. Every session resumes where the last one stopped, and semantic search spans the whole history.

What you get
  • Persistent memory across sessions, so a conversation picks up from the record rather than from a summary you paste back in
  • A bidirectional graph both sides write to — notes, tasks, bookmarks, files, todos — rather than an agent scratchpad you cannot edit
  • Natural-language search across everything either of you ever wrote
  • A multi-agent task queue: work items dispatched, claimed and completed across several agents
  • Event-driven workflows as CMMN stages with sentry-gated execution, and reusable case plan models you publish, version and instantiate
  • File management with versioning and content-aware embeddings, workspaces and git worktrees linked across machines, and time tracking with expenses and invoices rendered to PDF
  • 184 MCP tools in total — a large surface, and worth knowing before enabling it alongside other servers
Requirements

A CaseMgr account. Claude Desktop, Cursor and other stdio clients need this bridge and an API token in `CASEMGR_API_TOKEN`, from casemgr.systems/tokens; install with `npm install -g casemgr-mcp` (package `casemgr-mcp`, 1.0.1). Claude Code does not need the bridge at all — it speaks HTTP natively and authenticates over OAuth, so you point it at the server URL and skip the token. `CASEMGR_URL` overrides the endpoint for a self-hosted instance.

Setup effort

One command plus a key — npm install -g casemgr-mcp, then supply credentials