Reference

trello-mcp is a self-hostable, MIT-licensed open-source project. It exposes the same Trello tool catalog through local stdio and Streamable HTTP while leaving deployment, credentials, logs, and network boundaries under the operator’s control.

Pre-1.0, with documented contracts

Registered tool names and input schemas, curated behavior labels, client recipes, and security boundaries are treated as public contracts. Changes to those surfaces should be documented, regenerated, and tested together.

Technical reference

ConfigurationReview every runtime and Compose setting, default, and deployment boundary.

Tool catalogBrowse every registered tool, input schema, behavior label, scope, and result shape.

API coverageSee which Trello REST API groups are supported, partial, deferred, or out of scope.

Repository policies

ContributingSet up a checkout, follow the Trello tool pattern, and run the project checks.

Reporting issues and supportChoose the right channel and prepare a safe, reproducible report.

Security policySee supported versions and report vulnerabilities through the private channel.

Documentation contracts

• The tool catalog reads names, descriptions, and input definitions from the same registered tool definitions and Zod schemas used by the server. Curated categories and behavior labels are checked to cover every tool.
• API coverage records supported, partial, deferred, and out-of-scope Trello REST API groups without implying that every endpoint is exposed.
• Client compatibility records dated connection, discovery, and live-validation evidence separately from documentation-reviewed recipes.

Canonical long-form documentation remains under docs/. CONTRIBUTING.md, SUPPORT.md, and SECURITY.md remain canonical for their generated policy pages. Run corepack pnpm docs:tools after changing those sources; edit generated website pages through their canonical source.

Project and release resources

• Releases and the changelog record published versions and project changes.
• Issues track bugs, focused feature requests, and documentation fixes.
• The public roadmap shows current project direction.
• The MIT License defines reuse and distribution terms.
• llms.txt provides a generated, machine-readable index of the public documentation.

Documentation and support

• Security & Data covers credentials, transports, logs, attachment uploads, and safer tool use.
• Operations covers inspection, exact-version upgrades, rollback, credential rotation, and shutdown.
• Troubleshooting covers startup, client, Docker, Trello API, rate-limit, and attachment failures.
• FAQ explains hosting, official status, data access, destructive tools, privacy, and support boundaries.
• Reporting issues and support explains what belongs in a public issue and what must instead use private vulnerability reporting.

Normal tests and website checks are offline and require no Trello credentials. The opt-in live smoke and regression suites are guarded maintainer workflows for a confirmed disposable Trello board; they are not normal first-run verification.

Independent project and official alternative

trello-mcp is an independent, community-maintained project. It is not an official Trello or Atlassian product, service, or MCP implementation, and it is not affiliated with, endorsed by, or sponsored by Trello or Atlassian.

For Trello’s official managed service, use the current Trello MCP documentation.

Open source and independently maintained

Browse the source, report an issue, or follow the project on GitHub.

Star on GitHubMIT licensedSelf-hostableNode 24