io.github.tracegazer/clockify-mcp
Clockify Time Tracking
Is the Clockify Time Tracking MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-10-31.
Clockify time-tracking MCP: 112 tools across 18 domains, read-only by default with opt-in writes.
needs mcp<2 probed 2026-11-14 · unchanged since 2026-10-31
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-10-31.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' clockify-mcp@0.3.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- clockify 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/tracegazer/clockify-mcp
- Website
- https://github.com/tracegazer/clockify-mcp
- Registry
- active, updated 2026-06-09 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| list_time_entries | 446 | 6 % |
| list_projects | 411 | 5 % |
| list_tags | 300 | 4 % |
| list_tasks | 296 | 4 % |
| get_shared_report | 271 | 3 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Yandex Tracker (lite) io.github.tonysafonov/yandex-tracker-mcp-lite · alive
- ASAM ODS odsbox jaquel MCP Server io.github.totonga/odsbox-jaquel-mcp · alive
- TourClaim by Copernican io.github.tourclaim/tourclaim · needs args
- Swiss Public Transport io.github.tpjnorton/swiss-public-transport-mcp · needs mcp<2
- InvGate Service Desk io.github.tracegazer/invgate-service-desk-mcp · needs mcp<2
- Paradex Trading io.github.tradeparadex/mcp-paradex-py · install failed
- BioMapper io.github.trentleslie/biomapper · alive
- Apple TV MCP io.github.trevor-nichols/appletv-mcp · install failed
Servers that mention clockify or tracking or time.
- Clockify MCP by usefulapi io.usefulapi/clockify · timeout
- aTars MCP ai.aarna/atars-mcp · server error
- AlphaCreek SEC Filings MCP ai.alphacreek/alphacreek-mcp · alive
- Teamwork ai.b77/teamwork · needs auth
- Time ai.b77/time · needs auth
- BetterPost ai.betterpost/server · alive
- ai.boundaryai/boundaryai · needs auth
- Bring Your AI ai.bringyour/bringyour · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-31 07:40 | needs mcp<2 | 1.7 s | 48 | 15k | 8.1k |
| 2026-10-17 06:19 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'