Advanced Trello MCP Server
This MCP server lets an AI client manage Trello boards, lists, cards, labels, and actions, with batch operations and a resilient API layer.
List accessible boards with filters, limits, optional lists, and organization data.
Create, update, archive, move, and inspect lists; get list actions, board, and cards; bulk archive or move all cards in a list.
Create single or batch cards; move single or batch cards; add single or batch comments; fetch tickets/cards by list; archive single or batch cards.
Create labels singly or in batches; add labels to cards singly or in batches; get, update, delete labels; update label name/color.
Get, update, delete actions and retrieve action reactions.
Note: the README advertises card update and attachment metadata/download tools, but those tools are not present in the provided server schema.
Provides comprehensive integration with Trello API, offering 44+ tools across multiple categories including Lists, Cards, Labels, Actions, and Boards management. Capabilities include creating/updating lists, managing cards, handling labels, tracking action history, and accessing boards with enterprise-grade features like batch operations.
Used as the implementation language with strict typing for the MCP server, providing type safety throughout the codebase.
Implements schema validation for all inputs and outputs in the MCP server, ensuring type safety and proper data handling.
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., "@Advanced Trello MCP Server move all cards from 'In Progress' to 'Review' list on the Project X board"
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.
π Advanced Trello MCP Server
Enhanced Model Context Protocol Server for Trello integration with Cursor AI
Production-hardened API layer, batch tools, and attachment downloads
TypeScript Trello API MCP Protocol License
π Overview
This is an enhanced version of the Trello MCP Server that provides comprehensive integration between Trello and Cursor AI (and similar MCP clients). It includes ~35 tools across boards, lists, cards, labels, and actions, plus a reliable HTTP layer suited to heavy or sequential API use.
Related MCP server: Atlassian Trello MCP Server
β¨ Features
π‘οΈ Reliability (production-tested)
All Trello calls (MCP resources and tools) go through a shared client in src/utils/api.ts:
HTTPS keep-alive β reuses TLS connections (helps avoid CloudFront / CDN connection churn on burst traffic)
**fetchWithRetry** β ~60s timeout, exponential backoff with jitter (up to 7 attempts), retries on network errors and 5xxSliding-window rate limit β ~80 requests / 10s (mutex-protected)
429 handling β respects
Retry-Afterwhen present
π― API coverage (current)
Area | Tools | Notes |
Lists | 10 | Full list lifecycle, bulk card moves |
Cards | 12 | Batch create/move/archive/comments, attachments |
Labels | 8 | Including batch add |
Actions | 4 | Get / update / delete action, list reactions |
Boards | 1 | List accessible boards |
π§ Other
TypeScript + Zod validation on tool inputs
Batch operations β fewer round-trips for agents (
create-cards,move-cards,archive-cards,add-comments, etc.)Attachment pipeline β list metadata + optional download to disk (see below)
π Quick Start
Prerequisites
Node.js 18+
Trello API Key and Token
Cursor (or any MCP client)
Installation
Clone the repository
git clone https://github.com/adriangrahldev/advanced-trello-mcp-server.git
cd advanced-trello-mcp-serverInstall dependencies
npm installBuild the project
npm run buildConfigure environment variables
export TRELLO_API_KEY="your_api_key"
export TRELLO_API_TOKEN="your_api_token"Configure Cursor MCP Add to your
~/.cursor/mcp.json(paths adjusted for your machine):
π οΈ Available Tools
π Lists (10)
get-listsβ Lists on a boardcreate-list/update-list/archive-listmove-list-to-boardget-list-actions/get-list-board/get-list-cardsarchive-all-cards-in-list/move-all-cards-in-list
π― Cards (12)
create-cardβ Optional**due** and**start**(ISO 8601)create-cardsβ Batch create; each card may include**due**/**start**update-cardβ Name and/or descriptionmove-card/move-cardsadd-comment/**add-comments**(batch comments on multiple cards)get-tickets-by-listarchive-card/archive-cards**get-card-attachments**β Metadata +commentContext(e.g. screenshots on comments)**download-card-attachments**β Downloads files to a new private directory under the server's download root (numbered files +_manifest.json). File URLs often require OAuth-styleAuthorizationheader (not query-string key/token); this tool handles that.
Safe attachment download locations
download-card-attachments never accepts an arbitrary local path. The optional
savePath argument is now a folder label, for example card-photos. It must
contain 1β64 ASCII letters, digits, underscores or hyphens and start with a letter
or digit. Absolute paths, nested paths and traversal components are rejected.
Omit it to use the label attachments.
The server creates a unique directory for every invocation, including repeated or
concurrent downloads, and returns its absolute location in savedTo. The default
root is trello-downloads under the server's working directory. Operators can set
TRELLO_DOWNLOAD_ROOT in the server environment to choose a dedicated root; MCP
clients cannot override it. Relative configuration is resolved at tool registration.
Migration: Replace calls such as savePath: "/tmp/card-photos" with
savePath: "card-photos", configure TRELLO_DOWNLOAD_ROOT on the server if needed,
and consume the returned savedTo rather than assuming a fixed output directory.
Root components and output directories must be real directories, not symbolic links. Use a canonical path if your platform aliases directories through symlinks. Files (including the manifest) are created exclusively and never overwrite existing files or follow existing file links. New directories use private permissions and new files use owner-only permissions where supported by the OS. Keep the configured root and its ancestors controlled by the server operator, not writable by untrusted local users. These safeguards protect against untrusted MCP input; they do not isolate the process from a malicious local user who can rename its directories. Failed downloads may leave partial files in their unique directory; no success response is returned in that case.
π·οΈ Labels (8)
create-label/create-labelsadd-label/add-labelsget-label/update-label/delete-label/update-label-field
π Actions (4)
get-actionβ With optional display/entities/member paramsupdate-action/delete-actionget-action-reactions
π’ Boards (1)
get-boards
β Why is an old Pull Request still βopenβ on GitHub?
GitHub marks a PR as Merged only when you merge that PR (green βMerge pull requestβ button), or when the PR branch is merged in a way GitHub links to the PR.
If you cherry-picked, copied files, or merged locally into main and pushed main, the code is on the repo but the PR stays open until you:
Close the PR manually β add a comment such as: βLanded on
mainvia commit ** β thanks!βOr use GitHubβs merge flow next time so the PR closes automatically.
Conflicts on fork-based PRs are normal; resolving on your machine and pushing main is fine β just close the PR afterward so contributors know itβs done.
π Roadmap
Broader Trello API coverage (checklists, members, webhooks, search, etc.) is planned. PRs welcome.
π§ Development
Project structure
advanced-trello-mcp-server/
βββ src/
β βββ index.ts
β βββ tools/ # boards, lists, cards, labels, actions
β βββ types/
β βββ utils/ # api.ts β fetchWithRetry, keep-alive, rate limit
βββ build/
βββ scripts/build.js
βββ package.json
βββ README.mdBuilding
npm run build # TypeScript + shebang on build/index.js
npm test # Compile + offline regression tests (Node.js test runner)
npm run compile # tsc onlyCross-platform build (Windows / macOS / Linux): compiles TS, adds #!/usr/bin/env node, sets execute bit on Unix.
π€ Contributing
Fork the repository
Branch (
git checkout -b feature/...)Commit (Conventional Commits encouraged)
Open a Pull Request
If the maintainer merges your work outside the GitHub PR UI, they may close the PR with a link to the landing commit β that does not mean your contribution wasnβt accepted.
π API documentation
Tools follow the Trello REST API. Inputs are validated with Zod.
π Troubleshooting
Issue | What to check |
Credentials |
|
Tool not found | Rebuild ( |
| Retry layer should help; sustained 429 β slow down workflows |
Attachment download 401 | Use |
π License
MIT β see LICENSE.
π Acknowledgments
Original Trello MCP Server β yairhaimo/trello-mcp-server
Trello API Β· MCP Β· Cursor
Built with β€οΈ for the Cursor AI community
Available Tools
32 toolsadd-commentD
Inputs: cardId (required), text (required).
add-commentsD
Inputs: comments (required).
add-labelD
Inputs: cardId (required), labelId (required).
add-labelsD
Inputs: items (required).
archive-all-cards-in-listD
Inputs: listId (required).
archive-cardD
Inputs: cardId (required).
archive-cardsD
Inputs: cardIds (required).
archive-listD
Inputs: listId (required), archived (required).
create-cardD
Inputs: name (required), listId (required), description.
create-cardsD
Inputs: cards (required).
create-labelD
Inputs: boardId (required), name (required), color (required).
create-labelsD
Inputs: labels (required).
create-listD
Inputs: boardId (required), name (required), position.
delete-actionD
Inputs: actionId (required).
delete-labelD
Inputs: labelId (required).
get-actionD
Inputs: actionId (required), display, entities, fields, +4 more.
get-action-reactionsD
Inputs: actionId (required), member, emoji.
get-boardsD
Inputs: fields, filter, limit, organization, +1 more.
get-labelD
Inputs: labelId (required), fields.
get-list-actionsD
Inputs: listId (required), filter.
get-list-boardD
Inputs: listId (required), fields.
get-list-cardsD
Inputs: listId (required), fields, filter.
get-listsD
Inputs: boardId (required).
get-tickets-by-listD
Inputs: listId (required), limit.
move-all-cards-in-listD
Inputs: listId (required), destinationBoardId (required), destinationListId (required).
move-cardD
Inputs: cardId (required), listId (required), position.
move-cardsD
Inputs: cards (required).
move-list-to-boardD
Inputs: listId (required), boardId (required).
update-actionD
Inputs: actionId (required), text (required).
update-labelD
Inputs: labelId (required), name, color.
update-label-fieldD
Inputs: labelId (required), field (required), value (required).
update-listD
Inputs: listId (required), name, closed, pos, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 32 tools
Multiple tools have unclear boundaries, such as add-comment vs add-comments, archive-card vs archive-cards, and create-card vs create-cards, which could cause confusion. While some tools target distinct resources (e.g., get-boards vs get-list-cards), the overlapping singular/plural pairs and vague purposes like delete-action vs update-action reduce clarity.
Tool names follow a mostly consistent verb_noun pattern with hyphens, such as create-card, get-boards, and update-label. However, there are minor deviations like get-tickets-by-list (which uses 'tickets' instead of 'cards') and inconsistent handling of plurals (e.g., add-comment vs add-comments), slightly affecting predictability.
With 32 tools, the count is too high for the Trello domain, leading to redundancy and bloat. Many tools could be consolidated (e.g., singular and plural versions), making the set feel heavy and overwhelming for typical agent workflows, despite covering a broad scope.
The tool set covers core CRUD operations for boards, lists, cards, labels, and actions, but there are notable gaps, such as missing tools for managing board settings or user permissions. The inclusion of redundant tools (e.g., multiple archive/move variants) does not fill these gaps, leaving the surface somewhat incomplete for advanced Trello management.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoβ¦
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides tools for interacting with Trello boards, enabling seamless management of cards, lists, and activities while handling rate limiting and type safety.35MIT
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server for Trello that works with any MCP-compatible client -- Claude Desktop, Claude Code, Gemini CLI, and more. Provides 46 tools covering boards, cards, lists, labels, checklists, attachments, members, custom fields, and search.45187 npm3MIT
- AlicenseAqualityDmaintenanceA Trello MCP server that enables AI assistants to manage boards, cards, and lists via the Model Context Protocol.2537 PyPI2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with access to Trello's functionality. This server enables AI models to interact with Trello boards, lists, and cards programmatically.1MIT