- MCP server URL
-
https://verxion.ai/mcp - Sign-in
- OAuth 2.1 · Apple / Google
- Permissions
- Scoped tokens · revocable from Connected Apps
[ MCP SETUP ]
Connect Verxion to your AI.
OAuth-secured. Revocable per scope. No app to install — your AI talks directly to your logbook.
ChatGPT
Custom ConnectorAdd Verxion as a custom MCP connector from ChatGPT settings. Requires ChatGPT Plus, Business, or Enterprise.
- 1
Open ChatGPT → Settings → Connectors.
- 2
Toggle Advanced → Developer mode on (lets you add custom connectors).
- 3
Click Create (or Add custom connector) and paste the Verxion MCP URL below.
URL
https://verxion.ai/mcp
- 4
Authorize with Apple or Google in the window that opens.
Verxion is not yet listed in the public ChatGPT Apps directory (verification pending). Once verified, you'll be able to add it without Developer mode. Voice mode and rich widgets work the moment the connector is authorized.
Claude (Desktop & Web)
RecommendedAnthropic's chat app. Connect via Custom Connectors — OAuth in your browser, no API key needed.
- 1
Open Claude Desktop or claude.ai. Requires a Claude Pro, Max, Team, or Enterprise plan.
- 2
Go to Customize → Connectors → + → Add custom connector.
- 3
Paste the Verxion MCP URL:
URL
https://verxion.ai/mcp
- 4
Click Add, then sign in with Apple or Google in the window that opens.
After consent the connector is ready. Toggle it on per-conversation from the + menu.
Legacy stdio config (older Claude Desktop)
Only needed if your Claude Desktop is too old to show Custom Connectors, or for headless setups with an embedded API key. Generate the key from Settings → API Keys in the web app.
File
~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%\Claude\claude_desktop_config.json. Restart Claude Desktop after editing.
Configuration
{
"mcpServers": {
"verxion": {
"url": "https://verxion.ai/mcp",
"headers": {
"Authorization": "Bearer <your-vxk-key>"
}
}
}
} Claude Code
CLIAnthropic's terminal coding agent. Add Verxion as an MCP server with a single command — OAuth runs in your browser.
- 1
Run this command in your terminal:
Command
claude mcp add verxion --transport http https://verxion.ai/mcp
- 2
Inside Claude Code, type /mcp and select Authenticate next to Verxion.
- 3
A browser window opens — sign in with Apple or Google. After consent, the window closes and tool calls work immediately.
Headless / CI (with API key)
Use this when browser-based sign-in is not available (CI runners, dotfiles, restricted environments). Generate the key from Settings → API Keys in the web app, then run:
Command
claude mcp add verxion --transport http https://verxion.ai/mcp \ --header "Authorization: Bearer <your-vxk-key>"
Cursor
AI editorAI-first code editor. Add Verxion via Cursor's MCP config file — OAuth runs in your browser on first tool call.
- 1
Open ~/.cursor/mcp.json (create it if it does not exist). Use .cursor/mcp.json inside a project folder for project-scoped access.
- 2
Paste the configuration below and save:
Configuration
{ "mcpServers": { "verxion": { "url": "https://verxion.ai/mcp" } } } - 3
Cursor opens your browser on first Verxion tool call — sign in with Apple or Google.
Headless / no-browser (with API key)
Use the configuration below if browser-based sign-in is not available. Generate the key from Settings → API Keys in the web app.
Configuration
{
"mcpServers": {
"verxion": {
"url": "https://verxion.ai/mcp",
"headers": {
"Authorization": "Bearer <your-vxk-key>"
}
}
}
} Other MCP clients
GenericWindsurf, Continue, Cline, Zed, and any client that speaks MCP over HTTP. The same URL works everywhere.
- 1
Copy the MCP server URL below into your client's MCP configuration.
URL
https://verxion.ai/mcp
- 2
On first tool call the client opens your browser for OAuth sign-in (Apple / Google).
- 3
If your client doesn't implement OAuth 2.1, authenticate with an API key as Authorization: Bearer <key>.
Verxion follows the public MCP spec (Streamable HTTP transport). Discovery: /.well-known/oauth-protected-resource on the MCP host. Any spec-compliant client will work out of the box.
Scopes & revocation
Every connection gets its own OAuth token, scoped to the data it needs (training, nutrition, body, social). You can review and revoke any connected client at any time from Settings → Connected Apps in the web app.
Prefer the browser?
No MCP client needed. Sign in directly to the verxion web app and use it like any web product. Your logbook stays the same — every MCP client you connect later reads from it.
First time here?
Pick a client above, follow the steps — your AI handles the OAuth flow. We'll create your account on first sign-in.
Already have an account?
Sign in to manage your account, scopes, and connected clients.
Sign in