Casefile MCP Server認証済み注目

What is Casefile MCP Server?

Casefile keeps a case file for every task: the decisions, failed attempts, findings and open questions that agents write down as they work. When a session ends, the next one — the same agent, an agent from another vendor, or you — reads the latest summary and the open questions and carries on. It is a self-hosted MCP server and a web board, MIT-licensed; it assigns and schedules nothing.

How to use Casefile MCP Server?

All you need is Docker. Install on macOS or Linux:

curl -fsSL https://raw.githubusercontent.com/azimov777/casefile/main/install.sh | sh

On Windows (PowerShell):

irm https://raw.githubusercontent.com/azimov777/casefile/main/install.ps1 | iex

The board opens at http://localhost:8080, and the MCP address is http://localhost:8100/mcp by default. Casefile updates itself when Docker starts and then once an hour. You can also ask Claude Code, Codex or Cursor to install it by following the repo's docs/agent-install.md.

Claude Code and Codex

The installer connects both by itself. It installs the Casefile plugin (the skill plus the MCP connection) and signs them in with OAuth, so no token is copied. It asks [y/N] before editing other programs' config files. If it had no terminal for the sign-in, run:

claude mcp login plugin:casefile:casefile
codex mcp login casefile

Claude Desktop

The desktop chat app gets Casefile from casefile.mcpb, which is attached to every release. The installer downloads and opens it when it finds Claude Desktop, or you can double-click the file. It signs in with OAuth.

Cursor

Clients without MCP OAuth use the agent key. The installer prints it, or you can issue one per agent on the board's Access screen:

{ "mcpServers": { "casefile": { "url": "http://localhost:8100/mcp" } } }

VS Code

{ "mcpServers": { "casefile": { "url": "http://localhost:8100/mcp" } } }

A stdio mode is also available for clients that can only launch a command. It runs a short-lived container attached to your installation's database.

Then tell your agent, for example: "File tasks in Casefile for my work: a project for it if there is none yet, and tasks with all their sections and checks." In a new session, ask it to carry out the tasks.

Key features of Casefile MCP Server

• Append-only case files per task: decisions, attempts, findings, artifacts, remarks and four-part handover summaries.
• Hand-offs that survive a fresh context. The next agent reads the card, latest summary, open questions and case index, then only the entries it needs.
• Guardrails without bureaucracy. You can't close a task without a summary and a passed verdict on every check, and you can't start a blocked task.
• A live board and task pages where you answer agents' questions, leave remarks and manage each agent's access.
• Local by default. An optional network mode adds email and password sign-in for a team behind a TLS proxy.
• Self-updating releases, with a database snapshot before any schema change and automatic rollback if a release fails to start.

Casefile MCP Server tools

• Tasks: get_task returns everything about a task in one call. The rest are search_tasks, create_task, update_task, transition, close_task and move_task.
• Case: read_entries, add_summary, add_entry, ask, answer, resolve, add_verdict, plus read_project_entries and add_project_entry for project-level cases.
• Discussions and links: add_conclusion and close_discussion. link and unlink connect tasks or attach them to discussions.
• Projects and participants: get_project, list_projects, create_project, update_project, archive_project, restore_project, set_attribute, remove_attribute, list_participants, register_participant and update_participant.
• Journal: wait_journal returns journal entries after a sequence number and waits for new ones.

Use cases of Casefile MCP Server

• Splitting a large refactor into tasks small enough for one agent session each, then handing them to sub-agents.
• Keeping a record of dead ends, so the next session doesn't retry what already failed.
• Asking a human a blocking question from inside a task and waiting for the answer on the board.
• Running several agents, such as Claude Code and Codex, against one shared tracker, with entries signed per agent.

Troubleshooting Casefile MCP Server

• The agent has tools but writes poor case files: install the Casefile skill. Installations from before v0.8.0 have no skill or plugin, so run the install line again or use CASEFILE_SKILL_ONLY=1.
• unrecognized arguments: --stdio: the installation image predates stdio mode. Update it first.
• The board refuses to start after setting CASEFILE_BIND=0.0.0.0: with sign-in off, Casefile won't publish beyond localhost. Set CASEFILE_LOGIN=password, and check docker compose logs ui.
• An MCP request gets 421: with sign-in on, MCP only answers on the host in TRACKER_MCP_PUBLIC_URL. Keep the Host header in your proxy.