Claude Code
Use verxion inside Claude Code — log workouts from the same terminal where you ship features.
Claude Code is Anthropic’s terminal-native agent. With verxion configured, you can log sets between commits without switching apps.
Setup
- Open the MCP Setup page and sign in
- Copy the Claude Code configuration snippet
- Add it to your
.claude/settings.json— either at the user level (~/.claude/settings.json) for every project or at the project level (<repo>/.claude/settings.json) when you only want it active in one repo - The tools become available in your next Claude Code session — no restart of the CLI needed for new sessions
Verify
> Am I connected to verxion?
Claude Code lists the tool set it sees. As with Claude Desktop, the default is the single execute_code tool (Code Mode).
Use it during work
Some real patterns:
> Log a quick session: warmup 5x5 squat 60kg, then 4x5 100kg RPE 8
> Show me my last bench session
> How's my training this week — am I behind?
Because Claude Code already has shell access, you can also chain it with local actions:
> Log my workout and then run pnpm test
Scopes and permissions
verxion uses OAuth scopes to gate writes vs reads. The default config grants the standard set. If you want a read-only session (e.g., to inspect data without risking accidental writes), the setup page has a read-only token option — paste that snippet instead.
Troubleshooting
Tools show up but every call returns 401
- Token expired. Regenerate from the setup page and replace the snippet.
Tools missing from claude --list-tools
- Confirm
settings.jsonJSON is valid and themcpServerskey sits at the right level - Run
claudein verbose mode to see MCP connection errors
Tips
- Claude Code is great for batch operations: “import this routine and create a session for today” is a single prompt
- The same
.claude/settings.jsonworks across all your repos when placed in~/.claude/ - Pair with Routines & Programs — Claude Code shines for the “set up my training block” moments