You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dashboard immediately shows: 40% done, 1 blocked task in Auth, Product Catalog hasn't started. The LLM can now prioritize unblocking the rate limiting task or starting on the catalog.
185
+
186
+
### Example 3: Recording a decision and marking tasks done
187
+
188
+
**User prompt:** "We decided to use Redis for caching. Mark the caching research tasks as done."
189
+
190
+
**Tool calls:**
191
+
```
192
+
note_save({
193
+
title: "Decision: Use Redis for caching",
194
+
content: "After evaluating Redis vs Memcached vs in-memory, decided on Redis.\n\nReasons:\n- Built-in persistence\n- Pub/sub for cache invalidation\n- Better data structure support\n\nTrade-offs: Extra infrastructure, but managed Redis on AWS is acceptable.",
**Expected output:** Decision note created with ID, linked to the epic. Tasks 8 and 9 marked as done. Activity log records both the note creation and the status changes with "status: todo -> done" entries.
120
204
121
205
## How It Works
122
206
@@ -163,11 +247,18 @@ Every create, update, and delete is automatically recorded:
163
247
}
164
248
```
165
249
166
-
## Environment Variables
250
+
## Privacy Policy
167
251
168
-
| Variable | Required | Description |
169
-
|----------|----------|-------------|
170
-
|`DB_PATH`| Yes | Absolute path to the `.tracker.db` file |
252
+
saga-mcp is a fully local, offline tool. It does **not**:
253
+
254
+
- Collect any user data
255
+
- Send any data to external servers
256
+
- Require internet access after installation
257
+
- Use analytics, telemetry, or tracking of any kind
258
+
259
+
All data is stored exclusively in the local SQLite file specified by `DB_PATH`. You own your data completely. Uninstalling saga-mcp and deleting the `.tracker.db` file removes all traces.
260
+
261
+
For questions about privacy, open an issue at https://github.com/spranab/saga-mcp/issues.
"display_name": "Saga — Project Tracker for AI Agents",
5
+
"version": "1.1.0",
6
+
"description": "A Jira-like project tracker MCP server for AI agents. SQLite-backed, per-project scoped, with full hierarchy and activity logging — so LLMs never lose track.",
7
+
"long_description": "Saga gives your AI assistant a structured SQLite database to track projects, epics, tasks, subtasks, notes, and decisions across sessions. No more scattered markdown files — one `tracker_dashboard` call gives full project context to resume work.\n\n**Key features:**\n- Full hierarchy: Projects > Epics > Tasks > Subtasks\n- SQLite: Self-contained `.tracker.db` file per project — zero setup\n- Activity log: Every mutation is automatically tracked\n- Dashboard: One tool call gives full project overview\n- Notes system: Decisions, context, meeting notes, blockers\n- Batch operations: Create multiple subtasks or update multiple tasks in one call\n- 22 focused tools with safety annotations",
Copy file name to clipboardExpand all lines: package.json
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
{
2
2
"name": "saga-mcp",
3
-
"version": "1.1.0",
3
+
"version": "1.2.0",
4
4
"description": "A Jira-like project tracker MCP server for AI agents. SQLite-backed, per-project scoped, with full hierarchy (Projects > Epics > Tasks > Subtasks), activity logging, and a dashboard — so LLMs never lose track.",
0 commit comments