Inbody Api Mcp

io.github.rwestergrenPublished by GitHub account rwestergrenv0.1.0Updated Oct 24, 2026

MCP server for InBody body-composition data — scans, body fat, muscle mass, body water

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Read-only MCP server that lets an assistant pull your InBody body-composition history — profile, scan list and full scan metrics — from the InBody mobile API.

What you can do
  • Read profile identity and baseline metrics such as height, weight, age and gender
  • Count total scans and list chronological scan summaries with weight, BMI, body fat percentage and muscle mass
  • Fetch the full metric set for a single scan, including body composition, BMI/fat/muscle with normal ranges, and segmental impedance
  • Route requests to the correct regional API host from a country code and re-authenticate automatically when the token expires
When to use it
Useful when you want an assistant to review or discuss your own InBody scans — tracking weight, body fat, muscle mass or segmental impedance over time — without exporting data by hand.
Requirements
Runs locally over stdio, typically launched with uvx from the PyPI package, so Python tooling (uv) is needed. Requires an InBody account: INBODY_LOGIN_ID (registration phone number, digits only) and INBODY_LOGIN_PW. Optional INBODY_COUNTRY_CODE selects the regional API host (default US). Network access to the InBody regional API is required.
Before you install
Requires your InBody account password in INBODY_LOGIN_PW and your registration phone number in INBODY_LOGIN_ID; store them in the client's environment config rather than in shared files. It relies on a reverse-engineered, undocumented mobile API, so it may break without notice. It is read-only, but your body-composition data is sent to and from InBody's servers.

Installation

In SourceWeft

  1. Open Inbody Api Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

inbody-api-mcp

[License: MIT] [CI] [Build Docker image] [PyPI]

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

bash
curl -LsSf https://astral.sh/uv/install.sh | sh

2. Set credentials

bash
export INBODY_LOGIN_ID="3026323617"   # registration phone number, digits onlyexport INBODY_LOGIN_PW="your-password"export INBODY_COUNTRY_CODE="US"       # ISO country code (default US)

INBODY_LOGIN_ID is 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 with EmptyData.

3. Configure your MCP client

uvx downloads and runs the server on demand -- no separate install step.

OpenCode (opencode.json)
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)
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

ToolDescription
get_profileUser identity and baseline metrics (height, weight, age, gender)
get_scan_countTotal number of scans on the account
list_scansChronological scan summaries (weight, BMI, % body fat, muscle mass)
get_scanFull 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:

  1. POST /CommonAPI/GetCountryInfoV2 (on appapicommon.lookinbody.com) returns a per-country host table. The Type == "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.
  2. POST /V2/Main/GetLoginWithSyncDataPartV2 exchanges the login ID + password for a 24-hour JWT, a refresh token, and the account UID.
  3. 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:

python
from inbody_api_mcp.client import InBodyClient
client = InBodyClient()
# Total number of scanscount = client.get_scan_count()
# Recent scans (newest first), paginatedscans = client.get_scans(number=20, index=0)
# User profileprofile = client.get_user_info()

Transport

stdio only. MCP clients (OpenCode, Claude Desktop) spawn the stdio process directly via uvx/uv.

License

MIT

Source: README.md at commit f87f2b3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts