Manage Trello
from your MCP client.

Independent integration for Trello

trello-mcp is an independent, community-maintained project. It is not an official Trello or Atlassian product, service, or MCP implementation, and it is not affiliated with, endorsed by, or sponsored by Trello or Atlassian.

Looking for Trello’s official MCP server? Visit Trello MCP.

77 catalog-backed tools

Boards, lists, cards, checklists, labels, members, comments, attachments, custom fields, and search share one catalog generated from the server’s runtime definitions.

See all 77 tools

Choose your trust boundary

Use local stdio with no network listener, or the documented Docker Compose path with Streamable HTTP published to loopback. Wider HTTP access must be deliberate and protected.

Trello secrets stay out of prompts

The server reads TRELLO_API_KEY and TRELLO_TOKEN from its environment and uses them only for authenticated Trello API requests. HTTP clients can use a separate MCP_AUTH_TOKEN.

Archive before delete

Cards and lists have reversible archive controls. Tool guidance marks permanent card and label deletion as explicit-only; MCP client approval remains the enforcement boundary.

Let your MCP client create a Trello card for you

This example creates one real card in an existing list in your connected Trello account. Your MCP client can discover the board and list IDs, so you only need to choose the destination and supply a card title.

Card creation example prompt

Create a Trello card for me.
Ask which board, list, and title to use.
Show the proposed card_create call and wait for my approval.

1. Choose the destination. The client uses the read-only list_boards and board_lists tools so you can choose an existing list without finding IDs yourself.

2. Review the proposed call. Confirm that card_create has the intended listId and card name. It creates one persistent card.

3. Create the card. Approve the write. If it was only a test, use card_archive instead of permanently deleting it.

Pick your MCP client

The setup guide keeps configuration review separate from successful connection, tool discovery, and live Trello calls. These labels reflect the dated compatibility evidence; they are not inferred from similar clients.

First time connecting? Create your Trello API key and token before configuring your client.

CodexTested over local stdio and authenticated Streamable HTTP.

Claude CodeTested over local stdio and authenticated Streamable HTTP.

Claude DesktopTested over local stdio.

VS CodeConfiguration reviewed for stdio and authenticated Streamable HTTP.

OpenCodeConfiguration reviewed for stdio and authenticated Streamable HTTP.

All compatibility evidenceSee dated test scope, limitations, and live-validation status.

Need another client or deployment route? Open the complete client setup guide or choose a different deployment path.

Before approving a write

Use auth_whoami to confirm the connected Trello account. Discovery tools are read-only, but write tools make persistent changes in Trello. Confirm the target and intended change, and use a disposable board for trial mutations.

Useful by design

Use natural-language requests in an MCP client to search, inspect, and maintain the Trello resources your configured token can access.

Find and summarize work

Search for work, inspect the matching card, and review a bounded activity history before summarizing it.

search → card_get → card_actions

Create and organize cards

Discover the board and its lists, create a card in the intended destination, then move it when the workflow changes.

list_boards → board_lists → card_create → card_move

Coordinate with collaborators

Inspect current card members, assign the right collaborator, and leave a visible update on the card.

card_members → card_member_add → card_comment_add

Track the details

Inspect a card’s checklists, add the next checklist item, and record structured project data in a custom field.

card_checklists → card_checklist_item_create → card_custom_field_set

Follow the workflow guide

One canonical, searchable tool catalog

Names, descriptions, and input definitions come directly from the same registered tool definitions and Zod schemas used by trello-mcp. Category, behavior, scope, and result labels are curated for this reference and checked to cover every registered tool exactly once. Search by name, purpose, or input; filter by category or behavior; and link directly to any tool.

MCP request

MCP method: tools/list

77 tools loaded from the project catalog

Boards

11 list_boards, board_create, board_get, board_field_get, …

Lists

7 list_get, list_create, list_update, list_archive, …

Cards

12 card_get, card_board, card_list, card_create, …

Checklists

10 card_checklists, card_checklist_create, card_checklist_update, card_checklist_delete, …

Search

2 search, search_members

Generated from the same registered tools and schemas as the server. It contains no credentials or Trello account data.

See all 13 categories and 77 tools

Know when to use it

Choose this community server when self-hosting, local stdio, an inspectable deployment, or broad Trello REST automation matters. Choose Trello’s official MCP service when you prefer a Trello-hosted connection, OAuth consent, official support, and a workspace-scoped managed service.

See the full side-by-side comparison, last checked August 10, 2026 against Trello’s official MCP documentation.

Naturally, the public trello-mcp roadmap is itself a Trello board. Follow it to see what is planned, active, and shipped.

Security & DataFollow credentials, Trello data, transports, logs, and write operations across every trust boundary.

ConfigurationReview every runtime and Compose setting, its default, and where it applies.

TroubleshootingDiagnose startup, stdio, HTTP sessions, Docker, Trello API, rate-limit, and attachment failures.

FAQCompare the transports, understand data access, and distinguish this project from Trello's official MCP server.