Kenso exposes its tools through standard OAuth plus MCP and OpenAPI, the same interface the ChatGPT and Claude connectors use. If you want to build your own integration, these are the public endpoints.

Where to find it

kensoforge.com/integrations lists the endpoints below along with setup guides for Claude and ChatGPT specifically. In the app, Settings → Connected Apps shows and manages anything you've authorized.

Endpoints

  • MCP endpoint: api.kensoforge.com/mcp
  • OpenAPI schema: /api/v1/integrations/openapi.json
  • OAuth discovery: /.well-known/oauth-authorization-server

Scopes you can grant

An integration only gets access to the scopes you approve at connection time:

  • Workout history and exercises: sessions, sets, reps, weights, RPE, durations
  • Active and saved programs
  • Profile and preferences: goal, experience level, training notes
  • Recovery, signals, and biometrics
  • Strength score and personalized signal insights
  • Creating new programs (these land as drafts you activate yourself)
  • Logging freestyle workouts and staging imports for your review

Authentication

Connections use OAuth with PKCE, so there's no shared client secret. Kenso's own connectors use fixed client IDs (claude-connector, chatgpt-connector). The OAuth discovery endpoint above publishes everything a standard OAuth client needs to find the authorization, token, and registration endpoints automatically.

Registering your own OAuth client

Kenso supports dynamic client registration (RFC 7591), which is what MCP clients use to set themselves up before the first sign-in. POST a JSON body with client_name and redirect_uris to api.kensoforge.com/oauth/register and you get a client_id back. Only public clients are issued: PKCE is required and there is no client secret. Redirect URIs must be https, except loopback addresses such as http://127.0.0.1/callback, which match on any port so native clients can bind an ephemeral one.

API keys

Some assistants ask you to paste a key instead of signing in. Meta Muse's connector store works this way. Create a key in Settings → Connected Apps → API keys: give it a label, pick the scopes it can use, and copy it when it's shown. Kenso shows a key once and never again. Send it as a bearer token, Authorization: Bearer ke_pk_..., to the MCP endpoint or the REST API. A key has the same per-scope access as an OAuth connection, respects the same Pro checks per tool, and can be revoked at any time from the same screen. You can hold up to five active keys.

Who this is for

Most people connecting Kenso to an AI assistant only need the setup guides for Claude or ChatGPT: see Connect Kenso to Claude and Connect Kenso to ChatGPT. This page is for anyone building their own tool or integration against Kenso's API directly.

Good to know

  • Connecting an AI assistant is free. A few analytics tools (strength score charts, the coaching report, signal insights) require Kenso Pro and say so when called.
  • An integration only reads your data when a request explicitly calls a Kenso tool: there's no background polling.
  • You can revoke any connection immediately from Settings → Connected Apps: see Connected Apps and what they can access.