inbody-api-mcp
Enables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.
README
inbody-api-mcp
<!-- mcp-name: io.github.rwestergren/inbody-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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.