Back to browse
GitHub Repository

A Jira-like project tracker MCP server for AI agents. SQLite-backed, 22 tools, full hierarchy, activity logging, and dashboard.

25 starsTypeScript

Saga – A Jira-like project tracker MCP server for AI agents (SQLite)

by spranab·Feb 21, 2026·4 points·5 comments

AI Analysis

●●●BangerSolve My ProblemShip ItZero to One

MCP server solves AI agent context loss with SQLite task hierarchy—no API keys, no setup.

Strengths
  • Directly solves a real pain: AI agents losing project state mid-session without scattered markdown
  • 22 focused tools + activity log designed for agent cognition, not just CRUD
  • Zero external dependencies—SQLite auto-creates schema, no Docker/Postgres needed
Weaknesses
  • Limited to Claude ecosystem (MCP adoption); value drops outside Claude/Cursor workflow
  • Young project—no evidence yet of real-world agent usage scaling
Target Audience

AI engineers, LLM application builders, developers using Claude or Cursor with coding assistants

Post Description

I got tired of my AI coding assistant (Claude, Cursor, etc.) losing track of project state across sessions — creating random markdown files, forgetting what was done, repeating work. So I built Saga.

It's an MCP server that gives your AI agent a proper project tracker — Projects > Epics > Tasks > Subtasks — backed by a local SQLite file. One tracker_dashboard call and the agent has full context to resume where it left off.

Key points:

Zero setup — SQLite auto-creates a .tracker.db file per project. No Docker, no Postgres, no API keys. 22 tools — CRUD for the full hierarchy, plus notes (decisions, blockers, meeting notes), cross-entity search, activity log, batch operations. Per-project scoped — Each project gets its own database. Nothing shared, nothing leaked. Activity log — Every mutation is automatically tracked so the agent (or you) can see what changed and when. Install: npx saga-mcp

GitHub: https://github.com/spranab/saga-mcp npm: https://www.npmjs.com/package/saga-mcp

The idea is simple: instead of the LLM trying to remember state in its context window or dumping it into files, give it an actual structured database it can query and update through tool calls. Works with Claude Desktop, Claude Code, Cursor, or any MCP-compatible client.

Would love feedback — especially on the tool design and what's missing.

Similar Projects