freee-mcp
Related Servers
Alternatives to freee-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceattendance-engine-mcp is a Model Context Protocol server that gives AI agents deterministic, fixture-backed tools for workforce attendance and wage-and-hour compliance. Built on @attendance-engine/core — a pure-function, zero-deps, 100%-covered TypeScript engine — it lets Claude, Cursor, Windsurf, or any MCP host correctly answer the questions HR/payroll teams actually ask: did this person clock i811 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing freee HR operations like employee data, attendance, leave, and approvals through natural language in MCP-compatible clients such as Claude Desktop.1-
- AlicenseAqualityDmaintenanceAn MCP server that automates TimeCard timesheet management using Playwright browser automation. It enables users to manage projects, activities, and daily hours entries through natural language interactions.63MIT
- FlicenseNot gradedqualityBmaintenanceA modular MCP server integrating Clockify, WakaTime, and Azure DevOps for time tracking, work item management, and time logging via a unified API.2-
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.18 npm2MIT
- AlicenseBqualityDmaintenanceMCP server for Clockify time tracking, enabling CRUD operations on workspaces, projects, tasks, clients, tags, users, and time entries.36MIT
TDQS
Scored across 28 tools
Many prepare/commit pairs and multiple approval layers (generic approvals, monthly approvals, personal applications) overlap, so an agent must parse long descriptions to know which tool applies. Individual pairs are distinct, but generic vs monthly approval tools and several list/detail tools can be confused.
All tools use the freee_ prefix and snake_case with domain/action segments, making the set mostly predictable. Minor deviations exist in pluralization and action labels, such as personal_application_detail vs personal_applications_list and prepare_create vs prepare_action.
At 28 tools, the server exceeds the typical well-scoped range and includes many paired prepare/commit variants for similar operations. The domain is complex, but the count is still heavy and increases selection burden.
The set covers auth/status, clock punches, leave balances, personal application list/detail/options and create/cancel/withdraw prepare/commit, approvals, and monthly approval workflows, giving broad lifecycle coverage. Only minor gaps like comment/route management or direct update of an existing application are apparent.