griptonite-mcp
Related Servers
Alternatives to griptonite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables reading Fitbod training history, generating workouts via Fitbod's engine, configuring workout programs, and tracking body composition over time.3MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read and analyze your Boardsesh climbing logbook across boards like Kilter, Tension, and MoonBoard, with read-only access and optional credentials for personalized recommendations.12MIT
- AlicenseBqualityBmaintenanceEnables triathlon coaches and athletes to interact with Garmin Connect, including retrieving health/activity data, building and uploading structured workouts (cycling, running, swimming, brick), and accessing coaching analytics like readiness, load, and performance trends.172MIT
- AlicenseNot gradedqualityBmaintenanceEnables conversational logging and retrieval of workouts, sets, weigh-ins, meals, goals, plans, and progress photos through MCP-capable AI clients, with authenticated per-user storage and export/query capabilities.ISC
- AlicenseAqualityDmaintenanceProvides read-only access to Nolio training data including planned workouts, completed sessions, metrics, records, and notes.84MIT
- FlicenseNot gradedqualityBmaintenanceProvides read access to Garmin Connect health and training data (sleep, heart rate, stress, HRV, activities) and supports writes like creating workouts, editing activities, and exporting files.-
TDQS
Scored across 22 tools
Most tools target distinct resources (logs, climbs, rankings, etc.), but there is slight overlap between log_attempt and log_climb since log_climb can also record attempts, causing potential confusion for an agent.
The majority of tools follow a verb_noun pattern (get_*, list_*, log_*), but 'auth_status' lacks a verb and 'raw_request' uses an adjective-noun pattern, deviating from the predominant convention.
22 tools is slightly above the typical sweet spot of 3-15, but it is justified by the breadth of features (auth, routes, logs, rankings, etc.) and includes a raw_request tool for flexibility.
The tool surface covers core workflows like authentication, route browsing, logging climbs, and viewing rankings, with a raw_request tool to handle missing endpoints. Minor gaps exist (e.g., no update/delete for logs), but agents can work around them.