Zenith MCP Server
Related Servers
Alternatives to Zenith MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA personal health and fitness MCP server that provides tools for managing profile data, goals, body measurements, nutrition, workouts, sleep, check-ins, life events, analytics, and coach memories via Supabase Postgres.1-
- AlicenseNot gradedqualityBmaintenanceSelf-hosted fitness tracking MCP server that gives AI assistants access to your nutrition, training, weight, sleep, and accomplishment data via 77 tools and 5 resources. Enables natural-language logging and querying of personal health metrics through Claude or ChatGPT.1BSD 2-Clause "Simplified"
- AlicenseNot gradedqualityAmaintenanceAn MCP server that securely syncs and queries your health data from Apple Health, storing it in your own Supabase Postgres database and exposing tools for AI assistants to retrieve weight, calories, macros, and more.7 npmMIT
- FlicenseNot gradedqualityBmaintenancePersonal Notion MCP server with tools for task management, wrapping the Notion REST API to create, query, and update tasks in a kanban board.-
- FlicenseBqualityDmaintenanceA personal fitness tracking server that enables logging and querying workouts, nutrition, and body metrics through a local SQLite database. Integrates with OpenNutrition MCP for food logging and supports exercise history tracking for workout progression.17-
- FlicenseAqualityBmaintenancePersonal workout coach MCP server that logs exercises in natural language, tracks progress with SQLite, and provides coaching signals like estimated 1RM and volume trends.6-
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: logging a completion, viewing today's dashboard, checking a specific habit's streak, and viewing overall mission progress. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: log_habit, get_today_status, get_streak, get_mission_overview. The verbs are consistent ('log' and 'get'), and the nouns clearly describe the target.
With 4 tools, the set is concise and well-scoped for a habit-tracking mission server. Each tool covers a necessary interaction (log and three read views), and the count is within the ideal range.
The server covers core logging and status views, but lacks a way to list available habits or manage them (create/update/delete). An agent cannot discover valid habit names, which could cause failures when calling log_habit or get_streak.