All posts

Connectors first, rewrites second

Why we put an MCP layer in front of legacy systems before touching a line of the old code — and how that de-risks modernization.

Most legacy modernization projects fail the same way: they start with a rewrite. A team looks at a decade-old system, decides it's beyond saving, and quietly signs up for an 18-month big-bang replacement. Halfway through, the business changes, the old system keeps evolving, and the new one is perpetually "almost ready." Nobody wins.

We do it in the opposite order. Connectors first, rewrites second.

Wrap, don't replace

The first thing we build isn't new code — it's an interface. We wrap the existing system in MCP connectors: typed, permissioned tools that expose what the system does (issue a refund, look up an account, post a ledger entry) without exposing how it does it.

The moment that layer exists, three things become true:

  • AI agents can act on the system safely, today — through a narrow, auditable surface instead of direct database access.
  • The old code is now an implementation detail. It can be refactored, replaced piece by piece, or left alone — and nothing downstream notices.
  • You have a seam. Every future change happens behind a stable contract, with tests guarding behavior on both sides.

Refactor behind the contract

With the connector in place, modernization stops being a cliff and becomes a staircase. We characterize the current behavior with tests, then move one path at a time from the legacy internals to clean, agent-ready services. Production never freezes, because the contract never moves.

This is the difference between "we're rewriting the billing system" (terrifying) and "we're changing how issue_refund is implemented, and the tests still pass" (routine).

Why this beats the big-bang rewrite

A rewrite bets everything on a single future date. A connectors-first migration delivers value on week one — agents can start automating real workflows against the wrapped system immediately — and de-risks everything after it. You get the agentic capabilities early and the clean internals eventually, without ever betting the business on a flip of the switch.

If you're staring at a system everyone's afraid to touch, that fear is the signal. Wrap it, and it stops being scary.

Want to talk through your stack? Email us.

Have a legacy system you'd like to make agent-ready?

Book a call