Developer resources

RUBICON.fitness MCP and API

Connect Grok, Claude, Cursor, or a trusted coding agent to RUBICON.fitness, then inspect the public HTTP API contract when you need it.

No terminal required

Connect your training assistant

Every assistant uses the same public Rubicon address. You sign in on Rubicon and approve the access. Never paste a token into a connector.

Grok

  1. Choose New Connector, then Custom.
  2. Paste https://rubicon.fitness/api/mcp
  3. Complete the Rubicon sign-in.
Open Grok connectors

Claude

  1. Choose +, then Add custom connector.
  2. Paste https://rubicon.fitness/api/mcp
  3. Add it, click Connect, and sign in to Rubicon.
Open Claude connectors

Cursor

  1. Open the one-click install link.
  2. Approve the Rubicon server.
  3. Sign in when Cursor asks for access.
Add to Cursor

A Grok Business or Enterprise team admin first adds Other. A Claude Team or Enterprise Owner first adds the custom connector. Each athlete still connects their own Rubicon account.

Command-line setup

Rubicon MCP is a remote Streamable HTTP server. Protected tools use OAuth. Add the endpoint to your coding agent, then sign in as the athlete or coach whose data the agent may use.

Codex

codex mcp add rubicon --url https://rubicon.fitness/api/mcp
codex mcp login rubicon --scopes training:read,training:write,feedback:read,feedback:write,programming:write,offline_access

Claude Code

claude mcp add --transport http rubicon https://rubicon.fitness/api/mcp

The listed Codex scopes cover training reads, athlete-owned log edits, feedback reads, and programming changes. They exclude the operator-only programming:admin scope.

Connection facts

Transport
Streamable HTTP
Authentication
OAuth with PKCE
MCP endpoint
https://rubicon.fitness/api/mcp
Protected resource metadata
https://rubicon.fitness/.well-known/oauth-protected-resource/api/mcp

A plain browser GET returns 405 by design. Configure the URL as an HTTP MCP server. The client initializes the protocol over POST and follows the OAuth metadata when a protected tool needs access.

HTTP API

Each MCP tool is also a POST route under /api/rest, generated from the same capability contract. The OpenAPI document describes those routes, not the MCP protocol.