Trello
A web-based, kanban-style, list-making application.
Verdict
Common use cases
- Draft cards from customer feedback threads
- Move tasks between sprint lists automatically
- Attach meeting recordings to project cards
- Summarize board progress for standups
- Triage support requests into priority lists
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
Creates a new card in a trello list; `idlist` is required, and if `idcardsource` is used, the source card must be accessible.
- 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 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 a specified trello checklist; this action does not update existing check items.
- Add check item to checklist
Adds a new check item to an existing checklist on a specific trello card.
- 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, empty list on a specified, existing trello board, typically used as a column or category for organizing cards.
- 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 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
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Trello in the MCP directory and click Connect. 3. You'll be redirected to Trello's OAuth consent screen — sign in with your Trello account if prompted. 4. Review the requested scopes: Trello will ask for read and write access to your boards, cards, and lists. 5. Click Authorize to grant permission; Switchy will store the token securely. 6. You'll return to Switchy with a confirmation that Trello is connected. 7. Open any Project and type '@Trello' in the chat to verify the connection — ask it to list your boards or describe a specific card. 8. If the MCP responds with board names or card details, setup is complete and you can start invoking tools.
What teammates see: by default, memories from Trello are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Draft Cards from Notes
@Trello Create three cards in the 'Backlog' list from these notes: [paste notes]. Add 'feature-request' labels and set due dates for next sprint.
Move Completed Tasks
@Trello Find all cards in the 'In Progress' list marked complete and move them to 'Done'. List the card names you moved.
Attach Context Files
@Trello Attach this Figma link [paste URL] to the card titled 'Homepage Redesign' and add a comment explaining the latest changes.
Summarize Sprint Status
@Trello Show me how many cards are in 'To Do', 'In Progress', and 'Done' on the Q1 Launch board, grouped by label.
Triage Incoming Requests
@Trello Review the 'Requests' list and recommend which cards should move to 'High Priority' based on their descriptions and labels.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@trello show me all cards in the 'Q1 Launch' board that are due this week and assigned to the design team
Found 7 cards in 'Q1 Launch' due within the next 7 days with design team members assigned: • 'Homepage mockups v3' (due Feb 14) – assigned to Sarah Chen, in 'In Progress' list • 'Mobile nav prototype' (due Feb 15) – assigned to Marcus Lee, in 'Review' list • 'Icon set finalization' (due Feb 16) – assigned to Sarah Chen, in 'To Do' list • 'Brand guidelines update' (due Feb 17) – assigned to both Sarah Chen and Marcus Lee, in 'In Progress' list • 'Marketing site wireframes' (due Feb 18) – assigned to Marcus Lee, in 'Blocked' list • 'App store screenshots' (due Feb 19) – assigned to Sarah Chen, in 'To Do' list • 'Onboarding flow revisions' (due Feb 19) – assigned to Marcus Lee, in 'Review' list This is an illustrative example showing how the MCP would aggregate card data across lists with date and member filtering.
This example demonstrates the MCP's read capabilities for filtering and searching cards. Requires OAuth scope to access the specific board. The actual response structure depends on your Trello workspace organization—board names, member assignments, and list structures vary by account. Rate limits apply when querying multiple boards or large card sets.
@trello create a new card in the 'Sprint Backlog' list titled 'Fix mobile checkout flow' with a due date of next Friday and assign it to Alex
Created card 'Fix mobile checkout flow' in the 'Sprint Backlog' list: • Card ID: 65f8a2b1c3d4e5f6a7b8c9d0 • Due date: February 23, 2024 • Assigned to: Alex Rodriguez • List: Sprint Backlog (board: Engineering Q1) • URL: trello.com/c/aBcDeF12 The card has been added to your board and Alex will receive a notification about the assignment. This is an illustrative example of the card creation response—actual IDs and URLs will differ.
This example shows the MCP's write capability for creating and assigning cards. Requires OAuth write permissions. The MCP will create the card immediately—there's no undo through the AI interface, so confirm details before running. Member assignment only works if 'Alex' matches a board member's name or username exactly. Due dates are interpreted in your Trello account's timezone.
@trello review all cards in the 'Done' list from the last sprint and draft a summary of completed features for our release notes
Analyzed 14 cards moved to 'Done' in the last sprint (Feb 5-16). Here's a release notes summary: **New Features:** • Two-factor authentication for enterprise accounts (cards: #847, #851) • Bulk export functionality for reports (card: #823) • Dark mode support across mobile apps (cards: #809, #812, #815) **Improvements:** • Reduced API response time by 40% through caching optimizations (card: #834) • Enhanced search with fuzzy matching (card: #828) • Streamlined onboarding flow—3 steps instead of 7 (card: #841) **Bug Fixes:** • Fixed checkout timeout on slow connections (card: #856) • Resolved calendar sync issues with Outlook (cards: #844, #849) • Corrected currency formatting for EU locales (card: #838) This synthesis combines Trello card data with AI reasoning to group and summarize completed work by category.
This example showcases the MCP's ability to retrieve card data that the AI can then analyze and synthesize. The AI interprets card titles, descriptions, and labels to categorize work—accuracy depends on how consistently your team writes card content. Requires read access to the board. The MCP fetches the raw data; the AI performs the grouping and drafting logic.
Use-case deep-dives
When Trello MCP beats a dedicated ticketing system for small support teams
A 6-person support team handling 40-60 tickets a day can route faster in Trello than in Zendesk if they already live in Trello boards. The MCP's 50 tools let you create cards, attach screenshots, and label by urgency without leaving your AI workspace. The OAuth2 flow means each agent authenticates once and the workspace inherits their board access. This works until you hit ~100 tickets a day or need SLA tracking—at that scale, Trello's search gets slow and you're missing the audit trail a real ticketing system provides. If your team is already triaging in Trello and tickets stay under three figures daily, the MCP keeps you in one tool instead of context-switching to a heavier platform.
Trello MCP shines when your roadmap lives in cards, not issues
A 12-person product team spread across three time zones can run async sprint planning if their backlog is already in Trello. The MCP lets you bulk-create cards from meeting notes, clone boards for the next quarter, and star high-priority boards for each PM—all from a shared AI workspace where the team is already drafting specs. The 'add attachment to card' tool means you can drop Figma links or research PDFs directly into cards during planning sessions. This breaks down if your eng team is in Jira or GitHub Issues; the MCP doesn't sync across tools, so you'll duplicate work. If your entire workflow is Trello-native and you need to move fast without opening 12 browser tabs, the MCP is the right call for sprint prep.
When Trello MCP automates recurring event logistics better than spreadsheets
A 3-person events team running monthly webinars can template their checklist in Trello and use the MCP to clone boards and populate cards for each new event. The 'add board' and 'add card' tools let you script the entire setup—speaker outreach, promo timeline, tech check—so you're not manually recreating 40 tasks every month. OAuth2 means the whole team sees the same boards without sharing a service account. This works until you need calendar integration or budget tracking; Trello's power-ups help, but the MCP doesn't expose those directly. If your event logistics are checklist-heavy and you're tired of copying Google Sheets, the MCP turns Trello into a repeatable ops engine for teams under 10 people.
Frequently asked
What can Switchy do with Trello through this MCP?
Switchy can create and manage boards, cards, labels, and attachments across your Trello workspace. The MCP exposes 50 tools covering board setup, card operations, power-up management, and member actions. Your AI agents can automate card creation from meeting notes, sync project updates across boards, or attach files without leaving the conversation.
Do I need admin access to connect Trello via OAuth?
You need a Trello account with access to the boards you want Switchy to manage. OAuth2 will prompt you to authorize specific permissions — typically read/write access to boards, cards, and members. You don't need workspace admin rights unless you're enabling power-ups or modifying workspace-level settings through the MCP.
Can the Trello MCP move cards between boards or archive them?
The MCP focuses on creating boards, cards, labels, and attachments. Moving cards between boards or archiving them isn't shown in the representative tools, so you'll likely need to handle those actions directly in Trello or via a custom API call. Check the full tool list in Switchy's integration settings to confirm what's supported.
Why use this instead of Trello's API or Butler automation?
Switchy's MCP lets your AI agents interact with Trello conversationally — no webhook setup or Butler recipe syntax required. You describe what you want in natural language, and the agent picks the right tool. It's faster for ad-hoc tasks and integrates with your other MCPs, so an agent can pull GitHub issues and create Trello cards in one step.
Who on the team should connect the Trello integration?
Anyone who needs AI agents to create or update Trello content. Each team member connects their own Trello account via OAuth, so agents act with that person's permissions. If you want agents to manage boards across the workspace, connect an account that has access to all relevant boards.