Walkaway Connector documentation

Existing MCP over streamable HTTP. Endpoint: POST /mcp on muse.secure.build. Protocol 2025-03-26. Authentication: Bearer token (WALKAWAY_CONNECTOR_TOKEN on the host).

Tools

• walkaway_start_task (write, open-world): start a task from the user's verbatim goal.
• walkaway_status (read-only): status, page title/URL, proposed step, approval state.
• walkaway_propose_step (write, open-world): propose one step. Never executes.
• walkaway_request_approval (write): put a proposal on the user's glasses. Cannot approve.
• walkaway_reject_step (write): discard the proposal permanently.
• walkaway_stop_task (destructive): stop and close the browser.

Data rules

• Connector results are text only. Screenshots never transit the connector.
• Executing a step requires approval recorded on the glasses Web App.
• No task history is stored on disk.

Errors

Tool failures return MCP isError text results. HTTP 401 means a missing or wrong bearer token. HTTP 413 means the request body exceeded 64 KiB.