Claude Saga connectorWhat Claude keeps track of in your Saga projects.
The Claude Saga connector exposes 31 tools: 13 read, 18 write, 0 undocumented. It's a desktop extension that keeps projects, tasks and decisions in a SQLite database on your machine. Below: what Claude reads, what it writes, and what gets deleted.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude works on something over time
Saga pitches itself as the way to stop losing track of a project between sessions. It gives Claude a structured database on your computer: projects, epics, tasks, subtasks, notes and decisions. Instead of scattered text files, one dashboard call hands the context back, and from there it can create, update or delete.
Pick up where you left off. At the start of a conversation, tracker_session_diff lists what changed since a given point in time, and tracker_dashboard gives the big picture with a summary.
Break down a workstream. For a new piece of work, task_create sets up tasks with their dependencies, subtask_create splits them, and task_update frees up the next step automatically once a task is done.
Keep decisions on record. Once a decision is made, note_save logs it, note_search finds it again with a full-text search, and activity_log shows the change history.
What Claude doesn't do here: nothing fires on its own, and no task appears when a ticket or a commit comes in. The database lives in a local file, not in a shared online service. And the sheet doesn't publish every tool in the author's repository. For routines triggered by events, you want an automation tool; the Integrations page covers that side, and Claude connectors gathers the rest.
The vocabulary in one minute
Five words worth knowing before you install Saga.
- Connector
- The link you set up once between Claude and a service or a file, so Claude can use it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Directory
- The official catalogue where every connector has its own sheet: publisher, purpose and the named list of tools it exposes.
- Approval
- The confirmation Claude waits for before finishing an action that changes data, shown in the chat right when it matters.
- MCP
- The common standard behind connectors: it's what lets an assistant like Claude hold a conversation with an outside service.
Set up Saga in Claude in three steps
- 01
Find Saga
In Claude's settings, open Customize, then Connectors, and spot Saga in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Start the connection from its row with Connect. This desktop extension has no account to sign into: the author only asks for the database path. If the link breaks, Disconnect and connect again.
- 03
Pick the scope
If several projects share one database, the manifest offers an optional scope setting so the tools only see one project. Left blank, Claude reads across the whole database, every project included. Decide that before you start.
The 31 tools of the Claude Saga connector
Saga gives Claude 31 tools: 13 that read your account, 18 that change something in it.
Two groups, per the author's manifest and README, which annotate every tool: read-only or not, destructive or not. Names stay as Claude shows them.
- 13 read
- 18 write
What Claude reads (13)
13 toolsThirteen tools the author annotates as read-only: lists, searches, history and export.
tracker_dashboard
Gives a full overview of a project with a plain-language summary. In one call, Claude gets what it needs to pick the thread back up.
project_list
Lists the projects in the database with their completion stats. You see at once which efforts are progressing and which are stuck, without opening each one.
epic_list
Lists a project's epics, the large chunks of work that group tasks together, with the task count for each, so the weight of every chunk is visible.
task_list
Lists and filters tasks along with their dependencies. Order follows a manual arrangement when there is one, per the README, and the default order otherwise.
task_get
Fetches a task with its subtasks, notes, comments and dependencies. It's the complete card, ready to read through, with everything that orbits the task.
comment_list
Lists the comments on a task. Ones that were removed stay hidden unless you explicitly ask to include them.
template_list
Lists the available task templates; an option shows the tasks each one lays out. Useful before applying one, so you know what to expect.
note_list
Lists the notes in the database with filters. Decisions, context, meeting notes or blockers: whatever was recorded alongside the tasks, kept apart from the task cards themselves.
note_search
Runs a full-text search across every note. Handy when you remember a word but not the note it was in, or even which project it belonged to.
tracker_search
Searches across projects, epics, tasks and notes in a single query. It's the cross-cutting search of the database, useful when you no longer know at which level something was filed.
activity_log
Shows the history of what happened, with filters. Per the author, every mutation is recorded automatically, which makes it a complete trail of what happened in the database.
tracker_session_diff
Shows what changed since a given timestamp. The README suggests calling it at the start of a work session, so you restart from the real state rather than from memory.
tracker_export
Exports a full project as nested JSON, dependencies and comments included. It's your backup or the starting point for a migration.
What Claude writes (18)
18 toolsEighteen tools that create, update, import or delete. No source spells out their confirmation: the general rule below applies.
tracker_init
Approval: see the ruleInitializes tracking and creates the first project in the database. It's the very first move on a fresh file.
project_create
Approval: see the ruleCreates a new project in the database, alongside the ones already there.
project_update
Approval: see the ruleUpdates a project; archiving it works as a soft delete, per the author. The project leaves the listings without being wiped from the database.
epic_create
Approval: see the ruleCreates an epic inside a project, to group a set of related tasks under one goal.
epic_update
Approval: see the ruleUpdates an existing epic inside its project. The tasks grouped under it stay where they are.
task_create
Approval: see the ruleCreates a task, with optional dependencies on other tasks. The working order is set from the moment it exists.
task_update
Approval: see the ruleUpdates a task. Per the author, each change is logged and dependent tasks block or unblock automatically.
task_batch_update
Approval: see the ruleUpdates several tasks in one go instead of one by one. Handy for a change that touches a whole batch.
subtask_create
Approval: see the ruleCreates one or more subtasks under a task, in batch if needed. The work gets broken down without piling up calls.
subtask_update
Approval: see the ruleUpdates a subtask's title, status or position, and sets its order relative to the others.
subtask_delete
Approval: see the ruleDeletes one or more subtasks, in batch if needed. The author flags it as destructive.
comment_add
Approval: see the ruleAdds a comment to a task, in a threaded discussion. That's where the reasoning behind decisions made along the way is kept.
template_create
Approval: see the ruleCreates a reusable task template, with variables in curly braces to fill in when you use it.
template_apply
Approval: see the ruleApplies a template to create its tasks in one go, swapping the variables for the values you give.
template_delete
Approval: see the ruleDeletes a task template. The author flags the tool as destructive.
note_save
Approval: see the ruleCreates a note or updates an existing one. Decision, context, meeting notes or blocker: it stays attached to the project.
note_delete
Approval: see the ruleDeletes a note from the database. The tool carries the author's destructive annotation.
tracker_import
Approval: see the ruleImports a project from a JSON file in the export format. It's the counterpart to export, for a restore or a migration.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes for you. The request shows up in the chat, right when it matters.
No source says whether Claude asks before creating a task, importing a project or deleting a note: that default rule covers all eighteen write tools. On a Team or Enterprise workspace, owners decide whether a member can let certain actions through without being asked again, and they can shut off a connector's writes for the whole organization. Nobody overrides that setting from their own account, whatever they install.
Which plans include it
Out of 819 sheets in the official directory, none shows availability by plan. Connector by connector, the answer isn't published anywhere: it's a real gap in the catalogue.
The general rule is published: desktop extensions install on Claude Desktop, and they are open to all users there. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, the Saga sheet in the official directory is where to look.
Where Saga stops inside Claude
A connector isn't an automation. Claude calls these tools while it answers you: nothing gets created by itself when a ticket, a commit or a message arrives.
Only the author documents this connector, through the official repository: neither Claude's help center nor Anthropic's docs mention it. The directory badge isn't a security audit, and Anthropic says so on every sheet: it doesn't choose the tools a publisher exposes and doesn't guarantee they behave as described. On top of that, the sheet and the repository don't list the same tools, as the comparison below shows.
How many tools does the Saga extension expose?
- Claude directory sheet ↗October 202631 tools, each with safety annotations.
- Author's official repository README ↗October 2026More tools, including a next-task suggestion and soft deletion of a task or comment, none of which are on the sheet.
What this page followsNeither side is stale: the sheet describes 31 tools, the repository a newer, broader version. This page sticks to the sheet's 31; check in Customize > Connectors which list your installed extension shows.
Need help connecting Saga to Claude?
A person reads every message.
