Analytics and activity
You can use these MCP tools when an agent needs board status before deciding what to do next. They complement the board-management tools by focusing on movement, unread work, activity, and traceability.Tools covered
| Tool | Purpose |
|---|---|
okto_pulse_get_activity_log | Recent board events and user/agent activity. |
okto_pulse_get_analytics | Board-level counts, status breakdowns, throughput, validation metrics, and risk signals. |
okto_pulse_get_unseen_summary | What changed since the authenticated agent last checked. |
okto_pulse_list_my_mentions | Mentions addressed to the authenticated agent. |
okto_pulse_mark_as_seen | Mark activity or mention state as read. |
okto_pulse_get_traceability_report | Coverage links between tasks, scenarios, rules, contracts, and requirements. |
Session-start status check
A practical session start is:Activity log
okto_pulse_get_activity_log answers what changed and who changed it. Use it to ground a handoff or to decide whether a card moved while the agent was offline.
Analytics
okto_pulse_get_analytics returns board metrics: status counts, validation gate metrics, stale work, sprint health, bug counts, and coverage signals. Use it for planning and QA, not as a substitute for reading the exact spec or card.