Welcome to Tajo
Choose a listed tool or type any tool name.
Illustration · sample data
Sync example
Source
Shopify
Connector status: In progress
Destination
Brevo
Connector status: Live
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Tajo is an agentic integration builder. You describe, in plain language, the sync you want between two SaaS tools. Tajo’s agent builds it: the field maps, the reverse ETL jobs that move the data, and MCP tools your AI client can call. An MCP UI lets you review, approve and run each sync from inside the AI client you already use.
Tip
Tajo is not tied to any vendor. Shopify, HubSpot, Stripe, Brevo and any documented REST API are connectors. The builder, the approvals and the MCP layer stay the same whichever tools you pair.
What Tajo builds
- Field maps - A readable mapping from the source tool’s fields to the destination’s. You approve it before anything runs.
- Reverse ETL - Contacts, orders, products and events move from the system that records them into the tools that act on them, on a schedule or as they happen.
- MCP tools - Every integration is also exposed as MCP tools, so Claude, ChatGPT or your own agent reads and writes through one governed layer instead of raw API keys.
- MCP UI - Approve field maps, watch sync runs and fix failures from an interface that opens inside your AI client.
Governed by default
Consent and approval rules run before any write. Every decision lands in an audit history you can check.
How a first sync works
- Pick a source and a destination - Choose the two tools, for example a store and a messaging tool. See the integration guides for the pairs that are documented.
- Describe the sync - Say what should move and when: “Send new Shopify customers and their orders to Brevo every hour.”
- Review the field map - The agent proposes how each field maps. Approve it, or correct it, in the MCP UI.
- Run it and watch it - Run the sync once and check the result, then put it on a schedule. The same integration is now available as MCP tools.
Where to go next
- Integration layer - How Tajo connects a source tool to a destination tool, with a guide for each documented pair
- MCP and agents - How integrations are exposed as MCP tools and how agents are defined
- A worked example: Shopify to Brevo - One complete sync, end to end
Info
Connecting Brevo? The Quick Start Guide shows how to get Brevo API credentials and make a first API call.