jikan
Related Servers
Alternatives to jikan
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceMCP server that tracks what you are working on. Logs are stored locally as one markdown file per day on your Desktop.5-
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server for managing habits and quit trackers through a jhabit instance. It enables users to list trackers, log entries, and retrieve detailed statistics like streaks and abstinence time.-
- 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.27 npm2MIT
- AlicenseAqualityCmaintenanceAn MCP server for Productive.io that enables users to log time, inspect projects, and manage time entries using natural language commands. It features fuzzy project matching, local caching, and remembers default services per project for streamlined time tracking.14MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that provides tools to control a server-owned Pomodoro timer, allowing focus, pause, resume, skip, reset, and stats operations.1-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: check_session retrieves details for a single session, create_activity creates a private activity, get_stats provides aggregate statistics, list_activities and list_sessions handle listing with different scopes, start_session initiates a session, and stop_session ends one. The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case: check_session, create_activity, get_stats, list_activities, list_sessions, start_session, and stop_session. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 7 tools, the server is well-scoped for its apparent purpose of tracking behavioral sessions and activities. Each tool serves a specific function in the lifecycle (e.g., create, list, start, stop, check), and none feel redundant or missing, fitting within the ideal 3-15 tool range for such a domain.
The tool set provides complete CRUD/lifecycle coverage for session and activity management: create_activity for creation, list_activities and list_sessions for reading, start_session and stop_session for session control, check_session for detailed retrieval, and get_stats for analytics. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.