Inbody API MCP vs ChemCP
A side-by-side look at the Inbody API MCP and ChemCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Inbody API MCP for biology & bioinformatics work as a local process; choose ChemCP for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Inbody API MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INBODY_LOGIN_ID, INBODY_LOGIN_PW, INBODY_COUNTRY_CODE. - You want tools like
get_profile, get_scan_count, list_scans.
Choose ChemCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 49/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | INBODY_LOGIN_IDINBODY_LOGIN_PWINBODY_COUNTRY_CODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Inbody API MCP | View ChemCP |
Tools & capabilities
Inbody API MCP tools 4
get_profileUser identity and baseline metrics (height, weight, age, gender)get_scan_countTotal number of scans on the accountlist_scansChronological scan summaries (weight, BMI, % body fat, muscle mass)get_scanFull metric set for one scan (BCA / MFA / IMP blocks)
ChemCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Inbody API MCP
{
"mcpServers": {
"inbody-api-mcp": {
"command": "uvx",
"args": [
"inbody-api-mcp"
],
"env": {
"INBODY_LOGIN_ID": "YOUR_INBODY_LOGIN_ID_HERE",
"INBODY_LOGIN_PW": "YOUR_INBODY_LOGIN_PW_HERE",
"INBODY_COUNTRY_CODE": "YOUR_INBODY_COUNTRY_CODE_HERE"
}
}
}
}
ChemCP
{
"mcpServers": {
"chemcp": {
"command": "npx",
"args": [
"-y",
"cloudflared"
]
}
}
}
Frequently asked questions
Inbody API MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. ChemCP belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Inbody API MCP for biology & bioinformatics work and ChemCP for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Inbody API MCP has no declared pricing — check the project's own site. ChemCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add inbody-api-mcp and chemcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Inbody API MCP has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 14 GitHub stars. ChemCP has 40/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.