F
licenseNot graded
qualityB
maintenanceA read-only MCP server that lets team members access Simplified HR Work Journal entries and team reports through Claude, with permissions enforced by the existing Work Journal API.
-
Eodly MCP server
by layergen
Related Servers
Alternatives to Eodly MCP server
Related Servers
- AlicenseAqualityDmaintenanceA read-only MCP server for Linear that enables listing teams, cycles, and issues, and searching issues via the Linear API.5113 npmMIT
- AlicenseAqualityBmaintenanceA read-only MCP server for querying Timely time tracking data, providing tools for project overviews, time spent summaries, and work log entries.3MIT
- AlicenseBqualityDmaintenanceRead-only MCP server for the Humaans HRIS API, providing tools to query people, reporting chains, compensation, time away, and more.33MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server exposing client dashboard data (client series and reports) from Supabase, allowing live natural language queries about any client.-
teamhood-mcpofficial
FlicenseAqualityDmaintenanceA read-only MCP server that enables querying Teamhood workspaces, users, boards, items, and time logs through the Teamhood Open API, running locally via stdio so your API key stays on your machine.10-- AlicenseNot gradedqualityFmaintenanceRead-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.MIT
TDQS
A3.8/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: whoami identifies the API key, list_reports and get_report separate listing from retrieval, and list_team targets the team roster. There is no meaningful overlap that would cause misselection.
Naming Consistency4/5
list_reports, get_report, and list_team follow a consistent verb_noun pattern. whoami is a common identity command but breaks the pattern, making it a minor deviation rather than a major inconsistency.
Tool Count4/5
Four tools is a reasonable, well-scoped set for a read-only reporting and team-access server. It is slightly lean, but each tool earns its place and there are no redundant entries.
Completeness4/5
The surface covers identity, report listing and retrieval, and team roster access, which is coherent for a read-only integration. Minor gaps exist, such as no team member detail lookup or report filtering, but core read workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues