Integration layer
Connectors, MCP, the fleet and the catalogue. How Adam AI meets the systems you already run.
The Integration layer is how Adam AI meets the systems you already run, and how boxes across the fleet share what they learn without sharing what they must not.
What it holds
- Connectors. Adapters to systems of record: Microsoft 365, Xero, GoHighLevel, ConnectWise, Apollo, and the long tail. Each connector exposes a described set of actions that the Security layer can grant per session.
- MCP servers. The open protocol that lets any tool present itself to an agent in a standard way. Adam AI ships a Tools arsenal of MCP servers and can run yours.
- The catalogue. The shared register of skills, tools and integrations. Slugs are lowercase-kebab in both directions so that every box names things the same way.
- The fleet. Every Adam AI box we operate. Boxes receive catalogue updates; they contribute back only through the security-gated harvest inbox, which a person reviews.
- Local integrations. Anything a customer builds or installs for themselves is owned by that customer and never syncs anywhere.
Fill, don't blank
Every receiver in the Integration layer follows one rule: an update may fill a field that is empty, but never blank a field that has a value. A sync cannot erase what a person typed.
Workflows are a component, not a company
Workflow automation platforms are useful and we integrate with them. But a workflow is one component of running a business, alongside people, data, models and controls. You cannot run a business inside a workflow tool, so Adam AI treats workflows as something the Integration layer orchestrates, not as the platform itself.
What it never does
- It never syncs a customer's local integrations.
- It never harvests secrets. Credentials are a non-class in the catalogue.
- It never lets a connector act outside a session. Every call is attributed.
Why it matters
Integration is where most AI projects die: one more tool bolted on, one more set of keys, one more silo. Putting integration in its own layer means a new system is a new connector, with the same gates and the same audit as every other, on day one.
Related: Security layer, Architect.