Back to Guides

How to Convert SOAP APIs to MCP Servers

Transform legacy SOAP/WSDL web services into modern MCP servers using AnythingMCP. Bridge enterprise SOAP APIs to AI agents without rewriting anything.

Why SOAP APIs Still Matter

Despite the rise of REST and GraphQL, SOAP web services remain the backbone of enterprise IT. Banks, insurance companies, healthcare providers, and government agencies rely on millions of SOAP endpoints that power critical business processes.

The problem? AI agents speak MCP, not SOAP. Until now, connecting AI to these legacy systems required custom middleware, months of development, and deep SOAP expertise.

AnythingMCP: SOAP to MCP in Minutes

AnythingMCP automatically parses WSDL definitions, maps SOAP operations to MCP tools, and handles all the XML serialization and deserialization behind the scenes.

Step-by-Step Guide

Step 1: Deploy AnythingMCP

Clone the repository and start the application with Docker Compose:

git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d

This starts PostgreSQL, the backend API (port 4000), and the dashboard (port 3000).

Step 2: Create a SOAP Connector

Open the AnythingMCP dashboard at http://localhost:3000 and create a new SOAP connector. Provide the WSDL URL of your service — AnythingMCP will automatically parse it and discover all available operations.

Step 3: Automatic WSDL Parsing

AnythingMCP reads your WSDL and automatically:

  • Discovers all SOAP operations (e.g., getOrder, createInvoice, updateCustomer)
  • Maps complex XML types to structured MCP tool parameters
  • Generates human-readable descriptions for AI agents
  • Handles SOAP envelopes, headers, and namespaces transparently

Step 4: Configure Authentication

In the connector settings, configure authentication for your SOAP service. AnythingMCP supports WS-Security, Basic auth, and custom SOAP headers. Environment variables can be used to store credentials securely.

Step 5: Customize Tool Mapping

In the dashboard, review which operations to expose and customize how they appear to AI agents. You can rename tools, improve descriptions, and exclude dangerous operations.

Step 6: Test and Connect

Use the built-in testing interface to call each SOAP operation directly from the dashboard. Then configure your MCP client:

{
  "mcpServers": {
    "my-soap-service": {
      "url": "http://localhost:4000/mcp"
    }
  }
}

Common Enterprise SOAP Use Cases

| SOAP Service | MCP Tool Generated | AI Agent Use Case | |---|---|---| | SAP RFC/BAPI | get_material_details | "Look up inventory for part X" | | Oracle EBS | create_purchase_order | "Create a PO for 100 units" | | Healthcare HL7 | get_patient_record | "Retrieve patient history" | | Banking Core | get_account_balance | "Check account status" | | Insurance Claims | submit_claim | "File a new insurance claim" |

Handling Complex XML Types

SOAP APIs often use deeply nested XML structures. AnythingMCP flattens these into intuitive JSON parameters that AI agents can easily work with.

Best Practices

  1. Start read-only — Expose query operations first, then add write operations
  2. Use WS-Security — Never pass credentials in plain text
  3. Test with your WSDL — Verify the WSDL is accessible from the AnythingMCP server
  4. Rate limit — SOAP services often have strict rate limits; configure accordingly

Next Steps