Overview
What is Trello MCP Server?
A Model Context Protocol server that exposes Trello API functionality as MCP tools, enabling AI assistants to interact with Trello boards and cards programmatically. It is intended for developers building AI‑powered workflows that need to read Trello data.
How to use Trello MCP Server?
Clone the repository, install dependencies with pnpm or npm, copy .env.example to .env, and set the required environment variables (Trello API key, token, and base URL). Start the server with pnpm start or npm start. Once running, AI clients can call the get_trello_cards_by_board_id tool with a board ID to retrieve all cards from that board.
Key features of Trello MCP Server
- Retrieves all cards from a specified Trello board.
- Single MCP tool:
get_trello_cards_by_board_id. - Written in TypeScript with Zod input validation.
- Auto‑reload during development (
pnpm dev). - Easy to extend with new Trello API tools.
Use cases of Trello MCP Server
- AI assistant fetching task lists from a Trello project board.
- Automated reporting of card statuses to a chat agent.
- Integrating Trello data into larger MCP‑based workflows.
FAQ from Trello MCP Server
What Trello operations does the server support?
Currently, the server only provides the get_trello_cards_by_board_id tool to retrieve all cards from a given board. Additional tools can be added following the guide in the README.
What are the runtime requirements?
Node.js (version specified in .nvmrc), pnpm or npm, and a Trello API key and token obtained from Trello’s Developer Portal.
How do I get my Trello API credentials?
Go to the Trello Developer Portal (https://developer.atlassian.com/cloud/trello/guides/rest-api/api-introduction/) to generate an API key and a token.
Where does the server run?
It runs locally as a Node.js process. Data is fetched in real time from Trello’s public API; no local storage of Trello data is mentioned.
What transport and authentication are used?
The server uses standard MCP tool calls. Authentication to Trello is handled via the API key and token supplied in the environment variables. No other transports (e.g., stdio, HTTP) are specified in the README.
