mcp -trello

This MCP server provides a Trello integration toolkit that lets you interact with Trello boards, lists, and cards through a structured, type-safe API. It supports fetching full card data (including checklists, attachments, labels, members, and comments), creating and updating cards, managing comments, and attaching files from URLs. Built with a modern MCP SDK architecture and designed to respect Trello's rate limits, the server offers built-in input validation and comprehensive error handling to simplify integration with your applications or automation workflows. You can switch between boards and workspaces dynamically, and you can export or present data in markdown format for readable reports and dashboards.

To use it, start the server via Bun (bunx) or through npm/npx as shown in the installation instructions. Provide your Trello API credentials (API key and token) via environment variables (TRELLO_API_KEY and TRELLO_TOKEN). Once running, you can call endpoints to fetch board data, manipulate cards, manage comments, and attach files. The server also supports multiple boards and workspaces, allowing you to adapt to different Trello setups without restarting the service.

Prerequisites:

• Node.js/npm or Bun ecosystem ( Bun is recommended for this server )
• Access to Trello API credentials (API key and token)

Quick start options:

1. Quick Bun-based setup (fastest):

# Prerequisites: Bun installed (via bun.sh or mise as described in the README)
# Install and run via bunx
bunx @delorenj/mcp-server-trello

2. If you prefer using npx/pnpx (no global install required):

npx @delorenj/mcp-server-trello

3. Docker (containerized):

# After cloning and configuring .env, run with docker-compose
docker compose up --build

4. npm install (global) alternative:

npm install -g @delorenj/mcp-server-trello
npx mcp-server-trello

Environment setup (example):

# Create a .env file or export env vars directly
export TRELLO_API_KEY=your-api-key
export TRELLO_TOKEN=your-token

Configuration actions:

• If using Bunx, set env vars in your MCP config as shown in the example JSON.
• You can also configure a registry-based installation as described in the README (MCP Registry) if supported by your client.

Docker-specific notes:

• Copy the .env.template to .env and fill in Trello credentials before building the image.
• Use docker compose to manage the service lifecycle and dependencies.

Tips and common issues:

• Ensure your Trello credentials have the necessary permissions for the API operations you intend to perform (read/write as needed).
• When using multi-board support, you can omit the default board ID and pass boardId per API call to switch boards on the fly.
• If you encounter rate-limit errors from Trello, verify your API key and token, and consider spreading requests over time or using the built-in rate limiting features.
• The server persists active board and workspace selections to ~/.trello-mcp/config.json; back up this file if you rely on a specific setup.
• For Claude or headless environments, the README mentions Smithery integration; ensure your CLI tooling is available in the execution environment if choosing that path.
• When exporting data to markdown, you can leverage that feature to create readable reports for stakeholders.