productivityoauth2

Trello

Kanban boards for teams.

Verdict

Trello via MCP is the simplest project-management integration on this list — boards, lists, cards. If your team's workflow fits on a Kanban board and you don't need complex schemas, the simplicity is a feature. What we notice: the model handles Trello operations cleanly because the data model is small. Read queries (what's on this board, what cards are stuck in this list, who's assigned) work reliably. Card creation and movement work cleanly. The constraints of Trello (no custom statuses, basic field types, board-scoped views) mean the integration just doesn't have many corners to get wrong. Best for: small teams running on Trello who want AI in their card flow; personal task tracking where Trello is the sole tool; informal workflows that don't need Linear's structure or Jira's customisation; lightweight Kanban for marketing or content teams. Avoid for: orgs that need cross-board reporting at scale (Trello's cross-board story is weak); engineering workflows (Linear is the right tool); compliance-heavy environments where Trello's simpler permission model isn't enough. Practical frame: free tier covers basic boards; paid plans unlock advanced features. API access via API key + token. Token cost is the lowest of any project-management MCP because Trello records are small.

Common use cases

  • Triage feature requests from customer calls
  • Update sprint board during standup
  • Log meeting decisions as cards
  • Attach design files to active tasks
  • Pull board status for weekly reports

Integration

Vendor
Trello
Category
productivity
Auth
OAUTH2
Tools
50
Composio slug
trello

Tools

  • Add a label to a board

    Creates a new label on an existing trello board.

  • Add attachment to card

    Adds an attachment to a trello card by `idcard`; specify either a `file` to upload or a `url` to link, but not both.

  • Add board

    Creates a new trello board; the 'name' parameter is required for creation, and various preferences can be customized or cloned from a source board.

  • Add board

    <<deprecated: this action is deprecated. please use 'add boards' instead.>> creates a new trello board, requiring the 'name' parameter.

  • Add board power-up

    Enables the power-up specified by the 'value' parameter on the board; processes one power-up enablement per call.

  • Add board star to member

    Stars a trello board for a member (does not remove or list stars), optionally at a specified position; the board must exist and be accessible to the member.

  • Add card

    (deprecated: use add cards) creates a new card in a trello list; `idlist` is required, and if `idcardsource` is used, the source card must be accessible.

  • Add card

    Creates a new card in a trello list; `idlist` is required, and if `idcardsource` is used, the source card must be accessible.

  • Add card member by id

    Assigns a trello member to a specific trello card by card id (or short link) and member id.

  • Add card to list

    Creates a new card in a trello list, which must be specified by an existing and accessible `idlist`.

  • Add check item to checklist

    Adds a new check item to an existing checklist on a specific trello card.

  • Add check item to checklist

    Adds a new check item to a specified trello checklist; this action does not update existing check items.

  • Add checklist to board

    Creates a new, initially empty checklist with a given name on an existing and accessible trello board.

  • Add checklist to card

    Creates a new checklist on a trello card, either by name or by copying from `idchecklistsource`, targeting an `idcard` or `idboard`; this action creates only the checklist structure, not its items.

  • Add checklist to card via id

    Adds a checklist to a trello card: use `value` to add a specific existing checklist, `idchecklistsource` to create a new checklist by copying an existing one (optionally using `name` for the new checklist's name), or `name` to create a new

  • Add comment to card

    Adds a new text comment, which can include @mentions, to a trello card specified by its id; file attachments are not supported via this action.

  • Add custom board background for a member

    Adds a new custom board background for a specified trello member; the `file` parameter (image data) is required.

  • Add custom emoji for a member

    Adds a new custom emoji using an image file and a unique name to a trello member's account; this emoji is member-specific and not shared across the workspace.

  • Add custom sticker for member

    Uploads a custom sticker to a trello member's collection, if the member's plan allows custom stickers and respects associated limits.

  • Add labels to card

    Adds a label to an existing trello card (specified by `idcard`), defining the label by `name` and either `color` or the overriding `value` (which specifies color by name); a new label is created on the board if a matching one (by name/color

  • Add label to card

    Adds an existing label to a trello card; `idcard` identifies the card and `value` is the id of the label to add. both card and label must already exist.

  • Add member board background

    Adds a new custom board background, from an image file, to a specified trello member's collection, making it available for their use but not applying it to any board.

  • Add member vote to card

    Casts a 'yes' vote for a specified member on a trello card; a member can only vote once per card.

  • Add new list to board

    Creates a new list on a specified trello board, with options to copy an existing list, set its position, initial state (archived/subscribed), and does not modify existing lists or move cards.

  • Add new list to board

    Creates a new, empty list on a specified, existing trello board, typically used as a column or category for organizing cards.

  • Add organization logo

    Sets or updates the logo for a trello organization; the provided image file must adhere to trello's format and size restrictions.

  • Add saved search for member

    Creates a new saved search with a specified name, position, and query for a trello member.

  • Add sticker to card

    Adds a sticker to a trello card, using a default sticker name (e.g., 'taco-cool') or a custom sticker id for the image, and allows specifying its position, rotation, and z-index.

  • Add token webhook

    Creates a webhook for a trello token to monitor a trello model (`idmodel`) and send notifications to a `callbackurl`, which must be publicly accessible and able to respond to trello's head validation request.

  • Archive all cards in list

    Archives all cards in a trello list; while cards can be restored via the trello interface, this action does not provide an unarchive function.

  • Create label on board

    Creates a new label with a specified name (required) and color on a trello board (idboard required); this action defines the label but does not apply it to cards.

  • Create new session

    Creates or updates a trello user session, optionally linking it to a specific board for status updates and setting the user's activity status.

  • Create organization

    Creates a new trello organization (workspace) with a `displayname` (required), and optionally a description, website, and various preferences (e.g., board visibility, member invitation restrictions).

  • Generate board calendar key

    Generates a new calendar key for the trello board specified by `idboard`, invalidating any previous key for that board.

  • Generate email key for board

    Generates a new email key for the trello board specified by idboard to enable or reset adding cards via email; this invalidates any previously existing email key for the board.

  • Get action by ID

    Deprecated: use `get actions by id action` instead. retrieves detailed information about a specific trello action by its id.

  • Get an action's list

    Retrieves the trello list associated with a specific trello action id, for actions linked to a list. <<DEPRECATED use get_actions_list_by_id_action>>

  • Get board by action id

    Deprecated: use `get actions board by id action` instead. retrieves details for the trello board associated with a specific action id, returning board information only.

  • Get board by id

    Fetches comprehensive details for a specific trello board by its id; this is a read-only action. <<DEPRECATED use get_boards_by_id_board>>

  • Get board's lists

    Deprecated: retrieves lists from a specified trello board; use `get boards lists by id board`.

  • Get card by ID

    Deprecated: use `get cards by id card`. retrieves a trello card by id/shortlink, with options for related data.

  • Get card field by id

    (deprecated: use `get cards by id card by field` instead) retrieves the value of a single, specified field from a trello card.

  • Get cards by board ID

    Deprecated (use `get boards cards by id board`): retrieves cards from an existing trello board, allowing filtering and customization of fields for cards, attachments, and members.

  • Get cards by filter from board

    Deprecated: use `get boards cards by id board by filter`. retrieves cards from a trello board using a filter.

  • Mark all notifications as read

    Marks all trello notifications for the authenticated user as read across all boards; this action is permanent and cannot be undone.

  • Mark board as viewed

    Marks the trello board specified by idboard as viewed for the current user, exclusively updating its viewed status and potentially influencing its position in user-specific lists and notification settings.

  • Move all cards in list to board

    Moves all cards from a trello list to a *different* board; this action is irreversible, moves (not copies) cards, and empties the source list without deleting it.

  • Update card attributes

    Updates an existing trello card's attributes like name, description, due date, members, labels, position, or archives/unarchives it, attaches files, or changes its cover. <<DEPRECATED use update_cards_by_id_card>>

  • Update card list ID

    Deprecated: moves a trello card to a different list on the same board. use `update cards id list by id card` instead.

  • Upload member avatar

    Updates a trello member's avatar using a base64-encoded image; the `file` field, though schema-optional, requires valid image data for a successful update.

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Trello in the MCP catalog and click Connect. 3. You'll be redirected to Trello's OAuth consent screen — log in with the account that owns or has access to the boards you want to manage. 4. Grant read and write permissions for boards, cards, and lists (Trello will show the exact scopes requested). 5. After authorizing, you'll return to Switchy and see a green checkmark next to Trello. 6. Open any Space and type '@Trello list my boards' to confirm the connection works. 7. If you see your boards appear, you're ready — try '@Trello add a card to [list name]' to test write access. 8. If the test fails, revisit Settings > Integrations and check that the OAuth token hasn't expired or been revoked in your Trello account settings.

What teammates see: by default, memories from Trello are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Create Sprint Card

@Trello add a card to the 'Current Sprint' list with the title 'Refactor payment flow' and description 'Move Stripe logic into a service layer' and set the due date to next Friday.
Open in a Space →

Attach Meeting Notes

@Trello attach the meeting notes document at https://docs.example.com/notes to the card 'Q2 Planning' on the Product Roadmap board.
Open in a Space →

Pull Board Status

@Trello show me all cards in the 'In Review' list on the Engineering board, including who's assigned and the due dates.
Open in a Space →

Label Urgent Tasks

@Trello add the 'Urgent' label to the card 'Fix checkout bug' on the Support board.
Open in a Space →

Star Key Boards

@Trello star the 'Client Onboarding' board for me so it appears at the top of my board list.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@trello show me all cards in the 'Q1 Launch' board that are overdue or due this week, grouped by list

Output

Based on the Q1 Launch board, here are the cards due this week or overdue: **Overdue (3 cards):** - 'Finalize pricing page copy' in Design Review (due 3 days ago) - 'Set up analytics tracking' in In Progress (due 1 day ago) - 'Legal review of terms' in Blocked (due 5 days ago) **Due this week (5 cards):** - 'Deploy staging environment' in Ready for QA (due in 2 days) - 'Write launch email' in To Do (due in 4 days) - Three additional cards in In Progress This is an illustrative example showing how Trello's search and filtering capabilities surface time-sensitive work across your board structure.

Notes

This read-heavy example demonstrates Trello's ability to query cards by due date and organize results by list. Requires OAuth scope to read boards and cards. The MCP can filter by labels, members, and dates, but complex queries may hit Trello's API rate limits (300 requests per 10 seconds per token). Results reflect board state at query time.

Prompt

@trello create a card in the 'Bug Triage' list called 'Login fails on Safari 17' with a red 'Critical' label and assign it to @sarah

Output

Card created successfully in the Bug Triage list: **Login fails on Safari 17** - Card ID: 65f8a3b2c1d4e5f6a7b8c9d0 - List: Bug Triage - Label: Critical (red) - Assigned to: Sarah Chen (@sarah) - Created: Just now - URL: https://trello.com/c/aBc123De The card is now visible to all board members. Sarah will receive a notification about the assignment. This example illustrates a typical bug-reporting workflow where the MCP handles card creation, labeling, and assignment in a single action.

Notes

This write example shows Trello's card creation with label and member assignment. Requires OAuth write scope (boards:write). The MCP must resolve member usernames to Trello IDs, which fails if the member isn't on the board. Label names must match existing board labels exactly (case-sensitive). Side-effect: triggers Trello notifications to assigned members.

Prompt

@trello review all cards in 'Done' from the last sprint and draft a release note summarizing what shipped, organized by feature area

Output

Analyzing 23 cards moved to Done between March 1-15: **Release Note Draft – Sprint 12** *Authentication & Security (5 cards)* Shipped OAuth2 refresh token handling, added rate-limit headers to API responses, and fixed session timeout edge cases. *Search Experience (8 cards)* Launched fuzzy matching for board names, improved filter performance by 40%, and added keyboard shortcuts for quick search. *Mobile (6 cards)* Released offline mode for card viewing, fixed attachment preview crashes on Android, and updated push notification delivery. *Infrastructure (4 cards)* Migrated background jobs to new queue system and upgraded database connection pooling. This synthesis example shows how the AI can transform raw Trello card data into narrative summaries.

Notes

This synthesis example pairs Trello's card-fetching with AI reasoning to generate human-readable summaries. The MCP retrieves card titles, descriptions, and labels; the AI interprets and organizes them. Accuracy depends on how well cards are titled and labeled. Works best when teams use consistent naming conventions. No write operations occur—this is pure read-and-analyze.

Use-case deep-dives

Support ticket routing at 8-person SaaS

When Trello beats Linear for customer-facing triage

An 8-person support team uses Trello boards to route incoming tickets from Intercom to engineering pods. The MCP's 'Add card' and 'Add attachment to card' tools let an AI agent create cards with customer screenshots attached, then label them by severity and assign to the right list. This works because Trello's visual board layout matches how the team already thinks—swim lanes for each pod, labels for urgency. The OAuth2 flow means the agent acts as the team's shared service account, not individual logins. The trade-off: if you're routing more than 200 tickets a day, Trello's search gets sluggish and you'll want a database-backed tool. Below that threshold, the 50-tool surface area gives you enough automation to skip manual card creation entirely.

Content calendar sync for 3-person agency

Trello MCP for multi-client editorial planning

A 3-person content agency manages six client editorial calendars in separate Trello boards. The MCP's 'Add board' and 'Add card' tools let an AI agent create next month's content cards in bulk from a Google Sheet template, then attach draft briefs as PDFs. This scenario wins because each client gets a board they can view without agency tool access, and the agent handles the repetitive setup every month. The 'Add board power-up' tool means you can script enabling Butler or Calendar view per board. The limit: Trello doesn't version card descriptions, so if your workflow needs draft history, you'll export to Notion after the planning phase. For pure calendar coordination with external stakeholders, this MCP closes the loop.

Sprint retrospective aggregation at 12-person dev team

Why Trello MCP falls short for retro synthesis

A 12-person dev team runs sprint retros in Trello, one board per sprint with lists for 'Went Well', 'Needs Work', 'Action Items'. An AI agent could theoretically use the MCP to pull cards across boards and synthesize themes, but Trello's API doesn't expose card history or threaded comments in a structured way—the 50 tools here are mostly write-heavy (add card, add label, add attachment). If your retro workflow is about creating cards during the meeting, the MCP works. If you need to analyze patterns across ten sprints, you'll hit a wall because the read tools are shallow. The buying call: use this MCP for retro card creation and labeling, then export to a BI tool for the analysis layer.

Frequently asked

What can Switchy do with Trello MCP?

Switchy can create boards and cards, add labels and attachments, enable power-ups, and star boards for team members. With 50 tools available, the MCP covers most board management and card operations you'd do manually in Trello. It won't replace your Trello workspace — it automates repetitive setup and card creation tasks your team runs through AI workflows.

What Trello permissions does the OAuth connection need?

The Trello MCP uses OAuth2, so you'll authorize Switchy through Trello's standard permission flow. Expect it to request read and write access to your boards, cards, and members. You don't need Trello admin rights to connect, but the MCP can only touch boards your Trello account already has access to. Check the OAuth consent screen for the exact scope list.

Can Trello MCP move cards between boards or archive them?

The representative tools show card creation and attachment handling, but moving cards across boards or archiving isn't listed. If you need cross-board moves or bulk archiving, use Trello's Butler automation or API directly. The MCP is strongest at creating new cards and boards, not reorganizing existing structures. Check the full 50-tool list in Switchy for edge cases.

How is this different from just using Trello's API?

Trello's API requires you to write code, manage tokens, and handle pagination. The MCP wraps that complexity into natural-language tools your AI agents call directly. If your team already has API integrations, keep them. If you want AI to create cards from Slack threads or meeting notes without custom code, the MCP is faster.

Who on the team should connect the Trello MCP?

Whoever owns your team's Trello workspace or has access to the boards you want AI to touch. The connection uses that person's Trello permissions, so if they can't create boards, neither can the MCP. One connection per Switchy workspace is enough — all team members inherit access to the tools once it's set up.

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.