Where Tick-it plugs in
Tick-it works inside your coding agent, in the browser and on GitHub. Its tools are an MCP server, which is how other agents can connect.
The Claude Code mod
The board, the ticket's brief, the size budget and stewarding, beside your session.
> /tick-it add S Add a README badge Created TCK-212 · S · Ready
The web app
Home, the board, epic plans, the merge queue, agent sessions, proposals, costs and memory, for the whole team.
app.tick-it.dev/r/acme/checkout Board · Epics · Merge queue Proposals · Costs · Memory
The GitHub App
Follows each pull request and its CI, moves the ticket when it merges, and posts before and after pictures for a change people can see.
PR #318 merged
TCK-212 → Done
3 checks passed · 1 review roundThe mod
Install it from the plugin marketplace and sign in with GitHub. /tick-it shows the board and takes a ticket; the mod brings the brief, the size budget and stewarding into your session.
Cloud sessions
Add a claude.ai routine for a repository and Tick-it can start a session on a ticket in the cloud, on your own account. Each person adds their own, so sessions are billed to whoever started them.
/plugin marketplace add tinkerbench-studio/tick-it-claude-mod /plugin install tick-it@tickit /tick-it
The GitHub App
The App tells Tick-it what happens to a repository's pull requests and CI, so a merged pull request moves its ticket to Done and its checks show on the ticket. It reads pull requests, checks and contents.
It writes back only to post a ticket's before and after pictures on its pull request, and when you turn on leaving drafts, auto-merge, or press Merge.
Any MCP client
Everything Tick-it does is a tool on its MCP server: tickets, plans, sessions, reviews, costs and memory. Sign in with GitHub and choose the scopes to grant. Claude Code uses it today, and any agent that speaks MCP can use the same tools.