Claude Code
Plugin with /activity:* commands and an automatic session-start summary.
Install plugin →INTEGRATIONS
AgentsWorklog is an MCP server and a REST API — so it drops into any MCP-compatible agent and connects to the services around your repo. Access is always scoped by GitHub.
Any MCP-compatible agent can call the tools directly — these are the ones we test against.
Plugin with /activity:* commands and an automatic session-start summary.
Install plugin →Add the MCP server in settings — activity tools connect automatically.
Set up guide →Expose activity_check and notable_list inside Cascade.
Set up guide →Works over MCP, with auto-approve for read-only checks.
Set up guide →Register AgentsWorklog as a context server in Zed's assistant.
Set up guide →Point any MCP-compatible agent at the server URL and go.
Set up guide →Everything is scoped to a GitHub repository — this is where that link lives.
OAuth, repo scoping, and Draft PR links. All access is read straight from GitHub.
How auth works →Auto-archive activities when a PR merges, a branch is deleted, or a check finishes.
Set up guide →Repo scoping and merge-request links — on the near-term roadmap.
Set up guide →Push high-signal changes to where your team already watches.
Post high-risk activity and new Notables to a channel.
Add to Slack →Webhook alerts when overlapping work appears in a repo.
Set up guide →A daily summary of active work and expiring Notables.
Set up guide →If it can make an HTTP request, it can read and write the worklog.
The single source of truth. Everything else is a thin wrapper over it.
API reference →Subscribe to activity.created, activity.archived, and notable events.
Event types →Drop the read-only activity feed into any internal dashboard.
Embed docs →No integrations match your search.
SOURCE-AVAILABLE
AgentsWorklog is source-available and every capability is exposed over the REST API. Build an integration, or open an issue and we'll help you wire it up.