MCP server for the Trello REST API – manage boards, lists, cards, labels, checklists and more
An MCP server for the Trello REST API. Manage boards, lists, cards, labels, checklists, and more from any MCP-compatible client. ------|-------------| | List all boards for the authenticated user | | Get details of a single board | | Get all lists on a board | | Create a new list on a board | | Get all cards in a list | | Get all cards on a board | | Get details of a single card | | Create a new…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
An MCP server for the Trello REST API. Manage boards, lists, cards, labels, checklists, and more from any MCP-compatible client. ------|-------------| | List all boards for the authenticated user | | Get details of a single board | | Get all lists on a board | | Create a new list on a board | | Get all cards in a list | | Get all cards on a board | | Get details of a single card | | Create a new card in a list | | Update one or more fields on a card | | Move a card to a different list/board | |…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.