trello-mcp
Enables AI agents to inspect and update Trello boards via the Trello REST API, supporting actions like reading boards, lists, cards, and performing CRUD operations on cards and checklists.
README
<div align="center">
trello-mcp
A Codex-first Trello MCP server for AI agents
trello-mcp gives Codex and other MCP-compatible AI agents a clean, practical way to inspect and update Trello boards through Trello's official REST API.
</div>
Why This Exists
AI agents are useful when they can see the real workflow, not just the codebase. This server lets Codex connect to Trello so it can understand tasks, keep cards updated, add evidence comments, and help maintain project boards without scraping or browser automation.
It is designed for Codex first, but it works as a normal stdio MCP server in any client that supports the Model Context Protocol.
Features
| Area | Supported actions |
|---|---|
| Account | Identify the authenticated Trello member |
| Workspaces | List visible Trello workspaces |
| Boards | List open boards and inspect board metadata |
| Lists | List board columns/lists |
| Cards | List, read, search, create, update, move, comment on, and archive cards |
| Checklists | Create checklists and checklist items |
| Agent safety | Redacted errors, no committed credentials, archive-first workflow guidance |
Tool List
| Tool | Purpose |
|---|---|
trello_whoami |
Show the authenticated Trello member |
trello_list_workspaces |
List visible Trello workspaces |
trello_list_boards |
List open Trello boards |
trello_get_board |
Read board metadata |
trello_list_lists |
List board lists |
trello_list_cards |
List cards, optionally by list |
trello_get_card |
Read a card |
trello_search_cards |
Search cards by text |
trello_create_card |
Create a card |
trello_update_card |
Update card title, description, due date, or archive state |
trello_move_card |
Move a card to another list |
trello_add_comment |
Add a card comment |
trello_archive_card |
Archive a card |
trello_add_checklist |
Add a checklist to a card |
trello_add_check_item |
Add an item to a checklist |
Quick Start
git clone https://github.com/KharalDipendra/trello-mcp.git
cd trello-mcp
npm install
npm run build
Run the local verification suite:
npm run check
Trello Credentials
You need a Trello API key and token.
- Open Trello's API key page: trello.com/app-key
- Copy your API key.
- Generate a token using this URL after replacing
YOUR_API_KEY:
https://trello.com/1/authorize?expiration=never&name=trello-mcp&scope=read,write&response_type=token&key=YOUR_API_KEY
Required environment variables:
TRELLO_API_KEY=your_trello_api_key
TRELLO_TOKEN=your_trello_token
Optional environment variables:
TRELLO_BOARD_ID=default_board_id
TRELLO_IDENTITY=default
TRELLO_BASE_URL=https://api.trello.com/1
Never commit a real .env file. Keep Trello credentials in your MCP client config, shell environment, or secret manager.
Codex Setup
Build the project first:
npm install
npm run build
Then add an MCP server entry to your Codex config:
{
"mcpServers": {
"trello": {
"command": "node",
"args": ["/absolute/path/to/trello-mcp/dist/index.js"],
"env": {
"TRELLO_API_KEY": "your_trello_api_key",
"TRELLO_TOKEN": "your_trello_token",
"TRELLO_BOARD_ID": "optional_default_board_id",
"TRELLO_IDENTITY": "default"
}
}
}
}
For Windows paths, use escaped backslashes or forward slashes:
"args": ["C:/Users/you/Desktop/trello-mcp/dist/index.js"]
Multiple Trello Accounts
Run one MCP entry per Trello identity:
{
"mcpServers": {
"trello-personal": {
"command": "node",
"args": ["/absolute/path/to/trello-mcp/dist/index.js"],
"env": {
"TRELLO_API_KEY": "key_for_account_one",
"TRELLO_TOKEN": "token_for_account_one",
"TRELLO_IDENTITY": "account-one"
}
},
"trello-work": {
"command": "node",
"args": ["/absolute/path/to/trello-mcp/dist/index.js"],
"env": {
"TRELLO_API_KEY": "key_for_account_two",
"TRELLO_TOKEN": "token_for_account_two",
"TRELLO_IDENTITY": "account-two"
}
}
}
}
Standalone MCP Usage
The server communicates over stdio, so it is normally launched by an MCP client.
TRELLO_API_KEY=... TRELLO_TOKEN=... node dist/index.js
You can also run the TypeScript source during development:
TRELLO_API_KEY=... TRELLO_TOKEN=... npm run dev
Agent Safety Model
trello-mcp is intentionally simple and explicit:
- It uses Trello's REST API directly.
- It does not scrape Trello pages.
- It does not store credentials.
- It redacts credentials from Trello API error messages.
- It exposes archive tools, not permanent delete tools.
- It encourages agents to inspect board state before changing cards.
Recommended agent behaviour:
- Read the board, lists, and relevant cards first.
- Explain planned changes before writing when the workflow is sensitive.
- Add short evidence comments for meaningful card updates.
- Move cards to done only when the underlying work is actually complete.
- Prefer archiving stale cards over deleting them.
Development
npm install
npm run check
Available scripts:
| Script | Description |
|---|---|
npm run build |
Compile TypeScript into dist/ |
npm test |
Run mocked client tests |
npm run check |
Build and test |
npm run dev |
Run the MCP server from TypeScript |
npm start |
Run the compiled MCP server |
The test suite uses mocked Trello responses and does not call the live Trello API.
Project Structure
trello-mcp/
examples/
codex-mcp.json
src/
index.ts
trelloClient.ts
test/
trelloClient.test.ts
Contributing
Issues and pull requests are welcome. Keep changes generic and avoid committing board data, workspace names, real card content, tokens, or account-specific config.
License
MIT. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.