solidtime-mcp
Related Servers
Alternatives to solidtime-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for SolidTime — the open-source time tracking app. Enables start/stop timers, manage time entries, projects, clients, tags, and tasks directly from MCP-compatible clients.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage Toggl Track time entries, timers, projects, clients, tags, and reports through a self-hosted stdio server.144 npmMIT
- AlicenseAqualityBmaintenanceConnects MCP clients to a self-hosted Syncthing instance's GUI REST API for reading configuration, folders, devices, and connections, plus gated write actions like adding or patching folders and devices, scanning, pausing, restarting, and shutting down. Supports stdio and localhost-only Streamable HTTP with API-key auth, dry-run write previews, redaction of secrets, caching, and rate limiting.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.Apache 2.0
- 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.12116 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to query and manage a club-management system's documented JSON API via stdio, covering members, contacts, events, lists, registrations, invoices, and bookings with optional gated write, delete, and send operations and support for multiple club profiles.MIT
TDQS
Scored across 53 tools
Most tool families are separated by clear resources, but several pairs overlap significantly: timer_start vs time_entry_create, timer_stop vs time_entry_update, and members_list vs memberships vs member_* operations. Generic action-based tools also sit alongside dedicated CRUD tools, so an agent must read descriptions carefully to choose correctly.
All tools use snake_case with the solidtime_ prefix, but the naming convention is mixed: some are verb_noun (project_create, time_entry_delete), while many are noun-only action bundles (tags, clients, tasks, reports, invoices). Plural/singular forms are also inconsistent, such as projects_list versus project_get.
With 53 tools, the surface is very large for a single MCP server, even one covering a full time-tracking product. Many domains are represented through both dedicated CRUD tools and generic action-based tools, which likely inflates the count and increases selection burden.
Coverage is broad and deep across the domain: organizations, users, members, projects, tasks, clients, tags, time entries, timers, reports, invoices, charts, import/export, and metadata lookups. CRUD/lifecycle operations are present for the main resources, with few obvious dead ends.