spranab/saga-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
Your agent loses the plan between sessions, so saga-mcp gives it a SQLite-backed tracker for projects, epics, tasks, subtasks, dependencies, and notes: 33 MCP tools, an activity log, and a one-call...
概要
Your coding agent loses the plan between sessions. You come back tomorrow and it has no idea which of the five things you agreed on are done, which one is blocked on which, or why you rejected the second approach — because the plan lived in the context window, or in a TODO.md nobody updates. saga-mcp gives the agent a real tracker instead: a SQLite file in your project holding projects, epics, tasks, subtasks, dependencies, comments, notes and decisions, exposed as 33 MCP tools. The agent writes to it as it works and reads the dashboard when it comes back. No accounts, no external service, no network calls — the database is a file you own. Claude Code — add to your project's .mcp.json: Restart the client. DB_PATH is the only setting; the file and schema are created on first use. "Set up tracking for the e-commerce API and plan out auth." Tasks 2 and 3 come back — their dependencies aren't done. Finish task 1 and task 2 unblocks itself.
README
以下は原文 README の抜粋です。原文を見る。
saga-mcp
Your coding agent loses the plan between sessions. You come back tomorrow and it has no idea which
of the five things you agreed on are done, which one is blocked on which, or why you rejected the
second approach — because the plan lived in the context window, or in a TODO.md nobody updates.
saga-mcp gives the agent a real tracker instead: a SQLite file in your project holding projects, epics, tasks, subtasks, dependencies, comments, notes and decisions, exposed as 41 MCP tools. The agent writes to it as it works and reads it back when it returns. No accounts, no external service, no network calls — the database is a file you own.
Install
Add saga-mcp to your MCP client. The same block works for Claude Code (.mcp.json in your
project), Claude Desktop (claude_desktop_config.json), and any other MCP client:
{
"mcpServers": {
"saga": {
"command": "npx",
"args": ["-y", "saga-mcp"],
"env": { "DB_PATH": "/absolute/path/to/your/project/.tracker.db" }
}
}
}
Restart the client. DB_PATH is the only required setting; the file and its schema are created on
first use. Prefer a global install? npm install -g saga-mcp, then use saga-mcp as the command
instead of npx.
Tested on Node 20, 22 and 24, on Linux, macOS and Windows.
Settings
| Variable | Required | Description |
|---|---|---|
DB_PATH |
Yes | Path to the .tracker.db SQLite file. Created on first use. |
SAGA_PROJECT |
No | Scope every tool to one project, by id or name. Set this per repo when several repos share one database. |
SAGA_DESCRIPTION_LOCK |
No | on_progress locks a task’s description the moment work starts on it. Off by default. See keeping agents on the rails. |
SAGA_TOOLS |
No | full (default) lists all 41 tools. core lists only the 13 an ordinary tracking session needs, saving ~4,300 tokens per session. See token cost. |
No API keys, no accounts, no external services.
Your first session
You: “Set up tracking for the e-commerce API and plan out auth.”
tracker_init({ project_name: "E-Commerce API" })
epic_create({ project_id: 1, name: "Authentication", priority: "high" })
task_create({ epic_id: 1, title: "Design auth schema", priority: "critical" })
task_create({ epic_id: 1, title: "Implement JWT auth", depends_on: [1] })
task_create({ epic_id: 1, title: "Add OAuth2 Google login", depends_on: [2] })
インストール
npx -y saga-mcp設定
{
"mcpServers": {
"saga": {
"command": "npx",
"args": ["-y", "saga-mcp"],
"env": { "DB_PATH": "/absolute/path/to/your/project/.tracker.db" }
}
}
}