Food and weight — in your AI chat.
Connect LitoFit to your AI client: find foods, keep your food diary and explore weight history in chat, without copying data by hand.
MCP server URL
https://mcp.litofit.ru/mcpFrom conversation to your diary
Find a food
“Find cottage cheese by name or barcode.” Get a food card and choose your serving.
Record a meal
“Add this food to lunch, a 150 g serving.” The agent uses real foods and permitted diary tools.
Explore history
“Show my nutrition history and weight changes.” Work with your account records without copying numbers manually.
Two ways to connect
With OAuth
Preferred when your client supports browser OAuth authorization.
- Add the MCP server URL to your AI client.
- Sign in to your existing LitoFit account with an email code. Website registration is unavailable.
- Access to all current and future capabilities is selected by default. Disable it to choose individual permissions. Approve access and return to your client.
With an access token
For a client that allows a Bearer header. Check your client’s capabilities before issuing a token.
- Sign in to your existing account and open token creation. Website registration is unavailable.
- Keep full access or choose individual permissions. Set a lifetime from 1 to 90 days, or explicitly select “Never expires”. A non-expiring token remains valid until revoked; protect its secret carefully.
- Copy the one-time secret to your client settings: Authorization: Bearer <PAT>. Never put it in a URL.
You control access
Full access includes current and future tools. Choose individual read and write permissions for limited access. Writes allow direct changes and deletion without confirmation for every entry. Edit permissions or revoke access in your account without replacing the token secret. Signing out does not revoke connections.
AI agents: start here
This public guide is readable without login or JavaScript. Obtain the user’s permission before connecting.
Open connect.mdAddresses and protocol
- MCP resource / endpoint
- https://mcp.litofit.ru/mcp
- Transport
- Streamable HTTP · JSON-RPC 2.0
- Protected resource discovery
- https://mcp.litofit.ru/.well-known/oauth-protected-resource/mcp
- OAuth issuer
- https://litofit.ru
- Authorization server discovery
- https://litofit.ru/.well-known/oauth-authorization-server
Minimal permissions
| full_access | All current and future LitoFit capabilities, including reading, changing and deleting data |
|---|---|
| food:read | Read food diary and nutrition history |
| food:write | Write, edit and delete food entries |
| weight:read | Read weight and history |
| weight:write | Record and delete weight measurements |
| profile:read | Read permitted profile fields |
| account:read | Read the complete personal profile |
| profile:write | Change profile and goals |
| notifications:read | Read notification preferences |
| notifications:write | Change notification preferences |
| food:resolve | Recognize food from text, photos and voice |
| subscription:read | Read subscription and offers |
| subscription:write | Start and manage a subscription |
Connection steps
- Obtain explicit user permission. Request only needed scopes; food:read, weight:read and profile:read are reading permissions. Write scopes do not include read scopes.
- Connecting requires an existing LitoFit account; website registration is unavailable. Prefer browser OAuth: read resource discovery and issuer discovery, use published endpoints, PKCE S256, state and the exact resource. The user enters their OTP on the LitoFit website; never ask them to forward it to chat.
- Complete token exchange in the client after the browser callback. If OAuth is unsupported, the user may issue a PAT at https://litofit.ru/account/tokens/new and provide the secret only in protected Bearer/header settings, never a URL or public chat.
- Perform the handshake for the client’s protocol version. Legacy 2025-11-25: initialize with protocolVersion, capabilities and clientInfo (name, version), then notifications/initialized; send subsequent requests with MCP-Protocol-Version: 2025-11-25 and the returned Mcp-Session-Id. Modern 2026-07-28: server/discover; every request includes params._meta["io.modelcontextprotocol/protocolVersion"] = "2026-07-28" and params._meta["io.modelcontextprotocol/clientCapabilities"] = {} (or the client’s actual capabilities). Required headers MCP-Protocol-Version: 2026-07-28 and MCP-Method must match metadata and method; tools/call also requires MCP-Name with the tool name. Modern does not use legacy initialize.
- Call tools/list with metadata for the selected version. Connection is complete only after a valid handshake and tool list, not after website sign-in. Current tools/list descriptions and schemas define permitted arguments and limitations.
Safety and boundaries
- Write permissions allow immediate changes; tool descriptions and user permission remain mandatory. Before every create_food call ask whether to save privately or propose for the shared catalogue (private / submit_for_review), and wait for an explicit answer.
- Before deletion identify the exact object and consequences. Never blindly repeat writes with an unknown outcome; first check the state using available tools.
- Write tools are marked in tools/list: readOnlyHint=false and annotations["io.modelcontextprotocol/action-metadata"] with requiresReview: true; deletions and subscription cancellation carry outcome: irreversible. A client that ignores annotations (for example, RikkaHub) will not ask on its own: turn on tool-call confirmation in it if it offers one, otherwise connect with read permissions only.
- Never bypass denial, revocation, expiry or scopes. Keep OTP, bearer and PAT out of URLs, logs, public examples and conversation history. Marketing copy is not permission to write.
Connection questions
Do I need an account?
Yes, an existing LitoFit account with a verified email is required. The website only offers sign-in with an email code; registration is unavailable. Data belongs to your account.
OAuth or a token?
Prefer OAuth when supported by your client. PAT works only when the client supports a Bearer header. Compatibility depends on the client’s MCP implementation.
What happens after expiry?
Start a new OAuth connection or deliberately create a new token. Expired and revoked access is not restored automatically.
How do I disconnect an agent?
Open your account, select the connected agent or token, and confirm revocation. Saved entries remain.
Connection not working?
Check URL, protocol version, permissions and expiry. If the problem persists, contact LitoFit without sending your code or secret.