A Jira-like project tracker MCP server for AI agents. SQLite-backed, per-project scoped, with full hierarchy (Projects > Epics > Tasks > Subtasks)
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. That is what the saga mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
saga-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 9 tools. What each one is for:
Projects — The Projects tool exposed by this serverEpics — The Epics tool exposed by this serverTasks — The Tasks tool exposed by this serverSubtasks — The Subtasks tool exposed by this serverComments — The Comments tool exposed by this serverTemplates — The Templates tool exposed by this serverNotes — The Notes tool exposed by this serverIntelligence — The Intelligence tool exposed by this serverHierarchy — The Hierarchy tool exposed by this serverConfiguration is passed through the environment: DB_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Saga MCP's toolset — Projects, Epics, Tasks and 6 more — is a fair guide to whether it matches your workflow. It is maintained by spranab; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Projects | The Projects tool exposed by this server. |
| Epics | The Epics tool exposed by this server. |
| Tasks | The Tasks tool exposed by this server. |
| Subtasks | The Subtasks tool exposed by this server. |
| Comments | The Comments tool exposed by this server. |
| Templates | The Templates tool exposed by this server. |
| Notes | The Notes tool exposed by this server. |
| Intelligence | The Intelligence tool exposed by this server. |
| Hierarchy | The Hierarchy tool exposed by this server. |
{
"mcpServers": {
"saga": {
"command": "npx",
"args": ["-y", "saga-mcp"],
"env": {
"DB_PATH": "/absolute/path/to/your/project/.tracker.db"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DB_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.