UseHourly
Related Servers
Alternatives to UseHourly
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for time tracking and billing that allows freelancers to control timers, manage projects, and export invoices via natural language in any MCP-compatible AI assistant.0MIT
- FlicenseNot gradedqualityBmaintenanceEnables time tracking and invoicing through natural conversation with MCP clients like Claude or ChatGPT, allowing users to log work hours, query unbilled time, and draft invoices, with a minimal web app for settings, CSV import, and Stripe-powered billing.-
- AlicenseNot gradedqualityBmaintenanceA local, UI-less timesheet application served via MCP, letting AI assistants log hours, correct entries, generate monthly reports, and compute Finnish-holiday-aware working-time math for invoicing.AGPL 3.0
- AlicenseCqualityDmaintenanceA production-ready, fully anonymized Model Context Protocol (MCP) server for TimeIQ time tracking. It allows LLM agents to view and manage time entries, projects, clients, reports, invoices, expenses, services, and timesheets via a secure stdio transport.1008 npmMIT
- AlicenseAqualityCmaintenanceOfficial MCP server for Timebook (usetimebook.com) — time tracking, invoicing, and bookkeeping for freelancers and solo LLCs. Manage clients and projects, start/stop timers, and log, update, and delete time entries. Stdio via the @squidcode/timebook npm CLI; a hosted OAuth endpoint also exists at https://usetimebook.com/mcp.1239 npm2MIT

DuTemps MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables coding agents such as Claude Code or Codex to run and stop the timer, log, correct, delete and restore time entries, read settings, projects, clients, tags, entries and reports, and preview invoices or create and edit invoice drafts. It communicates over stdin/stdout without opening a port, writes to the same audited database as the app, and leaves issuing or voiding invoices to the user in the app.MIT
TDQS
Scored across 30 tools
Most tools target distinct resources and actions, but the time-entry trio (log_time, log_time_on_days, set_day_totals) overlaps enough that an agent must read carefully to pick correctly, and list_entries/project_totals/annual_report cover similar ground at different scopes. Descriptions do resolve most ambiguity, so boundaries are workable.
Predominantly consistent snake_case verb_noun (list_projects, create_invoice, update_entry, archive_client). A handful of noun-only names (whoami, project_totals, annual_report, next_invoice_number) deviate but remain readable and predictable in intent.
30 tools is on the heavy side for the stated scope and crosses the point where the set starts to feel large. The domain (clients, projects, entries, invoices, timers, reports) does justify many of them, but a few entry-writing tools could plausibly be consolidated.
Covers the full lifecycle: CRUD-ish for clients, projects, entries and invoices plus timers, batch logging, merging, and multiple reporting views. Archive/unarchive, invoice numbering, duration parsing, and paid-tracking round out the surface with no obvious dead ends.