Talks directly to a MuleSoft-built MCP server exposing Order Fulfillment resources and tools — inspect orders, invoke actions, and watch the JSON-RPC wire traffic.
Console (You)
MuleSoft MCP Server
Fulfillment Backend
Connection
Demo modeSimulated MCP server, no network calls
Not connected
Resources
Connect to discover resources exposed by the server.
Tools
Connect to discover callable tools.
No resource selected
Connect, then choose a resource on the left — such as an order list or a fulfillment queue — to view it here.
No tool selected
Pick a tool on the left — such as fulfill_order or check_inventory — to build a call.
No traffic yet
Every JSON-RPC request and response between this console and the MCP server will be logged here.
One goal in, orchestration handled. The agent discovers what your MuleSoft MCP server exposes and calls those tools itself, in whatever sequence the goal requires — no custom integration code per use case.
Replay modePlays a recorded agent run — no API key, no network
Sent directly from this browser tab to Anthropic — never stored. Requires demo mode off and a reachable MCP URL.
Live mode needs demo mode off and a real MCP server URL — Anthropic's servers call the MCP endpoint directly.
No agent run yet
Pick a scenario and run the agent to watch it work through the fulfillment tools step by step.
JSON-RPC 2.0 over Streamable HTTP (MCP spec). In live mode, the target MuleSoft MCP server must allow CORS from this page's origin, or this file should be served from an origin the server trusts. Demo mode simulates initialize / resources / tools / tools-call round-trips locally. The Agent tab uses Anthropic's native MCP connector (Messages API, mcp_servers field, beta header mcp-client-2025-04-04) — Anthropic's servers call your MCP endpoint directly, so it needs a real, internet-reachable URL and is unaffected by browser CORS.