Summary
Dashboard configuration, not health data.
Everything here is setup: which integrations you can offer users, and where Terra delivers the data once they connect. One tool reads destination credentials back, so the key you hand this server is one that can see delivery secrets. The wearable readings themselves live behind Terra's data API, which these tools do not touch.
What it is
A server over the Terra API dashboard. It lists the wearable and health integrations available to you, and manages destinations: the places Terra delivers user data to once someone connects.
What you get
- The list of available Terra integrations
- A detailed integration list, filtered to what you have enabled and whether SDK use is required
- Your configured destinations
- The credentials held for a given destination
- A new developer destination, added from the conversation
- A destination switched active or inactive
- A destination deleted
- A reachability check against a configured developer destination
Requirements
A Terra developer account with an API key, and your developer ID — passed per call, or read from the environment when you leave it out. Runs with uvx terramcp.
Setup effort
One command plus a key — pip install terramcp, then supply credentials