SOAP and WSDL — first-class, not an afterthought
Point AnythingMCP at a WSDL URL and it parses the contract into one MCP tool per SOAP operation. WS-Security, basic auth and TLS client certificates are all built in. We've connected SAP, .NET WCF, banking middleware, and 15-year-old industrial control systems — all without writing a line of integration code.
Talk to your production database safely
PostgreSQL, MySQL, MariaDB, MSSQL, Oracle, MongoDB, SQLite. Each tool is whitelisted. Each invocation is audit-logged. Each connector can be scoped to a read-only credential when that's what the situation calls for. The AI agent never sees the raw connection string.
Audit log stays on your infrastructure
Every tool invocation — request, response, duration, status, user — lands in your own PostgreSQL audit table. Not on someone else's gateway. Not in a SaaS dashboard. When your security team asks "what did the AI agent do with the SAP credentials last quarter?", the answer is one SQL query away.
Why this matters in 2026
The hosted MCP-gateway space is crowded. The MCP-for-legacy space is mostly empty. We're fine with that — it's the lane we were built for, and the lane we keep doubling down on.
# Import a WSDL contract and get MCP tools for every operation
curl -X POST http://your-anythingmcp/api/connectors \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "Legacy SAP Service",
"type": "SOAP",
"wsdlUrl": "https://sap.internal/services/Customer?wsdl",
"authType": "WS_SECURITY",
"authConfig": { "username": "sapuser", "password": "{{SAP_PASS}}" }
}'