tempo-mcp-server and mcp-toggl
These are competitors, as both are MCP servers that integrate with different time-tracking services, Tempo (Jira) and Toggl Track, respectively.
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.
About mcp-toggl
verygoodplugins/mcp-toggl
MCP server for Toggl Track integration with intelligent caching and reporting tools
Implements an LRU cache with configurable TTL and size limits to minimize Toggl API calls, achieving >95% cache hit rates while automatically hydrating time entries with project/workspace/client metadata. Designed as an MCP server for Claude Desktop and Cursor, it exposes tools for timer control, daily/weekly/project reporting, and workspace management with structured JSON output compatible with Automation Hub workflows. Uses Basic Auth with Toggl API tokens and includes automatic retry logic with exponential backoff to handle rate limiting.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work