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); a custom integration registers its own. The OAuth discovery endpoint above publishes everything a standard OAuth client needs to find the authorization and token endpoints automatically.
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 a third-party AI assistant requires Kenso Pro.
- 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.