Warp browser MCP setup

Connect E2LLM to Warp

Give Warp access to the browser session you already use. E2LLM connects as a remote MCP server, so Warp can read the rendered page, inspect controls, and act through explicit browser tools.

Remote MCPStreamable HTTPOAuthWarp Agent

Ready-made setup instruction

Paste this into Warp Agent. It describes the remote server and ends with a browser-tool verification.

Configure E2LLM as a remote MCP server in Warp.

1. Open Warp's MCP Servers settings.
2. Add a server named "e2llm" using the Streamable HTTP or SSE server type.
3. Set the URL to https://mcp.e2llm.com/mcp and leave custom headers empty.
4. Start the server and ask me to complete Warp's browser-based OAuth flow.
5. Wait for the E2LLM tools to appear, then ask me to run the verification prompt from this page.

Warp manages remote MCP servers from Settings, MCP Servers or Warp Drive, MCP Servers.

Connect

Connect your browser

Use the E2LLM setup wizard to install the browser extension and sign in.

Add the remote endpoint

Open Warp's MCP Servers page, select Streamable HTTP or SSE Server, and enter:

https://mcp.e2llm.com/mcp

Start and authorize

Start e2llm. Warp opens its browser-based OAuth flow and stores credentials on the device.

Official client mechanics: Warp supports Streamable HTTP and SSE server URLs, browser-based OAuth, local credential storage, and per-server logs. Read Warp's MCP documentation →

Verify the connection

Confirm that Warp lists the E2LLM tools. Open a normal webpage in the connected browser and run this read-only check:

Use E2LLM to list my open browser tabs. Then capture the active tab and tell me its page title and primary heading. Keep the page unchanged.

Pass condition: Warp returns the tabs, captures the active page, and reports details from that page through real tool calls.

Worked use case

Correlate a deployment check with the rendered service

Warp can run the deployment and inspect logs in the terminal. E2LLM adds the user-facing state from the authenticated application.

Validate the service I just deployed from this terminal.

1. Review the deployment command output and the latest relevant logs.
2. Use E2LLM list_tabs to find the service's browser tab.
3. Capture the page and inspect its visible status, navigation, and primary controls.
4. Correlate any rendered error with the terminal evidence.
5. Report whether the deployment and the user-facing service agree, with exact evidence from each.

Keep the browser read-only during validation.

This workflow joins terminal evidence and rendered application evidence in one Warp Agent thread.

Troubleshoot the connection

The server is stopped: open Warp's MCP Servers page and start e2llm.
OAuth needs another attempt: use the server's authentication controls, then restart the browser flow.
The endpoint errors: open View Logs and confirm the exact E2LLM URL.
No tabs appear: connect the browser extension with the same account.
Cloud Agent use differs: this page covers Warp's local desktop agent and MCP Servers settings.

Capabilities

E2LLM exposes the tools advertised by the running production deployment: structured page capture, targeted reads, tab discovery, exploration, and explicit browser actions. The generated MCP tool reference is built from that named production deployment and stays aligned with what it advertises.