Inbody API MCP vs Marrow

In-depth architectural comparison of the Inbody API MCP and Marrow MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Inbody API MCP when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: get_profile, get_scan_count, list_scans.

Explore Inbody API MCP Details

Choose Marrow when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: health_summary, list_metrics, metric_daily.

Explore Marrow Details

Feature & Specification Comparison

Specification	Inbody API MCP Biology, Medicine and Bioinformatics	Marrow Biology, Medicine and Bioinformatics
Summary	MCP server for InBody body-composition data — scans, body fat, muscle mass, body water	Read-only MCP access to your own Apple Health data, mirrored from the Marrow iOS app.
Category & Scope	Biology, Medicine and Bioinformatics	Biology, Medicine and Bioinformatics

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "inbody-api-mcp": {
      "command": "uvx",
      "args": [
        "inbody-api-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "marrow-4": {
      "url": "https://skeletonarmy.tech/mcp"
    }
  }
}

Related MCP Server Comparisons