Skip to main content
Deal Brain 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, Agents, Playbook, and Canvas 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 isn’t an administration surface. Organization membership, teams, integrations, provider mappings, API keys, organization settings, and the full field-definition policy surface are managed in the web app, not over MCP. 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 Deal Brain account. See MCP setup for client-specific instructions.

​
What the MCP surface exposes

It breaks into six areas: “Configuration” here means the capabilities in that last row. It does not mean organization administration: membership, teams, integrations, provider mappings, API keys, organization settings, and the full field-definition policy surface stay in the web app. Do that work there, then build on it over MCP. 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, agents, playbook sources, 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 agent or a signal returns it to a disabled state, so a half-applied change can’t run against live data. Re-enable explicitly.

​
Where to go next

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.