This MCP server provides tools for interacting with Trello boards, handling rate limiting, type safety, and error handling automatically. It enables seamless integration with Trello's API to manage boards, lists, cards, and workspaces.
git clone https://github.com/delorenj/mcp-server-trello
cd mcp-server-trello
cp .env.template .env
docker compose up --build
To install Trello Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @modelcontextprotocol/mcp-server-trello --client claude
npm install @delorenj/mcp-server-trello
Create a .env file in the root directory with the following variables:
# Required: Your Trello API credentials
TRELLO_API_KEY=your-api-key
TRELLO_TOKEN=your-token
# Required: Initial board ID (can be changed later using set_active_board)
TRELLO_BOARD_ID=your-board-id
# Optional: Initial workspace ID (can be changed later using set_active_workspace)
TRELLO_WORKSPACE_ID=your-workspace-id
You can get these values from:
list_workspaces toolThe server supports dynamic board and workspace selection:
TRELLO_BOARD_ID in your .env file is used as the initial board ID when the server startsset_active_board tool~/.trello-mcp/config.json)set_active_workspace{
name: 'list_boards',
arguments: {}
}
{
name: 'set_active_board',
arguments: {
boardId: "abc123" // ID from list_boards response
}
}
{
name: 'list_workspaces',
arguments: {}
}
{
name: 'set_active_workspace',
arguments: {
workspaceId: "xyz789" // ID from list_workspaces response
}
}
{
name: 'get_active_board_info',
arguments: {}
}
Fetch all cards from a specific list.
{
name: 'get_cards_by_list_id',
arguments: {
listId: string // ID of the Trello list
}
}
Retrieve all lists from the currently active board.
{
name: 'get_lists',
arguments: {}
}
Fetch recent activity on the currently active board.
{
name: 'get_recent_activity',
arguments: {
limit?: number // Optional: Number of activities to fetch (default: 10)
}
}
Add a new card to a specified list.
{
name: 'add_card_to_list',
arguments: {
listId: string, // ID of the list to add the card to
name: string, // Name of the card
description?: string, // Optional: Description of the card
dueDate?: string, // Optional: Due date (ISO 8601 format)
labels?: string[] // Optional: Array of label IDs
}
}
Update an existing card's details.
{
name: 'update_card_details',
arguments: {
cardId: string, // ID of the card to update
name?: string, // Optional: New name for the card
description?: string, // Optional: New description
dueDate?: string, // Optional: New due date (ISO 8601 format)
labels?: string[] // Optional: New array of label IDs
}
}
Send a card to the archive.
{
name: 'archive_card',
arguments: {
cardId: string // ID of the card to archive
}
}
Add a new list to the currently active board.
{
name: 'add_list_to_board',
arguments: {
name: string // Name of the new list
}
}
Send a list to the archive.
{
name: 'archive_list',
arguments: {
listId: string // ID of the list to archive
}
}
Fetch all cards assigned to the current user.
{
name: 'get_my_cards',
arguments: {}
}
Move a card to a different list.
{
name: 'move_card',
arguments: {
cardId: string, // ID of the card to move
listId: string // ID of the target list
}
}
Attach an image to a card directly from a URL.
{
name: 'attach_image_to_card',
arguments: {
cardId: string, // ID of the card to attach the image to
imageUrl: string, // URL of the image to attach
name?: string // Optional: Name for the attachment (defaults to "Image Attachment")
}
}
List all boards the user has access to.
{
name: 'list_boards',
arguments: {}
}
Set the active board for future operations.
{
name: 'set_active_board',
arguments: {
boardId: string // ID of the board to set as active
}
}
List all workspaces the user has access to.
{
name: 'list_workspaces',
arguments: {}
}
Set the active workspace for future operations.
{
name: 'set_active_workspace',
arguments: {
workspaceId: string // ID of the workspace to set as active
}
}
List all boards in a specific workspace.
{
name: 'list_boards_in_workspace',
arguments: {
workspaceId: string // ID of the workspace to list boards from
}
}
Get information about the currently active board.
{
name: 'get_active_board_info',
arguments: {}
}
The server implements a token bucket algorithm for rate limiting to comply with Trello's API limits:
Rate limiting is handled automatically, and requests will be queued if limits are reached.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.