Automation

The Automation App connects the Model Context Protocol (MCP) to the Automation API, enabling AI agents to perceive and interact with a live Webfuse Session — reading the page via optimised DOM snapshots and executing precise actions — including clicking, typing, and scrolling — across iframes and Shadow DOM.

MCP Server URL

https://session-mcp.HOSTNAME/mcp

Authentication

Authentication uses the Space Automation API Key, which can be generated under Space Settings → API Keys. Pass it as a Bearer token in the HTTP Authorization header:

Authorization: Bearer <your-space-automation-api-key>

Allowed URLs

By default the Automation app is loaded on every page. To restrict which pages it loads on, set Space Settings → Apps → Automation → Allowed URLs (option automation_app_allowlist) to one or more Chrome match patterns:

Value	Effect
`["<all_urls>"]`	App is loaded on every page (default)
`["https://example.com/*"]`	App is loaded only on `example.com`
`["https://.example.com/", "https://docs.example.com/help/*"]`	Multiple patterns. Any match loads the app
`[]`	App is never loaded. Disables automation on every page

Tool calls on a page where the app isn’t loaded return immediately with an error listing the configured patterns, so the agent can self-correct instead of retrying into a timeout. Only the allowlist is included in the error so the agent knows which patterns to navigate into. The navigate tool is not gated: it always dispatches the navigation, but returns a heads-up when the destination is outside the allowlist.

For example, with automation_app_allowlist set to ["https://example.com/*"]:

Calling act_click while on a non-matching page returns:

Tool calls aren’t available on this page. It’s not in the allowed URLs (["https://example.com/*"]). Use navigate to go to a URL in the list.
Calling navigate to a non-matching URL returns:

Navigated, but this URL isn’t in the allowed URLs (["https://example.com/*"]). Only navigate works here. Use it again to go to a URL in the list.