Renpho MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENPHO_EMAIL | Yes | Your Renpho Health account email address | |
| RENPHO_PASSWORD | Yes | Your Renpho Health account password |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userB | Get current Renpho user information |
| get_scale_usersB | Get linked Renpho scale-user IDs and table mappings discovered from the account |
| get_latest_measurementB | Get the most recent body composition measurement from Renpho scale |
| get_body_compositionB | Get detailed body composition analysis with health classifications |
| get_weight_trendD | – |
| get_measurementsD | – |
| get_sync_diagnosticsD | – |
| refresh_dataA | Clear Renpho auth/measurement caches and re-fetch account state. Useful after taking a new measurement or after the mobile app syncs. |
| health_checkB | Check the health status of the Renpho MCP server and API connection |
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 9 tools
Most tools target clearly distinct resources or actions: user info, scale-user mappings, latest measurement, body composition, trend, refresh, health, and diagnostics. The main ambiguity comes from missing descriptions on get_measurements, get_weight_trend, and get_sync_diagnostics, plus some potential overlap between get_sync_diagnostics and health_check.
All tools use snake_case, which is consistent and readable. The pattern is mostly get_* for retrieval, but refresh_data and health_check deviate from the verb_noun convention, and health_check uses noun_verb ordering.
Nine tools is well-scoped for a read-only Renpho scale integration. Each tool appears to cover a distinct user need or operational role, with no excessive bundling or unnecessary endpoints.
The surface covers the core read-only lifecycle: current user, linked scale users, latest and historical measurements, body composition, trends, refresh, diagnostics, and health. Minor gaps include missing descriptions for key retrieval tools and no explicit measurement-detail or date-range filtering operation, though get_measurements may cover this.