eufylife-scale-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EUFYLIFE_EMAIL | Yes | EufyLife account email | |
| EUFYLIFE_COUNTRY | No | Two-letter country code of the account, e.g. GB, DE | US |
| EUFYLIFE_PASSWORD | Yes | EufyLife account password | |
| LANGFUSE_BASE_URL | No | Langfuse URL for self-hosted or regional instances (default: Langfuse Cloud) | |
| LANGFUSE_PUBLIC_KEY | No | Langfuse public key. Tracing is on only when both LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY are set. | |
| LANGFUSE_SECRET_KEY | No | Langfuse secret key. Tracing is on only when both LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY are set. | |
| LANGFUSE_CAPTURE_DATA | No | Set to true to include tool inputs, outputs and error messages. Default false. |
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 |
|---|---|
| list_membersA | List the member profiles (people) on this EufyLife account. |
| get_latest_measurementB | Most recent weigh-in with its body composition. Check |
| get_measurement_historyB | Weigh-ins from the last |
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 3 tools
The three tools target distinct resources: member listing vs. measurement retrieval. However, get_latest_measurement is essentially a special case of get_measurement_history (the newest entry), so an agent could reasonably confuse the two when only the latest reading is needed.
All tools follow a consistent verb_noun snake_case pattern: list_members, get_latest_measurement, get_measurement_history. The verbs are appropriate and predictable for their actions.
Three tools is a small but reasonable surface for a read-only smart-scale integration. Each tool has a clear role, though the set sits at the lower bound and leaves little margin for additional read operations.
The core read paths are covered: enumerate members, fetch the latest body-composition measurement, and retrieve historical weigh-ins. Minor gaps exist (e.g., no tool to fetch a single measurement by ID, no member-specific filter explicitly documented), but nothing that would block typical agent queries.