Build on Tempo

Tempo is infrastructure, not a destination. Your organization’s intelligence layer (deals, observations, artifacts, Playbook guidance, and Themes) is reachable through open interfaces, so you can build on it rather than around it. There are two programmatic surfaces. Which one you want depends on what you are building.

Which surface do I want?

MCP server

For AI agents and sellers’ AI tools. Claude, ChatGPT, Cursor, or your own agent connects over MCP with OAuth per user. Tools are self-describing, so the agent discovers what it can do.

REST API

For dashboards, ETL, and internal tools. Versioned endpoints under /api/v1, an organization API key, and predictable request and response shapes.

	MCP	REST API
Built for	Agents and assistants	Services and scripts
Auth	OAuth, per user	Organization API key, Bearer token
Surface	Deals, meetings, CRM fields and updates, observations, artifacts, Playbook, Themes, Skills, and permitted configuration	Deals, deal state, deal updates, action items, meetings, Themes, sales process, the query API, and agentic search
Shape	Self-describing tools grouped into toolsets	Versioned HTTP endpoints under `/api/v1`
Use when	The caller reasons about what to call	You know exactly what you want

Both surfaces read the same underlying data. An agent over MCP and a nightly job over REST see the same deals. MCP is not an administration surface. Organization membership, teams, integrations, provider mappings, API keys, and organization settings stay in the web app.

Connect over MCP

Open Settings → Connections in Tempo and pick the card for your client. The setup dialog gives you the server URL:

Field	Value
Name	`Tempo`
MCP server URL	`https://findtempo.co/api/mcp?toolset=seller_default`
Authentication	OAuth

Turn on Include Skills and Build tools in that dialog to get ?toolset=seller_default,build instead. See MCP toolsets for what each toolset contains and MCP setup for client-specific instructions.

What the MCP surface exposes

Tools are grouped into five toolsets:

Toolset	Tools cover
Core	Who is signed in, their organization and role, connected sources, and active toolsets
Workspace	Deals, current deal state with citations, and meetings
CRM	Field catalogs and definitions, current field values, proposed CRM updates, and creating CRM records
Context	Cited observations, synthesized deal answers, finding deals in a similar situation, artifacts, Playbook guidance, and Themes
Build	Skills, Playbook sources, and linking Slack, Notion, and Granola sources to deals

Build tools are permission-gated. A caller sees only the actions their account can take, so do not infer that data is missing from an unavailable action.

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. Playbook sources and Skills carry a revision. Pass the revision you read; a concurrent edit rejects the write instead of silently overwriting it. On conflict, list again and reapply. Organization-wide field changes need an admin. Only the deal owner or an organization admin can approve, reject, or create CRM update proposals on a deal. Creating or changing organization-wide Tempo-managed field definitions requires organization admin access.

Where to go next

MCP toolsets

Choose which tool groups a connection exposes.

MCP tool reference

Browse every tool available to connected agents and assistants.

REST API reference

API keys, endpoints, and the query API.

​Which surface do I want?