Choose an interface
API v1 is the source of truth. The SDK, CLI, and MCP server are clients of that API rather than independent integration surfaces.
| Need | Recommended interface | Why |
|---|---|---|
| A production service in any language | API v1 | Stable HTTP contract and explicit scopes |
| A Node.js or TypeScript service | TypeScript SDK | Typed resources, retries, timeouts, and pagination |
| Shell scripts, CI, or an operator workflow | CLI | Structured output and stable exit codes |
| Read-only access from a supported AI host | MCP server | Small, local, read-only tool surface |
| An existing integration that already uses v0 | API v0 | Compatibility only; plan a migration |
Recommended architecture
Section titled “Recommended architecture”Build automation against API v1 or the SDK. Use the CLI as an operator and scripting interface. Treat MCP as an optional adapter for human-supervised read workflows, not as the foundation of an integration.
MCP does not introduce a second TeamGrid API, a remote TeamGrid session, or MCP-specific credentials. Every MCP request still passes through the API v1 authentication, scope, tenant, and region checks.