🏛️ Modernize a legacy SOAP service
Stack — Tools: WSDL import → typed tools · Secrets: Credentials vault · Gateway: MCP · Output: 2006 service, 2026 interface
Who it’s for — teams with a core system that still runs over SOAP and no appetite to rewrite it. What it does — imports a WSDL, turns each operation into a clean typed tool (almyty handles the envelope, headers, and namespaces), and republishes it as an MCP gateway — so modern agents and clients call the old service through a modern interface, untouched.
Build it
-
Import the WSDL. APIs → Connect API, point at the service’s WSDL URL. almyty parses the definitions and builds a JSON parameter schema from the XML types.
-
Review the generated tools. Each operation becomes a tool with typed inputs and outputs; the agent never sees the SOAP envelope.
-
Store the credentials once. WS-Security or basic auth goes in the Credentials vault, referenced from the tools — one place to rotate.
-
Publish it forward. Group the operations and publish an MCP gateway. A modern agent, Claude Code, or a partner’s system now calls your 2006 service with auth, rate limits, and audit in front.
Make it yours
- SOAP is one of several parsers — OpenAPI, GraphQL, and Protobuf import the same way, so a mixed old/new estate lands in one place.
- Wrap several legacy services behind one gateway for a unified surface.
- You didn’t migrate the system — you gave it a new front door.
Uses — Platform · Legacy · SOAP · MCP