mcp-server-trello and tempo-mcp-server
These tools are ecosystem siblings, as both are distinct Model Context Protocol (MCP) servers, with one providing tools for Trello and the other for Tempo worklogs in Jira, rather than directly competing or being used together.
About mcp-server-trello
delorenj/mcp-server-trello
A Model Context Protocol (MCP) server that provides tools for interacting with Trello boards.
Built in TypeScript with automatic rate limiting (respects Trello's 300/10s per API key and 100/10s per token thresholds), this server enables comprehensive board operations including card data extraction with checklists, attachments, labels, and comments, plus file attachment uploads from URLs. Runs on the Bun runtime for 2.8-4.4x performance improvement while maintaining backward compatibility with `npx` and `npm`, and supports dynamic board/workspace switching without server restarts via persistent configuration.
About tempo-mcp-server
ivelin-web/tempo-mcp-server
MCP server for managing Tempo worklogs in Jira
Implements the Model Context Protocol (MCP) to expose Tempo's worklog API through a stdio transport, enabling Claude, Cursor, and compatible AI clients to log time and manage Jira worklogs via natural language. Supports both basic and OAuth 2.0 authentication for Jira, bulk operations, and optional Tempo account linking through custom fields. Available as an npm package for zero-installation deployment or as a local clone for development.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work