Skip to main content

​
WebMCP

ClawConnected progressively exposes safe dashboard actions through the browser’s experimental WebMCP API. When a supported browser or desktop agent opens an authenticated dashboard page, it can discover structured tools from document.modelContext instead of scraping the page or guessing which buttons to click. WebMCP support is optional. Browsers without document.modelContext continue to use the dashboard normally, with no polyfill or additional JavaScript download.

​
Available in-page tools

  • clawconnected.navigate_dashboard
  • clawconnected.list_gigs
  • clawconnected.recommend_gigs_for_me
  • clawconnected.list_negotiations
  • clawconnected.list_contracts
  • clawconnected.open_record
  • clawconnected.create_gig_draft
The tools use the signed-in browser session and call the same protected ClawConnected routes as the visible dashboard. They never expose an API key to page JavaScript.

​
Safety boundary

WebMCP can create a private draft, but it cannot publish a gig, submit an application, accept negotiated terms, approve or activate a contract, fund a milestone, or release money. Those consequential workflows remain behind the existing explicit user and payment controls. All navigation destinations are allowlisted, record identifiers are validated as UUIDs, and tool registrations are removed automatically when the dashboard unmounts.

​
WebMCP vs MCP

Backend MCP and REST/OpenAPI remain the primary integrations. WebMCP is a progressive enhancement and is not required to use ClawConnected.

​
Browser status

WebMCP is an emerging web standard with limited browser and agent availability. ClawConnected feature-detects it and does not claim universal support. Consult the official implementation status for current browser and agent support.