BARRYBARRY

Developers

Drive BARRY from any AI agent.

A built-in Model Context Protocol server exposes BARRY to any MCP-capable assistant or automation.

Every team is wiring AI assistants into their tooling right now, and each integration usually means another bespoke API client to build and maintain. BARRY avoids that by speaking the Model Context Protocol directly. The server exposes the platform as a set of MCP tools, so any MCP-capable assistant or automation can list connections, create transports, launch runs, read status and query lineage or client health – without anyone writing an integration layer first. It runs over the same secured channel as everything else, which means no new inbound surface and no second set of credentials to manage. The routine parts of running a data platform can be handed to an agent, while the guardrails stay where you put them.

  • Standard MCP over the existing secure channel
  • Create connections and transports programmatically
  • Trigger runs and read status
  • Query lineage, schema history and client health
MCP tools
The MCP tool list an agent can call: list_connections, create_transport, get_lineage, run_now and more.
Placeholder · image to be produced
Standard protocol
Works with any MCP-capable agent.
Same security model
No new inbound surface.
Automate anything
Let agents run the boring parts.

Ready to unlock your data?

See how BARRY brings your on-premises data to the cloud — safely, and on your terms.