Summary

Board detail comes back with its lists and cards, which is what makes one call enough.

Most Trello questions — what is in progress, what is stuck, who owns what — are answerable from a single board fetch rather than a walk through lists and cards. The tiering is worth noting for what it implies about scope: creating and moving cards is core, while checklists and attachments are read-only surfaces here.

What it is

An MCP server for Trello that works with any MCP client over stdio, organised into three tiers: the essentials for search and card work, core operations for updating and moving, and advanced tools for the board's supporting data. Credentials stay in your client's config and every Trello call goes over HTTPS with automatic retry when the rate limit bites.

What you get

Universal search across boards, cards, members and organisations, plus the boards you can reach — `trello_search`, `trello_get_user_boards`
Board detail with its lists and cards, and full card detail including members, labels and checklists — `get_board_details`, `get_card`
Cards created in any list, updated in place, and moved between lists to change workflow state — `create_card`, `update_card`, `move_card`
Comments posted onto cards, and new lists created on a board — `trello_add_comment`, `trello_create_list`
Cards fetched per list or per board with filtering — `trello_get_list_cards`, `trello_get_board_cards`
The supporting data: card activity history, attachments, checklists, board members, board labels and member detail — `trello_get_card_actions`, `trello_get_card_attachments`, `trello_get_card_checklists`, `trello_get_board_members`, `trello_get_board_labels`, `trello_get_member`
Two legacy tools kept for backward compatibility — `list_boards`, `get_lists`

Requirements

A Trello account with API credentials: get the API key from `https://trello.com/app-key` and generate a token with read/write access. Node.js 18+ and a clone built with `npm install` and `npm run build`; register `dist/index.js` with `node` and put `TRELLO_API_KEY` and `TRELLO_TOKEN` in the client's `env` block. The README gives per-client instructions for Claude Desktop, Claude Code and Gemini CLI, and any stdio-capable client works the same way. Credentials stay in the local client config; the server talks to Trello over HTTPS and retries automatically when rate-limited. Claude Desktop logs to `~/Library/Logs/Claude/mcp-server-trello.log` on macOS.

Setup effort

One command plus a key — npx -y trello-mcp, then supply credentials