io.github.spranab/saga-mcp
NPM · SAGA-MCP
Jira-like project tracker for AI agents with SQLite, full task hierarchy, and dashboard
Available components
Last scanned (5 hours ago)
Scores higher than 95% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 51 of 127 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to spranab/saga-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3494 tokens (~85/item across 41 items; 41 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −3
- Stability: pass → 0.80 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Package version: 1.5.5 → 1.19.0 functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 0
- Package version: 1.5.5 → 1.19.0 functional
- 23 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/saga-mcp@1.19.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | spranab/saga-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/spranab/saga-mcp/.github/workflows/publish.yml@refs/tags/v1.19.0 |
| Rekor log index | 3003750992 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8953e6477b02491a6ac2cbfaf4409bc7a270acb61cf2cec964e20ef137038c1280806f3cbc8511c09e1889dc02f6288cf7c66b89ea2eb28ef13f4eca7 |
Background: How many MCP packages publish verified provenance →
Dependencies 127 packages
| Packages resolved | 127 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activity_log ~118
View the activity log showing what changed and when. Useful for understanding recent progress or reviewing what happened since the last session.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by action type |
| entity_id | integer | – | Filter by specific entity |
| entity_type | string | – | Filter by entity type |
| limit | integer | – | – |
| project_id | integer | – | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. |
| since | string | – | ISO 8601 datetime - show only activity after this time |
No output schema declared.
No examples provided.
comment_add ~62
Add a comment to a task. Comments create a chronological discussion thread — useful for leaving breadcrumbs across sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author name (optional) |
| content | string | yes | Comment text |
| task_id | integer | yes | Task ID to comment on |
No output schema declared.
No examples provided.
comment_delete ~99
Remove a comment (soft delete). The row is kept for the audit trail but hidden from comment_list and task_get. Use this to retract a comment that turned out to be wrong or stale. Reversible with comment_restore.
| Name | Type | Req | Description |
|---|---|---|---|
| deleted_by | string | – | Who removed it (optional) |
| id | integer | yes | Comment ID to remove |
| reason | string | – | Why the comment is being removed (recommended — it stays in the audit trail) |
No output schema declared.
No examples provided.
comment_list ~69
List comments on a task in chronological order. Comments removed with comment_delete are hidden by default; pass include_deleted to see them with their removal reason.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include comments that were removed (soft-deleted). Off by default. |
| task_id | integer | yes | Task ID |
No output schema declared.
No examples provided.
comment_restore ~28
Restore a comment previously removed with comment_delete.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Comment ID to restore |
No output schema declared.
No examples provided.
epic_archive ~75
Archive or unarchive an epic. Archived epics and their tasks drop out of listings, the dashboard and search unless include_archived is set. For putting finished work out of sight without cancelling it; nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true to archive, false to bring it back |
| id | integer | yes | – |
No output schema declared.
No examples provided.
epic_create ~106
Create an epic within a project. Epics group related tasks into a feature or workstream.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch to scope this epic to: "current" = active branch, omit/"" = branch-agnostic. |
| description | string | – | Epic description |
| name | string | yes | Epic name |
| priority | string | – | – |
| project_id | integer | yes | Parent project ID |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
epic_list ~110
List epics for a project with task counts and completion stats. Filter by status, priority or branch. Archived epics are hidden unless include_archived is set.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Git branch filter: "current" = active branch, "" = branch-agnostic only, omit = all. |
| include_archived | boolean | – | Include archived epics and their tasks. |
| priority | string | – | – |
| project_id | integer | yes | Project ID |
| status | string | – | – |
No output schema declared.
No examples provided.
epic_update ~126
Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete. Pass branch="current" to pin to the active branch, or empty string to clear.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch to scope this epic to: "current" = active branch, "" = clear. |
| description | string | – | – |
| id | integer | yes | Epic ID |
| name | string | – | – |
| priority | string | – | – |
| sort_order | integer | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
note_delete ~23
Delete a note by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Note ID |
No output schema declared.
No examples provided.
note_list ~92
List notes with optional filters. Returns notes sorted by most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| note_type | string | – | – |
| project_id | integer | – | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. |
| related_entity_id | integer | – | – |
| related_entity_type | string | – | – |
| tag | string | – | Filter by a single tag |
No output schema declared.
No examples provided.
note_save ~117
Create or update a note: decisions, context, progress, meetings, blockers, technical detail, releases. With id, updates; without, creates.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full note content (markdown supported) |
| id | integer | – | Note ID (omit to create new) |
| note_type | string | – | – |
| related_entity_id | integer | – | ID of the related entity |
| related_entity_type | string | – | Link note to an entity |
| tags | array | – | – |
| title | string | yes | Note title |
No output schema declared.
No examples provided.
note_search ~41
Search across note titles and content by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| note_type | string | – | – |
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
project_create ~61
Create a new project. Projects are the top-level container for all work.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Project description |
| name | string | yes | Project name |
| status | string | – | Project status |
| tags | array | – | Tags for categorization |
No output schema declared.
No examples provided.
project_list ~35
List all projects with epic/task counts and completion percentages. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by status |
No output schema declared.
No examples provided.
project_update ~69
Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | Project ID |
| name | string | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
subtask_create ~113
Create subtasks (checklist items) for a task. Pass titles as an array — one string per subtask — and each becomes its own record. New subtasks are appended after any that exist.
| Name | Type | Req | Description |
|---|---|---|---|
| depends_on | array | – | Siblings each new subtask waits on |
| task_id | integer | yes | Parent task |
| titles | array | yes | Subtask titles, one per array item — e.g. ["Write it", "Test it"]. Always an array, even for a single subtask. |
No output schema declared.
No examples provided.
subtask_delete ~55
Delete one or more subtasks. Accepts a single ID or array of IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Subtask IDs to delete — e.g. [4, 7]. Always an array, even for one. |
No output schema declared.
No examples provided.
subtask_reorder ~60
Reorder a task subtask list. Pass IDs in the order you want; any omitted keep their relative order at the end.
| Name | Type | Req | Description |
|---|---|---|---|
| ordered_ids | array | yes | Subtask IDs, in order |
| task_id | integer | yes | Parent task |
No output schema declared.
No examples provided.
subtask_update ~146
Update a subtask title, status or position. depends_on sets what it waits on, blocks the inverse; both replace the set, [] clears. Starting or finishing one with unmet prerequisites needs force.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Siblings that wait on this one — inverse of depends_on |
| depends_on | array | – | Siblings this one waits on (replaces the set) |
| force | boolean | – | Proceed despite unmet prerequisites. Only when a human says the blocker no longer applies, never on your own initiative. Logged. |
| id | integer | yes | – |
| sort_order | integer | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
task_batch_update ~102
Update multiple tasks at once. Useful for changing status of several tasks (e.g., mark 3 tasks as done) or reassigning tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | – |
| force | boolean | – | Proceed despite unmet prerequisites. Only when a human says the blocker no longer applies, never on your own initiative. Logged. |
| ids | array | yes | Task IDs to update |
| priority | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
task_create ~135
Create a task within an epic. Tasks are the primary unit of work.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | Assignee name |
| depends_on | array | – | Task IDs this task depends on |
| description | string | – | Task description |
| due_date | string | – | Due date (YYYY-MM-DD) |
| epic_id | integer | yes | Parent epic ID |
| estimated_hours | number | – | Estimated hours |
| priority | string | – | – |
| source_ref | object | – | Link to source code location |
| status | string | – | – |
| tags | array | – | – |
| title | string | yes | Task title |
No output schema declared.
No examples provided.
task_delete ~78
Remove a task (soft delete). Only 'todo' tasks — anything further along has history worth keeping. The row is kept and hidden from listings; task_restore brings it back.
| Name | Type | Req | Description |
|---|---|---|---|
| deleted_by | string | – | – |
| id | integer | yes | – |
| reason | string | – | Why it is being removed (kept in the audit trail) |
No output schema declared.
No examples provided.
task_get ~37
Get a single task with full details including all subtasks, related notes, comments, and dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Task ID |
No output schema declared.
No examples provided.
task_list ~251
List tasks; without epic_id, across all epics. Includes subtask and dependency counts. Rows are compact: nulls and metadata dropped, descriptions cut to 120 chars (task_get for full). branch="current" restricts to the active git branch.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | Filter by assignee |
| branch | string | – | Git branch filter: "current" = active branch, "" = branch-agnostic only, omit = all. |
| epic_id | integer | – | Filter by epic (omit for all tasks) |
| include_archived | boolean | – | Include archived epics and their tasks. |
| include_deleted | boolean | – | Include removed tasks. |
| limit | integer | – | Max results |
| priority | string | – | – |
| project_id | integer | – | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. |
| sort_by | string | – | Omit to follow the arrangement set by task_reorder, falling back to priority. priority (critical first), created (newest), due_date (earliest), status (actionable first), manual. |
| status | string | – | – |
| tag | string | – | Filter by tag |
No output schema declared.
No examples provided.
task_lock_description ~71
Lock or unlock a task's description. While locked, task_update refuses to change it — a guard against rewriting the spec when you meant to add a comment. Every other field still changes freely.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Task ID |
| locked | boolean | – | true to lock, false to unlock |
No output schema declared.
No examples provided.
task_reorder ~61
Set the order of an epic's tasks. Omitted IDs keep their relative order at the end. task_list then follows this arrangement by default.
| Name | Type | Req | Description |
|---|---|---|---|
| epic_id | integer | yes | Parent epic |
| ordered_ids | array | yes | Task IDs, in order |
No output schema declared.
No examples provided.
task_restore ~23
Restore a task removed with task_delete.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
task_update ~197
Update a task; pass only fields to change. Completing it while subtasks are unfinished is refused unless force is set.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_hours | number | – | – |
| assigned_to | string | – | – |
| depends_on | array | – | Task IDs this task depends on (replaces existing) |
| description | string | – | – |
| due_date | string | – | – |
| estimated_hours | number | – | – |
| force | boolean | – | Proceed despite unmet prerequisites. Only when a human says the blocker no longer applies, never on your own initiative. Logged. |
| id | integer | yes | Task ID |
| priority | string | – | – |
| sort_order | integer | – | Manual position within the epic; lower sorts first. Use task_reorder instead of setting this by hand. |
| source_ref | object | – | Link to source code location |
| status | string | – | – |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
template_apply ~77
Apply a template to create tasks in an epic. Replaces {variable} placeholders with provided values.
| Name | Type | Req | Description |
|---|---|---|---|
| epic_id | integer | yes | Epic to create tasks in |
| template_id | integer | yes | Template ID to apply |
| variables | object | – | Key-value pairs for {variable} substitution (e.g., {"feature": "auth"}) |
No output schema declared.
No examples provided.
template_create ~64
Create a reusable set of tasks that can be instantiated into any epic. {variable} placeholders are filled in on apply.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | Template name (must be unique) |
| tasks | array | yes | The tasks this template creates. |
No output schema declared.
No examples provided.
template_delete ~22
Delete a task template.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Template ID |
No output schema declared.
No examples provided.
template_list ~42
List task templates. Pass include_tasks to see what each one actually creates.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tasks | boolean | – | Return each template's task definitions, not just a count. |
No output schema declared.
No examples provided.
template_update ~77
Edit a template in place. Only the fields you pass change; tasks replace the whole list.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | Template ID |
| name | string | – | – |
| tasks | array | – | Replaces every task. Omit to leave them alone. {variable} works in title and description. |
No output schema declared.
No examples provided.
tracker_dashboard ~138
Full project overview in one call: project, epics with task counts, stats, blocked and overdue tasks, recent activity and notes. Best first call when starting work. branch="current" scopes to the active git branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Scope to a git branch: "current" = active branch, "" = branch-agnostic only, omit = all. |
| include_archived | boolean | – | Include archived epics and their tasks. |
| project_id | integer | – | Project ID. Omit for a single-project database or when SAGA_PROJECT is set. Otherwise the first is used and the rest listed under other_projects. |
No output schema declared.
No examples provided.
tracker_export ~62
Export a full project as nested JSON. Includes all epics, tasks, subtasks, comments, dependencies, and related notes. Useful for backup, migration, or sharing.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Project ID to export (omit if only one project exists) |
No output schema declared.
No examples provided.
tracker_import ~51
Import a project from JSON (matching tracker_export format). Creates all entities with new IDs and remaps references. Uses a transaction for atomicity.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Full export JSON object from tracker_export |
No output schema declared.
No examples provided.
tracker_init ~72
Initialize the tracker for a project. If the database is empty, creates a project with the given name. If a project already exists, returns its info.
| Name | Type | Req | Description |
|---|---|---|---|
| project_description | string | – | Description for the new project |
| project_name | string | – | Name for a new project (only used if DB is empty) |
No output schema declared.
No examples provided.
tracker_next ~113
What to work on next: one recommended task with the reason, its next unfinished subtask, alternatives, and — when nothing is actionable — what to unblock. Call it when resuming work; cheaper than tracker_dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | Only consider tasks assigned to this person |
| branch | string | – | Git branch filter: "current" = active branch, omit = all. |
| project_id | integer | – | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. |
No output schema declared.
No examples provided.
tracker_search ~143
Search projects, epics, tasks and notes by keyword. Returns categorized previews — use task_get or note_list for full text.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Git branch filter: "current" = active branch, "" = branch-agnostic only, omit = all. |
| entity_types | array | – | Limit search to specific entity types (omit for all) |
| include_archived | boolean | – | Include archived epics and their tasks. |
| limit | integer | – | Max results per entity type |
| project_id | integer | – | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. |
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
tracker_session_diff ~73
What changed since a timestamp: counts by action and entity, plus the notable changes. Call it at the start of a session to catch up.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | ISO 8601 datetime — show changes after this time (e.g. "2026-02-21T15:00:00") |
No output schema declared.
No examples provided.
How do I install the io.github.spranab/saga-mcp server?
io.github.spranab/saga-mcp runs locally as an npm package, launched with npx -y saga-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · saga-mcp
claude mcp add spranab-saga-mcp -- npx -y saga-mcp
What is the io.github.spranab/saga-mcp server?
io.github.spranab/saga-mcp is listed in the public MCP registry as io.github.spranab/saga-mcp. Jira-like project tracker for AI agents with SQLite, full task hierarchy, and dashboard. This page covers its npm package (saga-mcp).
Is the io.github.spranab/saga-mcp server safe to use?
io.github.spranab/saga-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.spranab/saga-mcp server expose?
io.github.spranab/saga-mcp exposes 41 tools: project_create, project_list, project_update, epic_create, epic_list, and 36 more. Their descriptions and schemas cost roughly 3,494 tokens of context every time the server is loaded.
Is the io.github.spranab/saga-mcp server still maintained?
io.github.spranab/saga-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.spranab/saga-mcp server under?
io.github.spranab/saga-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.