RS Life exposes an authenticated Model Context Protocol server at
https://api.rs.life/functions/v1/mcp. It connects an existing
RS Life account to compatible AI assistants through OAuth 2.1 with PKCE.
Every personal-data category starts disabled. The user can grant separate read and create permissions during connection, change them later in RS Life, or revoke the connection. Permission changes apply to live requests.
Read tools cover profile, nutrition, the global food catalog, kitchen, body measurements, supplements, workouts, recipes, dishes, exercises, and training programs. Create tools can add nutrition-log entries, recipes, dishes, private exercises, and training programs when the matching permission is enabled.
Content creation uses a prepare, explicit confirmation, commit, and status flow. Tool inputs are validated server-side, and retries use stable request identifiers to avoid duplicate records.
Tool responses contain only the requested category. Operational logs keep correlation and request identifiers but not access tokens, authorization codes, passwords, raw prompts, or health payloads.