terra_get_integrationsLABSCO 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
USE CASES
01
Seeing which wearables you can offer users today
List the integrations, then take the detailed view filtered to the ones you have enabled and whether they need the SDK.
02
Adding a new place for Terra to deliver data
Add the developer destination, then read the destination list back to confirm it registered.
03
Pausing a delivery destination during an outage
Set it inactive so deliveries stop, and set it active again when the endpoint is back.
04
Checking a destination is reachable before you rely on it
Ping the configured destination rather than waiting for a user's data to be the first thing to arrive.
05
Retrieving the credentials configured for a destination
Read back what Terra holds for that destination, when you are reconciling it against your own store.
06
Removing a destination you no longer use
List what is configured, then delete the one that is obsolete.
17 tools
Listed in project docs. Your client may show a different list.
terra_get_detailed_integrationsget_destinationsget_developer_destination_credentialsdelete_destinationset_destination_stateadd_developer_destinationping_developer_destinationset_provider_keysget_provider_keysget_developer_providersadd_providersdeactivate_providerset_provider_stateget_providers_by_popularityadd_custom_credentialsget_custom_credentialsBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- uvx on PATH
- TERRA_API_KEY in your environment
- TERRA_DEV_ID in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install terramcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"terramcp": {
"command": "uvx",
"args": [
"terramcp"
],
"env": {
"TERRA_API_KEY": "<YOUR_TERRA_API_KEY>",
"TERRA_DEV_ID": "<YOUR_TERRA_DEV_ID>"
}
}
}
}Zed
ZED · JSON
{
"context_servers": {
"terramcp": {
"command": "uvx",
"args": [
"terramcp"
],
"env": {
"TERRA_API_KEY": "<YOUR_TERRA_API_KEY>",
"TERRA_DEV_ID": "<YOUR_TERRA_DEV_ID>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"terramcp": {
"command": "uvx",
"args": [
"terramcp"
],
"env": {
"TERRA_API_KEY": "<YOUR_TERRA_API_KEY>",
"TERRA_DEV_ID": "<YOUR_TERRA_DEV_ID>"
}
}
}
}
