ZeroHrs MCP server
OfficialRelated Servers
Alternatives to ZeroHrs MCP server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables Codex to create, update, review, and present live SceneBoard boards after user approves a one-time connection.-
- AlicenseDqualityBmaintenanceEnables Codex to delegate implementation tasks to Kimi Code while managing server lifecycle and authentication automatically.111MIT
- AlicenseAqualityBmaintenanceEnables Codex to use an authenticated ChatGPT Web session as a reasoning and coding backend through isolated browser sessions, without granting ChatGPT direct workspace access.3111 npmMIT
- AlicenseNot gradedqualityAmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.MIT
- FlicenseNot gradedqualityCmaintenanceConnects Claude Code to Microsoft 365 Graph API, enabling direct use of email, calendar, Teams, SharePoint, and OneDrive.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex and Claude Code to securely read and manage a personal Cronometer account, including food logs, nutrient summaries with missing-data awareness, food search, biometrics, and export analysis.MIT
TDQS
Scored across 24 tools
Several tools have near-identical purposes, especially the OpenClaw-compatible aliases: search_transcripts/get_transcripts, get_transcript/get_meeting_transcript_by_id, list_meetings/get_meetings, create_task/create_user_owned_task, and add_meeting_prep_note/insert_prep_notes_for_meeting. An agent can easily misselect between these pairs despite slightly different descriptions.
Tool names consistently use lowercase snake_case verb_noun, but verbs are not semantically consistent: list vs search for similar retrieval, create vs add vs insert for creation, and get_meetings vs list_meetings for the same operation. The style is predictable, but the duplicate action names break the pattern.
24 tools is at the high end of the range and feels bloated because six or more are redundant OpenClaw-compatible variants of existing tools. A leaner set of unique capabilities would be around 16-18 tools.
Core resources (meetings, transcripts, tasks, contacts, prep notes, morning briefs) have reasonable read/create/update coverage, but there are notable gaps: no delete for tasks or contacts, no update/delete for contacts, and no delete for individual prep notes. Agents would hit dead ends when users ask to remove or modify existing data.