MCP & Agents
In short: Tajo builds integrations between the systems you use. Agents inside a Tajo workspace build each sync, run it and work on the data it lands. MCP is how a model outside Tajo, such as Claude or ChatGPT, reaches the same connectors. Brevo’s own MCP server is a separate product that Tajo agents do not use.
Agents in a workspace
Every workspace starts with 15 agents. Nine of them are the agents sync work runs through. The Brevo Integration Architect builds a sync rule, the Sync Operator runs it, and seven more work on the contacts and orders it lands: Segment Builder, Compliance Reviewer, Engagement Designer, Performance Analyst, Orchestrator, Win-back and Customer Intelligence.
Two rules hold for all of them. A sync goes live only with your approval. A send goes out only with your approval, and only to contacts who opted in on that channel.
One card per agent, with what each never does: Tajo agents. How they fit around one sync: Tajo 101.
What an agent is made of
An agent is a role in your workspace, not a file you write. It has instructions, a fixed list of tools, and optional skills. Each tool carries a permission tier, and the tier decides what happens when the agent calls it. The details are on Agent specification. Hiring your own is on Building agents.
MCP tools Tajo serves
Tajo serves each connector to MCP hosts as a small, fixed set of tools rather than one tool per API endpoint. The Brevo profile is eight tools that cover the whole Brevo API:
| Purpose | Tools |
|---|---|
| Find an operation | brevo_search, brevo_describe |
| Read | brevo_query, one read request per call, with capped results |
| Write | brevo_propose stages a declared Brevo action; brevo_apply runs it once it is approved |
| Common tasks | brevo_customer, brevo_report, brevo_health |
No write reaches Brevo from this profile except through brevo_apply, after approval. Shopify and Webflow have their own profiles of the same shape, built around each integration’s own actions.
These endpoints come with a Tajo workspace. Workspaces are not open for self-serve sign-up yet: sign up for early access.
Brevo’s own MCP server
Brevo runs a hosted MCP server of its own. You can connect it to Claude, Cursor or another MCP client with a Brevo token, and it works without Tajo. Setup is on Brevo MCP Server. Tajo agents do not connect to it.