Skip to main content

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

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_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)

{
  "$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:

  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:

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

Metadata

Release files for inbody-api-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for inbody-api-mcp 0.1.0
File Size Uploaded Provenance Actions
inbody_api_mcp-0.1.0.tar.gz 37.5 kB With provenance Details for inbody_api_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for inbody-api-mcp 0.1.0
File Interpreter ABI Platform Actions
inbody_api_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for inbody_api_mcp-0.1.0-py3-none-any.whl

Total release size: 48.7 kB

Release files / inbody_api_mcp-0.1.0.tar.gz

Download URL inbody_api_mcp-0.1.0.tar.gz
Size 37.5 kB
Tags Source
SHA-256 checksum
How to use checksums
7c2bbe1c481e4a57718031a7a7a887add04b931dcddc886dc97232108f2039cd
BLAKE2b-256 checksum
How to use checksums
2a2b017b80cde401c7ebff4f0c9b7710b2e6f3141edd16ae74eb0dec7e11511a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.

Transparency log

Release files / inbody_api_mcp-0.1.0-py3-none-any.whl

Download URL inbody_api_mcp-0.1.0-py3-none-any.whl
Size 11.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
383c6b78d7eb59b8cc0e0979387b7716b98258614f404ece78f981308edde388
BLAKE2b-256 checksum
How to use checksums
6d43ce7c88359683a1e260165facd43e70c11bc53e65da186f164b53bf34e089
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.

Transparency log

Security for inbody-api-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for inbody_api_mcp-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page