trello
Your boards, run from your agent
Boards, lists and cards end to end, plus the moves that save real time: a board digest, a due-date radar for what is slipping, and a shopping list put in aisle order. One install, the whole pack.
Install trello
Add the DBHQ marketplace, once
/plugin marketplace add dbhq-uk/marketplaceInstall the skill
/plugin install trello@dbhq
Both commands work in Claude Code and in Codex. The marketplace is a public repository you can read first: dbhq-uk/marketplace (external site)
What it is good at
Every board at once, and that is the trade
Atlassian runs an official Trello MCP server: hosted, signed in with OAuth, and one workspace per connection. This calls the Trello REST API directly with your own key and token instead, so it sees every board your account can, which the radar needs, and reads comments and activity, which the digest needs. The cost is a token that reaches your whole account rather than one workspace, and a host where the agent can run a script.
The whole board, end to end
Create, move, position, label, comment on and archive cards, add and tick checklists, and create boards, lists and labels, driven in plain language over the Trello REST API. On a board that already uses labels, every card on a list it touches carries one. It archives rather than deletes, and deletes only a card you name.
A standup you did not have to write
The board digest is a plain-English status snapshot: the lists and their cards, what is due or overdue, what moved recently and what has not moved in a fortnight. Each list shows its first ten cards and counts the rest, so it reads as a briefing rather than a data dump.
Seeing what is slipping across every board
The due-date radar sweeps all your boards at once and sorts by date, overdue first, so a deadline hiding on a board you have not opened this week still surfaces. A board it could not read is named rather than skipped, and a card already in Done is not called overdue.
Shopping in aisle order
A list gets reordered into a supermarket's aisle flow with a food-type emoji on every card. The order comes from a preset file, so any store can be described.
What it does not do
It cannot limit a token to some of your boards
Trello has no per-board tokens, so any token reaches every board your account can see. Setup offers a read-only token, which is all the digest and the radar need, and an expiry of 1 day, 30 days or never, but it cannot fence a token to the boards you meant. If that breadth matters, Atlassian's hosted Trello MCP is scoped to one workspace.
Only one store is described in the box
Aisle order comes from a preset, and a Tesco (UK) preset is the one that ships. Another supermarket means copying that file and editing it - which takes a few minutes, but nobody has done it for you.
It holds nothing on your behalf
No secrets live in the repository and there is no DBHQ service in the middle. Setup runs only at your own terminal, so you type the key and token and no agent handles them. They sit in your own home directory at permissions 600 and go to Trello direct from your machine, in a request header rather than on a command line, which also means losing that machine is losing that setup.
It needs jq and curl, on Linux, macOS or WSL
There is no native Windows path and no vendor SDK, and curl has to be 7.55 or later, because the key and token reach it on stdin. If those two commands are not on the box, nothing runs.
Read it before you install it
Every line is public and MIT licensed. The README is the long version of this page, including the parts that are still rough.