my_training_context — anatome MCP Tool
my_training_context
(my training context) is one of 36 tools on the
anatome
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call my_training_context from your client
- Claude Code anatome my_training_context run in your project directory
- Claude Desktop anatome my_training_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor anatome my_training_context ~/.cursor/mcp.json
- VS Code anatome my_training_context .vscode/mcp.json
- Zed anatome my_training_context ~/.config/zed/settings.json
- Windsurf anatome my_training_context ~/.codeium/windsurf/mcp_config.json
- Cline anatome my_training_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI anatome my_training_context ~/.gemini/settings.json
- Grok anatome my_training_context .mcp.json (in your project root)
- ChatGPT anatome my_training_context Settings → Connectors → Advanced → Developer mode
- Claude.ai anatome my_training_context Settings → Connectors → Add custom connector
- LangChain anatome my_training_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http anatome https://anatome.dev/mcp
Other tools on this server
- search_exercises
- get_exercise
- resolve_exercise
- list_muscles
- generate_muscle_image
- list_routines
- get_routine
- instantiate_routine
- search_foods
- lookup_barcode
- log_workout
- get_workouts
- log_meal
- get_meals
- log_water
- log_body_metric
- get_body_metrics
- upsert_profile
- get_profile
- log_cardio
- get_cardio_activities
- ai_parse_meal
- ai_photo_macros
- ai_meal_plan
- ai_workout_plan
- get_muscle_recovery
- get_nutrition_daily
- get_water
- update_meal
- delete_meal
- update_sets
- delete_workout
- export_data
- get_events
- get_progress
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.