Need MCP Wrapping for Legacy SOAP/XML Systems
Enterprises need a way to expose legacy SOAP, XML, and other pre-REST backends as MCP server tools so agents can read and write to systems no team wants to evolve — without forcing a multi-year rewrite or rebuild of the underlying stack.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Tina, the architect, owns a portfolio that still includes core systems running on SOAP, XML-RPC, and other pre-REST protocols. Nobody on the team wants to touch those systems — they are stable, business-critical, and the original engineers are gone. Tina now needs agents and copilots to read and write through them. She does not have permission, budget, or appetite to migrate the backend; she needs a layer in front that speaks SOAP to the legacy stack and exposes MCP tools to the agents.
Problem Context
- Critical enterprise systems still expose SOAP / XML-RPC / WSDL contracts that pre-date REST and have no native JSON or MCP affordance
- Original engineering teams are gone; no one wants to evolve the backend, but the data inside it is essential
- Agents and copilots need read / write access to these systems for routine workflows (account lookups, claims, transactions, inventory)
- A full rewrite to REST-then-MCP is a multi-year program; the agent rollout is a six-month commitment
Problem Impact
- Agentic AI projects stall at the boundary of the legacy stack and never deliver against the business case
- Teams write one-off REST adapters per legacy backend that immediately diverge in shape, naming, and error handling
- The agent surface area for those adapters becomes a fresh tribal-knowledge silo — exactly the problem agents were supposed to solve
- Without a shared wrapping pattern, every legacy-system-to-agent integration is bespoke and outside any governance or observability layer
Naftiko Today
- Declarative consumes for SOAP / XML-RPC / WSDL backends turn legacy contracts into named, governed integration points without code in the agent path
- A single capability YAML can speak SOAP outbound and expose MCP tools inbound, with the request / response transformation living next to the capability spec
- REST exposure side-by-side with MCP means the same wrapped legacy backend is reachable from both classic API consumers and modern agents
- Capability lifecycle metadata (owner, stability, changelog) attaches to the wrapper so the agent-facing surface inherits enterprise governance from day one
Naftiko Tomorrow
- Schema generation for legacy contracts (Second Alpha) would auto-generate MCP tool descriptions from WSDL / XSD, removing the hand-written translation step
- A2A adapter (Second Alpha) would let the legacy-wrapping capability sit inside agent-to-agent chains so legacy data is reachable from any agent layer, not just the front-line one
- Backstage capability cards (Third Alpha) would surface every wrapped legacy backend in the developer catalog with topology back to the SOAP origin, making agent-readiness visible to the architecture team
- Reference patterns library (v1.1) would ship templates for the most common legacy-to-MCP shapes — banking core, ERP, claims, EDI gateway — so the first wrapping is a fill-in, not a build