Skip to main content
OneRep speaks the Model Context Protocol, which lets an AI assistant read your training and nutrition log and, if you allow it, add to it. You use the same API keys, the same scopes, and the same rate limits as the REST API, so there is nothing new to provision. The endpoint is a single POST URL that your assistant calls to discover tools and invoke them.

​
Endpoint and protocol

Your MCP endpoint is:
Find your exact URL under Settings → API & MCP in the app. Copy it from there. Do not assemble it by hand.

​
Authentication

Pass your API key as a bearer token in every request:
You create and manage keys under Settings → API & MCP. A key is Read only (read), Read & write (read and write), or Full access (read, write, and delete). Scopes, rate limits, and key management work the same way here as they do for the REST API.
A token is only shown the tools its scopes cover. A read-only token lists 10 tools; read & write lists 21; full access lists all 29. Tools outside your scopes are hidden entirely, and calling one directly is refused. Count the entries in tools/list if you are unsure which kind of key you are holding.

​
Connecting an AI assistant

Run this command once to register OneRep as an MCP server. Replace the URL with your deployment URL and the key with your API key.

​
Quick connection test

To confirm the endpoint is reachable and your token is valid, call tools/list directly:
A working response lists the tools available to your token. A missing or revoked token returns a 401 with a WWW-Authenticate header rather than an empty list, so a misconfigured client will tell you immediately rather than silently appearing to be an empty account.