# Reported issues for saga-mcp

Pod holds 13 of 13 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [saga-mcp](/mcp/saga-mcp).

## Most discussed

### [Question] Web ui for observability

Hello! Thanks for sharing your work.

Any plans for a web UI to make task observability available to users?

[Read the thread](https://github.com/spranab/saga-mcp/issues/15) · 2026-08-27 · open · external user · 6 comments

### [Submission] saga-mcp — Anthropic MCP Directory Review

Hi @spranab,

Thank you for submitting **saga-mcp** to the Anthropic MCP Directory. We've completed our review and have a few items that need to be addressed before we can proceed.

## Required

1. **Add LICENSE file** — Both `manifest.json` and `package.json` declare MIT, but no `LICENSE` file exists in the repository.

2. **Add icon.png** — A 512x512 PNG icon is needed for directory presentation. Place it in the repository root.

3. **Resubmit bundle from latest version** — The submitted bundl

[Read the thread](https://github.com/spranab/saga-mcp/issues/11) · 2026-02-26 · closed · external user · 6 comments

### [Idea] Reduce context pressure with mcp-fusion — group saga's 23 tools into one

Hi 👋

First off, great work on saga-mcp. The structured SQLite-backed hierarchy with full activity logging is exactly the kind of persistent memory layer AI agents need.

I wanted to share a framework that might be worth exploring as saga-mcp grows: **[mcp-fusion](https://github.com/vinkius-labs/mcp-fusion)**.

## The problem it addresses

Saga currently exposes 23 individual tools (`project_create`, `project_update`, `epic_create`, `task_batch_update`, etc.). Each tool definition burns tokens i

[Read the thread](https://github.com/spranab/saga-mcp/issues/3) · 2026-02-22 · closed · external user · 4 comments

### MCP Directory Review — Items to Address

## MCP Directory Review

Hi! We're reviewing saga-mcp for inclusion in the Anthropic MCP Directory. During our review, we identified a few items that need to be addressed before we can publish.

### 1. Missing LICENSE file

The manifest declares `"license": "MIT"` but the repository has no LICENSE file. Please add an MIT LICENSE file to the root of the repo.

### 2. Missing icon.png

An `icon.png` is required for display in the MCP Directory listing. Please add a square icon (recommended 512x512

[Read the thread](https://github.com/spranab/saga-mcp/issues/12) · 2026-02-26 · closed · external user · 1 comment

### Add source file linking to tasks

## Problem

Tasks describe what to do, but there's no structured way to associate them with specific source files, line ranges, or commits. When an AI agent picks up a task, it has to rediscover which files are relevant.

## Current State

There's a `source_ref` field on tasks but it's a single reference. For real development work, a task often touches multiple files.

## Proposed Solution

Extend `source_ref` to support multiple file references:

### API Changes

- `task_create` / `task_update`

[Read the thread](https://github.com/spranab/saga-mcp/issues/6) · 2026-02-23 · closed · 1 comment

### Add priority-based task ordering in lists

## Problem

`task_list` returns tasks in creation order. For AI agents deciding "what should I work on next?", they need tasks ordered by priority, dependencies, and status.

## Proposed Solution

Add a `sort_by` parameter to `task_list`:

### API Changes

```
task_list(epic_id, sort_by="priority")    // critical first
task_list(epic_id, sort_by="suggested")   // smart ordering
task_list(epic_id, sort_by="due_date")    // deadline first
```

### Smart Ordering ("suggested")

Score each task by:

[Read the thread](https://github.com/spranab/saga-mcp/issues/10) · 2026-02-23 · closed · 0 comments

### Add smart rollup / summary generation for dashboard

## Problem

As projects grow, `tracker_dashboard` returns a lot of raw data. The AI agent has to parse and interpret it. For large projects, this eats context window.

## Proposed Solution

Add a `summary` field to the dashboard response — a pre-computed natural language summary of project state.

### Implementation

Generate a concise summary from the structured data:

```
"AIDB: 29 tasks across 5 epics. 0% complete.
Active: Whitepaper epic (in_progress, 0/5 tasks done).
Next up: V0 — Core Memo

[Read the thread](https://github.com/spranab/saga-mcp/issues/9) · 2026-02-23 · closed · 0 comments

### Add task templates for common workflows

## Problem

AI agents often create similar task structures for common workflows (e.g., "implement a feature" always has design → implement → test → document). This is repetitive.

## Proposed Solution

Add a template system that expands into pre-defined task sets.

### API

- `template_create(name, tasks[])` — save a reusable template
- `template_apply(template_name, epic_id, variables)` — instantiate tasks from template
- `template_list()` — show available templates

### Example

```json
{
  "n

[Read the thread](https://github.com/spranab/saga-mcp/issues/8) · 2026-02-23 · closed · 0 comments

## Most recent

### Add time tracking with automatic duration logging

## Problem

Tasks have `estimated_hours` and `actual_hours` fields, but there's no automatic tracking. AI agents mark tasks `in_progress` and `done` but never record how long they actually took.

## Proposed Solution

Automatically calculate duration from status transitions in the activity log.

### Implementation

When a task transitions:
- `todo` → `in_progress`: record start timestamp
- `in_progress` → `done`: calculate elapsed time, write to `actual_hours`
- `in_progress` → `blocked` → `in_p

[Read the thread](https://github.com/spranab/saga-mcp/issues/7) · 2026-02-23 · closed · 0 comments

### Add threaded discussions on tasks

## Problem

Notes are standalone entities. There's no way to have a threaded conversation about a specific task — e.g., "tried approach X, didn't work because Y, switching to Z."

## Proposed Solution

Add a `comment` entity type tied to tasks (and optionally epics).

### API

- `comment_create(task_id, content)` — add a comment to a task
- `comment_list(task_id)` — list all comments on a task, chronological
- Include comments in `task_get` response

### Schema

```sql
CREATE TABLE comments (
  

[Read the thread](https://github.com/spranab/saga-mcp/issues/5) · 2026-02-23 · closed · 0 comments

### Add task dependency tracking

## Problem

There's no way to express that one task depends on another. Sequencing lives in the user's head (or the AI agent's context), not in the tracker.

## Proposed Solution

Add a `depends_on` field to tasks — an array of task IDs that must be `done` before this task can start.

### API Changes

- `task_create` and `task_update`: accept optional `depends_on: [task_id, ...]`
- `task_list`: return `blocked_by` showing which dependencies are incomplete
- Auto-set task status to `blocked` when

[Read the thread](https://github.com/spranab/saga-mcp/issues/4) · 2026-02-23 · closed · 0 comments

### Add JSON import/export for project data

## Feature Request

Add tools to export and import project data as JSON, enabling backup, migration, and seeding from existing sources.

### Context
From community feedback — users want to seed a tracker from existing repo milestones/labels, or sync data to GitHub Issues/Jira later.

### Possible approach
- `tracker_export` — Dump full project (or all projects) as a single JSON object with all epics, tasks, subtasks, notes
- `tracker_import` — Load a JSON file to create/merge project data
- Keep

[Read the thread](https://github.com/spranab/saga-mcp/issues/2) · 2026-02-22 · closed · 0 comments

### Add source_ref field to tasks for linking to code

## Feature Request

Add a dedicated `source_ref` field to tasks for linking to specific code locations (repo, file path, line range, commit).

### Context
From community feedback — tasks should be able to point at the exact place work happened, beyond what's possible with the free-form `description` field.

### Possible approach
- Add `source_ref` TEXT column to tasks table (JSON object with `repo`, `path`, `line_range`, `commit`)
- Include in `task_get` and `task_list` output
- Allow setting vi

[Read the thread](https://github.com/spranab/saga-mcp/issues/1) · 2026-02-22 · closed · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/spranab/saga-mcp/issues).