Inbound through MCP
Use a connected MCP client to create an Inbound Server, find webhook requests and inspect their saved HTTP data. To set up the connection, follow the MCP Quickstart.
Receive a test webhook
Ask: “Show available Adal Cloud regions. Create a Server named MCP test in the region I choose. Allow POST and show me its HTTPS URL once it is synced.”
Once the Server is synced, ask the client to start watching for new requests on MCP test. Send a test webhook, replacing
YOUR_SERVER_URLwith the HTTPS URL returned by Adal Cloud:curl -X POST 'YOUR_SERVER_URL?source=mcp-quickstart' \ -H 'Content-Type: application/json' \ --data '{"event":"mcp-test","count":1}'Ask: “Find the test webhook on MCP test. Show its status, the
sourcequery parameter and the value and JSON type ofcount.” If the client did not see it while watching, ask it to look in the Server’s request history.
Inspect saved requests
Filter the Server’s history by time or status. Ask why a request was rejected or ask to inspect a specific header, query parameter or body field. Use synthetic payloads for testing and request only the fields you need. Captured requests can contain credentials or other private data.
The request snapshot can include up to 16 KiB of the body. To read a larger saved body, ask for the full body of that request. MCP can return up to 1 MiB of original body bytes as UTF-8 text or base64. Rejected requests may have no saved body. See Requests and delivery history and Storage and retention.
Update or remove a Server
Specify which Server and fields you want to change. For example: “On MCP test, allow only POST and leave the other settings as they are.” Wait for synchronization before checking the new settings with another request.
When you are done, ask to delete MCP test. If a Router uses the Server, unlink it in the Dashboard first. After deletion syncs to the region, the URL stops accepting webhooks.