Coros Workout MCP
UnclaimedMCP server for creating COROS strength workouts via the Training Hub API
Install
claude mcp add coros-workout -- node /path/to/coros-workout-mcp/dist/src/index.jsSet up this server
More in Developer Tools
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
6 of 6 tools
Documented tools (6)
From project documentation. A server handshake does not verify each tool’s description or behavior.
authenticate_coros
Log in with email/password (or auto-login from env vars)
check_coros_auth
Verify current auth status
create_workout
Build and push a strength workout to COROS
list_workouts
List existing workouts
search_exercises
Search ~383 exercises by name, muscle, body part, equipment
update_exercises
Fetch the latest exercise catalog from COROS and rebuild locally
Tool change history
FAQ
Questions about Coros Workout MCP Server
- How do I connect Coros Workout MCP Server to Claude?
- The listing records `claude mcp add coros-workout -- node /path/to/coros-workout-mcp/dist/src/index.js` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code as compatible clients.
- Is Coros Workout MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Coros Workout MCP Server do?
- Coros Workout MCP Server documents 6 tools to the agent, including authenticate_coros, check_coros_auth, create_workout. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.