generate_workout — WorkoutX Exercise API MCP Tool
generate_workout
(generate workout) is one of 20 tools on the
WorkoutX Exercise API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call generate_workout from your client
- Claude Code WorkoutX Exercise API generate_workout run in your project directory
- Claude Desktop WorkoutX Exercise API generate_workout ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WorkoutX Exercise API generate_workout ~/.cursor/mcp.json
- VS Code WorkoutX Exercise API generate_workout .vscode/mcp.json
- Zed WorkoutX Exercise API generate_workout ~/.config/zed/settings.json
- Windsurf WorkoutX Exercise API generate_workout ~/.codeium/windsurf/mcp_config.json
- Cline WorkoutX Exercise API generate_workout ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WorkoutX Exercise API generate_workout ~/.gemini/settings.json
- Grok WorkoutX Exercise API generate_workout .mcp.json (in your project root)
- ChatGPT WorkoutX Exercise API generate_workout Settings → Connectors → Advanced → Developer mode
- Claude.ai WorkoutX Exercise API generate_workout Settings → Connectors → Add custom connector
- LangChain WorkoutX Exercise API generate_workout pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http workoutx https://api.workoutxapp.com/mcp
Other tools on this server
- list_exercise_filters
- search_exercises
- get_exercise
- get_exercise_media
- find_exercise_alternatives
- find_similar_exercises
- estimate_calories
- map_v1_exercise
- generate_program
- search_supplements
- get_supplement_stack
- export_exercise_seed
- get_usage_stats
- get_trending_exercises
- get_endpoint_reference
- generate_types
- get_code_example
- diagnose_request
- check_api_key
This list was read from the server itself, by connecting to it and calling tools/list on 29 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.