Integrations Overview

Mesh Pilot does not replace your tools. Shopify stays the source of truth for orders. HubSpot stays the source of truth for deals. Meta stays the source of truth for ad state. We orchestrate flows across them and mirror enough state inside the cockpit that you never have to leave to verify what just happened.

​

How a connection works

​

What we mirror, what we don’t

We mirror enough state to surface and act:

• Recent campaigns, ad sets, and spend (for ad platforms).
• Recent orders, customers, and product state (for Shopify).
• Pipeline stages and recent deal activity (for HubSpot).
• Recent calls, transcripts, and outcomes (for LiveKit).

We don’t replicate your full source-of-truth dataset. We don’t try to be a parallel Ads Manager or a parallel CRM. If you disconnect a platform, the cockpit’s view of it goes empty — but your data stays safe in the source tool. We do not eat your data.

​

The MCP layer

Under the hood, agents talk to external platforms through a thin shared client layer. For REST-shaped APIs (Meta, Amazon) the client calls the platform’s HTTPS endpoints directly. For richer wrappers (Google Ads’ GAQL query language) the client talks to a small MCP server that handles the heavy lifting. Either way, the per-brand OAuth tokens you authorize at connection time are what gate every call — agents can only ever act on what your brand has authorized. Mesh Pilot also exposes its own MCP server, so you can drive the cockpit from your AI client (Claude, Cursor, etc.) over the same authorized connections. See Developers & MCP.

​

What disconnect does

Disconnect a platform from Settings → Integrations and Mesh Pilot revokes its access upstream (where supported), deletes the local OAuth token, and clears the cockpit’s mirror of that platform’s data for the brand. Your data in the source tool is untouched.

​

Supported platforms today