Enables reading and managing Trello boards, lists, and cards: list boards/lists/cards, fetch full card details (description, checklists with item ids and states, members, labels, attachments, comments), search cards across boards with Trello search syntax, tick or untick checklist items, post comments on cards, and move cards between lists. Card arguments accept an id, short link, or full card URL.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@trello-mcp Read this Trello card and tick off the checklist items I've finished: https://trello.com/c/abc123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A small Model Context Protocol server for Trello. It lets Claude Code (or any MCP client) read the cards a customer writes for you, tick checklist items and leave comments, without leaving the editor.
Built for a real workflow: the product owner on my current project files every round of feedback as a Trello card with a checklist. With this server the assistant reads the card, works through the items and ticks them off as each one lands.
Tool | What it does |
| Open boards for the token's user |
| Lists (columns) on a board |
| Open cards on a board or in one list |
| Full card: description, checklists with item ids and states, members, labels, attachments, comments |
| Trello search across boards ( |
| Tick / untick a checklist item |
| Post a comment on a card |
| Move a card to another list |
Card arguments accept an id, a short link, or the full card URL, so you can paste a link straight from Trello.
Read tools are annotated readOnlyHint: true; the three write tools are not, so clients can ask before running them.
Related MCP server: Trello MCP server
Get an API key and token: https://trello.com/power-ups/admin → your Power-Up → API key → "Token".
Build:
npm install
npm run buildRegister with Claude Code (user scope, so it works in every project):
claude mcp add trello --scope user \
-e TRELLO_API_KEY=your_key -e TRELLO_TOKEN=your_token \
-- node /absolute/path/to/trello-mcp/dist/index.jsOr by hand in ~/.claude.json:
{
"mcpServers": {
"trello": {
"command": "node",
"args": ["/absolute/path/to/trello-mcp/dist/index.js"],
"env": { "TRELLO_API_KEY": "your_key", "TRELLO_TOKEN": "your_token" }
}
}
}npm test # vitest, no network: the Trello client takes an injected fetch
npm run typecheck
npm run dev # runs the server over stdio with tsxThe code is split so the interesting parts are testable without a server:
src/trello.ts — typed client over the REST API, URL/short-link parsing, error mapping
src/format.ts — renders cards as compact markdown for the model (ids stay visible for follow-up calls)
src/tools.ts — tool definitions with zod input schemas and handlers
src/index.ts — MCP wiring over stdio
Everything runs as the token's user: comments and ticks show up under your name in Trello.
stdout is the MCP channel; the server writes diagnostics to stderr only.
Trello rate limits: 300 requests per 10 s per key, 100 per 10 s per token. Normal use is far below that.
Post a comment on a card as the token's user.
Inputs: text (required), cardId (required).
Full card: description, checklists with item ids and states, members, labels, attachments and comments.
Inputs: cardId (required).
List the open boards the current user can see, with ids for the other tools.
Inputs: no named parameters.
List open cards on a board or in one list. Pass listId to narrow to a column, otherwise boardId for the whole board.
Inputs: listId, boardId.
List the open lists (columns) of a board.
Inputs: boardId (required).
Move a card to another list on the same board. List ids come from trello_list_lists.
Inputs: cardId (required), listId (required).
Search cards across all boards. Supports Trello search operators, e.g. 'board:Project is:open @me label:bug'.
Inputs: query (required), limit.
Mark a checklist item complete or incomplete. Item ids come from trello_get_card.
Inputs: state (required), cardId (required), checkItemId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
Each tool targets a distinct resource and action: boards, lists, cards, comments, moves, search, and checklist items. list_cards and search_cards could superficially overlap, but the descriptions clearly distinguish browsing a board/list from global search.
All tools use a consistent trello_ prefix followed by a verb_noun pattern, such as trello_list_boards and trello_move_card. There are no deviations in casing or verb style.
Eight tools are well-scoped for a focused Trello workflow covering discovery, card inspection, search, comments, moves, and checklist updates. Each tool has a clear role without excessive surface area.
The set supports reading and some card actions but lacks fundamental Trello operations such as creating cards, creating lists, updating card fields, and archiving/deleting items. These gaps will block common agent workflows despite the solid read/search/move coverage.
Simple kanban for small teams. Read and update your Moxboard boards and tasks from Claude.
AI-native Kanban board — connect Claude to claim, work and move your tasks over MCP.
Trello in Claude Code in 60 seconds. No API key, no hosting. Hosted, OAuth sign-in, 18 tools.
Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.
