Skip to content

tryterra/terra

v2.1.0MIT

Set up, manage and debug your Terra API integration from your coding agent. Ask for the result and the agent does the work through the terra CLI or the bundled Terra API MCP server: environments, enabled providers, webhook destinations, credentials, connected users, delivered events and billing, with skills for the Unified API, the mobile and streaming SDKs, planned workouts, routes, lab reports, Vantage and Models.

terra-mcp

Manage a Terra API account through the Terra API admin MCP server (access.tryterra.co/api/v3/admin/mcp) from a chat assistant such as claude.ai, Claude Desktop or ChatGPT, even one that can run code, or where the terra CLI cannot be used: environments, enabled providers, data scopes, webhook destinations, delivered events and resends, connected users, models, billing, team, and docs_ask. Use in a chat assistant for any Terra API account task, when its tools, such as environments_read, events_read or unified_api_destinations_write, are available, when a tool returns approval_required or asks for an approval_id, when connecting Terra API to Claude, ChatGPT, Cursor, VS Code or Codex as an MCP server, or when debugging insufficient_scope, dev_id_not_found or validation_failed. Not the AI Interface MCP that reads end users' health data. Coding agents such as Claude Code, Codex and Cursor use terra-cli instead.

Version
1.1.0
License
MIT
Compatibility
Requires the Terra API admin MCP server, connected and signed in
Read SKILL.md at the source

Pinned to revision 82b2e4751b92, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.