Skip to main content
Tempo is infrastructure, not a destination. Your organization’s customer context is reachable through open interfaces, grounded in your own sales process, playbooks, and deal state — so you can build on it rather than around it. There are two programmatic surfaces, and which one you want depends on what you’re building.

​
Which surface do I want?

MCP server

For AI agents. A broad capability surface, including Signals, Automations, Playbook, Canvas, and Tempo-managed field configuration. Tools are self-describing, so an agent can discover what it can do. OAuth per user.

REST API

For traditional integrations. Dashboards, ETL, internal tools, scheduled jobs. Versioned endpoints, Bearer API key, predictable request/response shapes.
MCP is broad, but it is not a complete administration surface. Organization membership, teams, integrations, provider mappings, API keys, and organization settings remain in the web app. Organization-wide field and key-field changes over MCP require organization admin access. Both hit the same underlying data, so mixing them is fine — an agent over MCP and a nightly job over REST will see the same deals.

​
Connect over MCP

Point any MCP client at that URL and authenticate with your Tempo account. See MCP setup for client-specific instructions. See the MCP tool reference for the complete tool inventory and availability notes.

​
What the MCP surface exposes

It breaks into six areas: “Configuration” here means the capabilities in that last row. It does not include membership, teams, integrations, provider mappings, API keys, or organization settings. Configuration tools are permission-gated. A caller only sees the actions its account is allowed to take — don’t infer availability from an empty result.

​
Design notes worth knowing

Tools report their own readiness. Configuration tools return allowed actions and named blockers rather than failing opaquely. Read those before retrying. Mutations are revision-checked. Signals, automations, Playbook artifacts, and canvas templates all carry a revision. Pass the revision you expect; a concurrent edit rejects the write instead of silently overwriting. On conflict, re-list and reapply. Configuration changes disable the thing they change. Editing an automation or a signal returns it to a disabled state. Re-enable it when your changes are complete.

​
Where to go next

MCP tool reference

Browse the tools available to connected agents and assistants.

REST API reference

Auth, endpoints, and the query API.

Building on Canvas

Render authored templates from your own agent, including auth, key resolution, and the render lifecycle.