MCP setup

Connect agents to a paid remote MCP endpoint

Use AutoBrowser Approval Cloud as a hosted MCP server with bearer-token access, structured tool outputs, and audit receipts.

Endpoint

https://autobrowserapproval.clauxel.com/mcp

Authentication

Production calls require a paid bearer token. The checkout and token-claim endpoints return machine-readable instructions for agents.

Available tools

  • request_page_approval returns structured JSON with verdict, reason, receipt_id, usage_units, and next_action.
  • read_session_state returns structured JSON with verdict, reason, receipt_id, usage_units, and next_action.
  • submit_approval_result returns structured JSON with verdict, reason, receipt_id, usage_units, and next_action.
  • export_approval_receipt returns structured JSON with verdict, reason, receipt_id, usage_units, and next_action.

Example call

{"jsonrpc":"2.0","id":"call-1","method":"tools/call","params":{"name":"request_page_approval","arguments":{"sample":"AutoBrowser Approval Cloud sample with public-safe workflow context, owner, policy, deadline, risk notes, and reviewer evidence."}}}

Setup pages