About inbody-api-mcp
inbody-api-mcp is a read-only MCP server for people who want to access their InBody body-composition history through MCP clients. It retrieves profile, scan summaries, and detailed composition and impedance metrics from the regional API used by the Android app.
Key features
- 01Retrieve profile and baseline metrics
- 02List scan history and scan counts
- 03Read detailed composition and impedance data
- 04Route requests by country and refresh authentication
Use cases
- 01Review body-composition trends across scans
- 02Retrieve detailed metrics for a particular scan
MCP support
The server exposes four read-only tools for profile, scan count, scan listing, and full scan details. It uses stdio transport for MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx inbody-api-mcpINBODY_LOGIN_IDThe phone number used to register your InBody account (digits only, no country code).INBODY_LOGIN_PWSecretYour InBody account passwordINBODY_COUNTRY_CODEISO country code selecting the regional API host (defaults to US).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEinbody-api-mcp
Hosted version for Claude.ai, ChatGPT, and Grok coming soon. Join the waitlist →
An MCP (Model Context Protocol) server for InBody body-composition data, built on the reverse-engineered mobile REST API used by the InBody Android app.
InBody has no public API and no web UI for personal scan data. This server talks to the same JSON REST endpoints the mobile app uses, exposing your body composition history (body fat, muscle mass, body water, segmental impedance) to any MCP client.
Features
- Profile -- identity and baseline metrics (height, weight, age, gender)
- Scan history -- chronological summaries (weight, BMI, % body fat, muscle mass)
- Full scan metrics -- complete body composition (BCA), BMI/%fat/muscle with normal ranges (MFA), and segmental/multi-frequency impedance (IMP)
- Automatic region routing -- resolves the correct regional API host from your country code
- Automatic re-authentication -- caches the 24h JWT and re-logs in on expiry
Quick Start
1. Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
2. Set credentials
export INBODY_LOGIN_ID="3026323617" # registration phone number, digits only
export INBODY_LOGIN_PW="your-password"
export INBODY_COUNTRY_CODE="US" # ISO country code (default US)
INBODY_LOGIN_IDis the phone number used at registration, not your email -- digits only, no country code or+(e.g.3026323617). InBody keys login on the phone number; the email is only returned as profile data. An email value will fail login withEmptyData.
3. Configure your MCP client
uvx downloads and runs the server on demand -- no separate install step.
OpenCode (opencode.json)
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"inbody": {
"type": "local",
"command": ["uvx", "inbody-api-mcp"],
"environment": {
"INBODY_LOGIN_ID": "{env:INBODY_LOGIN_ID}",
"INBODY_LOGIN_PW": "{env:INBODY_LOGIN_PW}",
"INBODY_COUNTRY_CODE": "US"
},
"enabled": true
}
}
}
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"inbody": {
"command": "uvx",
"args": ["inbody-api-mcp"],
"env": {
"INBODY_LOGIN_ID": "3026323617",
"INBODY_LOGIN_PW": "your-password",
"INBODY_COUNTRY_CODE": "US"
}
}
}
}
Available Tools
| Tool | Description |
|---|---|
get_profile | User identity and baseline metrics (height, weight, age, gender) |
get_scan_count | Total number of scans on the account |
list_scans | Chronological scan summaries (weight, BMI, % body fat, muscle mass) |
get_scan | Full metric set for one scan (BCA / MFA / IMP blocks) |
This server is read-only: no write or delete endpoints are exposed.
How It Works
This server communicates with the regional *.lookinbody.com REST API -- the
same backend used by the InBody Android app (v2.8.31). The API was
reverse-engineered by capturing app traffic with mitmproxy and confirming
payload shapes against the live API.
The auth flow:
POST /CommonAPI/GetCountryInfoV2(onappapicommon.lookinbody.com) returns a per-country host table. TheType == "API"row for your ISO country code gives the regional API base (US ->appapiusav2.lookinbody.com) and the numeric phone code used in request bodies.POST /V2/Main/GetLoginWithSyncDataPartV2exchanges the login ID + password for a 24-hour JWT, a refresh token, and the account UID.- Subsequent calls send
Authorization: Bearer <JWT>. The client re-authenticates automatically when the token expires.
Each scan record nests three blocks: BCA (body composition analysis -- body water, protein, mineral, fat, segmental water), MFA (BMI, % body fat, skeletal muscle mass, WHR with normal ranges), and IMP (raw impedance per frequency and body segment).
Python API
You can use the client directly:
from inbody_api_mcp.client import InBodyClient
client = InBodyClient()
# Total number of scans
count = client.get_scan_count()
# Recent scans (newest first), paginated
scans = client.get_scans(number=20, index=0)
# User profile
profile = client.get_user_info()
Transport
stdio only. MCP clients (OpenCode, Claude Desktop) spawn the stdio process
directly via uvx/uv.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.