
Casemgr Mcp
io.github.mstangPublished by GitHub account mstangv1.0.1Updated Oct 24, 2026
Shared workspace your AI agent writes to. 184 tools, persistent memory, semantic search.
Overview
A stdio bridge to the CaseMgr workspace, letting an assistant write notes, plan and complete tasks, and search a persistent graph of notes, tasks and files.
- What you can do
- Create and edit notes, tasks, bookmarks, todos and files in a shared workspace
- Search everything either party wrote using natural-language semantic search
- Dispatch, claim and complete work items across multiple agents
- Run event-driven workflows and reusable case plan templates
- Upload, download and version files, and track time, expenses and invoices
- Organize cases into workspaces and link git worktrees across machines
- When to use it
- Useful when you want an assistant to keep durable working memory across sessions and to plan, track and finish tasks in a shared space you can review and edit, rather than losing context each session.
- Requirements
- Runs locally as an npm package (casemgr-mcp) over stdio, so Node.js is needed. Requires a CaseMgr account and the CASEMGR_API_TOKEN environment variable, obtained from the provider's token page. An optional CASEMGR_URL variable points at a self-hosted endpoint; network access to the CaseMgr service is required.
Installation
In SourceWeft
- Open Casemgr Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
casemgr-mcp
A shared workspace your AI agent actually writes to — 184 MCP tools.
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.
This package is the stdio-to-HTTP bridge for the CaseMgr MCP server — use it with any MCP client that supports stdio transport (Claude Desktop, Cursor, etc.). For Claude Code, see below — it supports HTTP natively and does not need this bridge.
Quick Start
Get an API token at casemgr.systems/tokens.
MCP Client Config
Claude Desktop / Cursor
Add to your MCP settings:
Claude Code (CLI)
Claude Code authenticates via OAuth automatically — no token needed. Just add the server URL:
If you prefer token auth, add "headers": { "Authorization": "Bearer your_token_here" }.
Smithery
Install directly via Smithery — one-click setup for Claude Code, Cursor, Codex, and more.
What is CaseMgr?
A shared, persistent workspace for you and your AI agent — 184 MCP tools across a graph of notes, tasks, files, calendar, and agent presence.
Your agent creates notes when it finds things. Plans tasks when there's work to do. Marks them done as it finishes. You review, edit, and add your own. Nothing is ephemeral — every session resumes exactly where the last one left off, and semantic search spans everything either of you ever wrote.
What's in the workspace:
- Persistent memory — every session resumes where the last one left off; nothing is ephemeral
- Bidirectional graph — agent and user both read and write notes, tasks, bookmarks, files, todos
- Semantic search — natural-language search across everything either of you ever wrote
- 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
- Reusable templates — case plan models with publish, version, and instantiate
- File management — upload, download, versioning, content-aware embeddings
- Workspaces & worktrees — organize cases, link git worktrees across machines
- Time tracking & billing — durations, expenses, invoices with LaTeX/PDF generation
Environment Variables
License
MIT
Source: README.md at commit 300949c
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.