WxMCPServer

For a local webMethods Integration Server, load the WxMCPServer package from the webMethods Package Registry using Service Designer. For IBM webMethods Hybrid Integration (SaaS), add the GitHub repository as an external package to your project and sync it.

Set the required global configuration variables on your Integration Server. At minimum, set wxmcp.auth.type (e.g., API_KEY) and wxmcp.tool.catalog.base.url to point to your API Gateway's tool catalog endpoint.

wxmcp.auth.type=API_KEY
wxmcp.tool.catalog.base.url=https://<gateway-host>:<port>/gateway/WxMCP-Tool-Catalog/1.1
wxmcp.api.key.headername=x-Gateway-APIKey
wxmcp.tool.response.mode=structured
wxmcp.response.code=http

After deploying, the MCP HTTP endpoint is available at http://<Integration-Server-Host>:<Port>/mcp. Test it with a simple HTTP request to confirm the server is running and returning a valid MCP response.

curl http://localhost:5555/mcp

Because the server runs as an HTTP MCP endpoint (not stdio), use the mcp-remote bridge package in your Claude Desktop config. Pass authentication credentials as HTTP headers.

{
  "mcpServers": {
    "wxmcpserver": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://<integration-server-host>:<port>/mcp",
        "--header", "x-auth-type:API_KEY",
        "--header", "x-api-key:<your-api-key>",
        "--header", "x-tool-catalog-base-url:https://<gateway-host>:<port>/gateway/WxMCP-Tool-Catalog/1.1",
        "--header", "x-api-key-headername:x-Gateway-APIKey",
        "--header", "x-tool-response-mode:structured",
        "--header", "x-response-code:http"
      ]
    }
  }
}

Restart Claude Desktop and ask Claude to list available tools. The server dynamically loads tool definitions from the API catalog. Invoke a tool by name and confirm that the response passes through the API Gateway's security policies correctly.