inbody-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INBODY_LOGIN_ID | Yes | Registration phone number, digits only (no country code or +). Used as login ID. | |
| INBODY_LOGIN_PW | Yes | Password for the InBody account. | |
| INBODY_COUNTRY_CODE | No | ISO country code for region routing. | US |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Get the InBody user profile. Returns identity and baseline body metrics (name, gender, age, height, weight, email) useful for interpreting scan results. |
| get_scan_countA | Get the total number of InBody scans available for the account. |
| list_scansA | List InBody scans with headline metrics, newest first. Returns a slim summary per scan (date, weight, BMI, %body fat, skeletal muscle mass, body fat mass, total body water, equipment). Use get_scan with a scan's raw_datetime for the full metric set. Args: limit: Maximum number of scans to return (default 20). offset: Pagination offset into the scan history (default 0). |
| get_scanA | Get the full metric set for a single InBody scan. Returns the complete BCA (body composition), MFA (BMI/%fat/muscle with norm ranges), and IMP (segmental/multi-frequency impedance) blocks. Args: raw_datetime: The scan's raw DATETIMES value (YYYYMMDDHHMMSS) from list_scans. Defaults to the most recent scan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_profile returns user identity and baseline metrics; get_scan returns full metrics for a specific scan; get_scan_count returns the total number of scans; list_scans returns a summary list of scans. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: get_profile, get_scan, get_scan_count, list_scans. The convention is uniform and predictable.
With 4 tools, the server is well-scoped for an InBody API: it provides profile retrieval, scan listing, scan detail, and scan count. No unnecessary tools, and the count is appropriate for the domain.
The tool set covers the essential read operations for InBody scans and user profile. A minor gap is the lack of filtering or searching scans by date range, but the core workflow (list, get detail, count) is fully supported.