Claude Desktop

Set up and use verxion with Claude Desktop on macOS, Windows, and Linux.

Claude Desktop is the simplest non-browser way to use verxion. Configure it once and your fitness data is available in every conversation.

Setup

Go to the MCP Setup page and sign in with Apple or Google
Copy the Claude Desktop configuration snippet
Open your claude_desktop_config.json:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- Linux: ~/.config/Claude/claude_desktop_config.json
Paste the snippet inside the mcpServers object (or create the object if it doesn’t exist)
Restart Claude Desktop — config is only re-read on launch

Once Claude restarts, verxion tools appear in the tool picker. Ask anything — Claude routes the right calls automatically.

In a fresh conversation, ask:

"Am I connected to verxion?"

Claude will list the tools it sees. If you only see the execute_code tool, you’re in Code Mode — that’s the default and what you want.

Claude doesn’t see verxion after restart

Check the JSON syntax is valid (trailing commas are a common culprit)
Confirm the config file path matches your OS (macOS path is not under ~/.config)
Look at Claude Desktop’s developer logs: View → Toggle Developer Tools → Console

OAuth login loop

Sign out from the setup page, close the browser tab, and re-copy a fresh snippet. Tokens are bound to your session.

Tools work in one conversation but not another

Each conversation inherits the tool config at start; new tools added mid-conversation aren’t picked up. Start a fresh chat.

Claude Desktop renders markdown tables, code blocks, and lists natively — ask for “a table of my last 8 bench sessions” and you get a clean comparison
For visual widgets (charts, contribution grids), use ChatGPT — those are ChatGPT-specific
Be specific in prompts: “Log bench 100kg x 8 RPE 8” beats “I did some bench today”