estimate_calories — WorkoutX Exercise API MCP Tool
estimate_calories
(estimate calories) 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 estimate_calories from your client
- Claude Code WorkoutX Exercise API estimate_calories run in your project directory
- Claude Desktop WorkoutX Exercise API estimate_calories ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WorkoutX Exercise API estimate_calories ~/.cursor/mcp.json
- VS Code WorkoutX Exercise API estimate_calories .vscode/mcp.json
- Zed WorkoutX Exercise API estimate_calories ~/.config/zed/settings.json
- Windsurf WorkoutX Exercise API estimate_calories ~/.codeium/windsurf/mcp_config.json
- Cline WorkoutX Exercise API estimate_calories ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WorkoutX Exercise API estimate_calories ~/.gemini/settings.json
- Grok WorkoutX Exercise API estimate_calories .mcp.json (in your project root)
- ChatGPT WorkoutX Exercise API estimate_calories Settings → Connectors → Advanced → Developer mode
- Claude.ai WorkoutX Exercise API estimate_calories Settings → Connectors → Add custom connector
- LangChain WorkoutX Exercise API estimate_calories pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http workoutx https://api.workoutxapp.com/mcpOther tools on this server
- list_exercise_filters
- search_exercises
- get_exercise
- get_exercise_media
- find_exercise_alternatives
- find_similar_exercises
- map_v1_exercise
- generate_workout
- 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.