MCP Bridge: turning legacy systems into tools an AI agent can use

The question that separates an AI demo from an agent in production is simple: does it reach the systems where the work actually happens? An assistant that only chats is a toy. An agent that reads the order in the ERP, checks stock in the database and replies in the customer's channel is operations.

The problem is that those systems were almost never built for an AI to talk to them. That's where the Model Context Protocol (MCP) comes in — and the way Zihin puts it into production with the MCP Bridge.

What MCP solves

MCP is an open standard for exposing tools to a language model in a structured way: each capability becomes a function with a name, a description and typed parameters. The agent doesn't "guess" how to use your system — it gets a contract.

Tip: Think of MCP as the "USB-C" of agent tools: a standard connector between the model and any system, instead of a custom integration for every case.

From legacy to MCP, without a rewrite

The declarative MCP Bridge maps existing resources to MCP tools without requiring any change to the source system. In practice, three paths cover most cases:

• via API — a REST/GraphQL endpoint becomes a tool with a schema derived from its contract.
• via Database — parameterized queries become safe tools, with an allowlist of operations.
• via native MCP — MCP servers you already expose plug straight into the runtime.

The mapping is declarative. You describe what to expose; the Bridge takes care of how to present it to the agent:

tool: consultar_pedido
source: erp.orders
input:
  pedido_id: string
returns: json

The part that usually gets stuck: on-premise

Much of the critical data isn't in the public cloud — it's behind the firewall. The Tunnel establishes outbound connectivity from your environment to the runtime, without opening inbound ports or setting up a VPN. The agent reaches the on-premise legacy system; your network stays closed to the world.

Warning: Reach without control is risk. Every tool exposed through the Bridge follows the policies of its scope (tenant → agent → user) — the topic of the next post in this series.

Connecting is the first pillar: Reach. It's what takes AI off the slide and puts it where the work is actually done. Want to see it in your own setup? Book a diagnostic.

Originally published in Portuguese on the Zihin blog. I work at Zihin, which connects AI agents to a company's systems and processes, with permissions, human approvals and cost tracking.