Activity Feed
A chronological record of who changed what — attributed to the app or to an MCP client by key name.
The Activity feed answers "who did what, when?" across your work. It surfaces in the dashboard's Activity tab.
What is tracked
Activity is recorded for the three core entity types — task, project, milestone — across these actions:
| Action | When it's recorded |
|---|---|
created | A task, project, or milestone is created. |
updated | Fields are edited (no status/assignment change). |
status_changed | A task's status changes (the new status is captured). |
completed | A task or milestone is marked Completed/Done. |
assigned | A task's assignee list changes. |
deleted | An entity is deleted. |
Each event stores the actor, the entity and its title, the action, optional detail (e.g. the new status), and the related project.
Personal vs. team scope
- In a personal workspace, the feed shows your own activity.
- In a team workspace, the feed is team-scoped — actions across the team's projects, attributed to whichever member performed them.
Manual vs. MCP attribution
Every event records a source:
manual— the change was made in the sprintrr app.mcp— the change came through the MCP integration. MCP events additionally record the name of the API key that made the change, so automated changes are clearly distinguishable from human ones and traceable to a specific key.
Attribution is recorded at the application layer (not by a database trigger), which is what makes the manual-vs-MCP distinction — and the MCP key name — reliable. Activity recording is best-effort: if it ever fails, it never blocks the underlying change.
Why it matters
When you automate with MCP (from Claude, Cursor, or your own scripts), the feed lets you see exactly which actions an agent took and under which key — useful for review, auditing, and trust when handing work to AI tooling.
Related
- MCP integration — how MCP actions are attributed.
- Teams — team-scoped feeds.