panerelaylisted

# Panerelay Use one Panerelay workflow for browser-authenticated HTTP requests, Agent routing, integration setup, and explicitly authorized existing-browser automation. Panerelay supplies browser attachment, Fetch, routing, and policy; agent-browser, Browser Use, and Playwright CLI retain their own DOM, navigation, and interaction semantics. ## Choose fetch or page automation first When `mcp__panerelay_fetch__browser_fetch` is available, use it for a known HTTP(S) URL whose request should reuse the user's browser Cookie state. It creates no tab authorization or control lease and never returns Cookies. An already authorized domain is reused without a popup; a new or browser-revoked domain requires the user's direct Extension approval. Fetch MCP is not a search engine and cannot inspect DOM or page state. Use the selected automation engine for navigation, rendered content, JavaScript challenges, interaction, downloads, screenshots, or anything whose source is the page rather than a known endpoint. Use the Agent's normal search capability for discovery, then Fetch MCP only for an exact URL that needs browser login state. Fetch supports mutating HTTP methods, so do not describe it as read-only. Use GET or HEAD unless the user requested a mutation. After an interrupted or failed mutation, inspect server state before retrying; do not assume the request was not applied. Redirects fail closed, and the caller cannot choose a Cookie name or `localStorage` key. Protected storage bi