Zed browser MCP setup

Connect E2LLM to Zed

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

Remote MCPStreamable HTTPOAuthZed Agent

Ready-made setup instruction

Paste this into Zed Agent. It adds a remote context server while preserving the rest of your settings.

Configure E2LLM as a remote MCP server in Zed.

1. Open Zed's settings JSON and preserve every existing setting.
2. Under "context_servers", add:
   "e2llm": {
     "url": "https://mcp.e2llm.com/mcp"
   }
3. Keep the settings valid JSON and retain unrelated entries.
4. Ask me to open Settings > AI > MCP Servers, start e2llm, and complete OAuth.
5. Wait for the E2LLM tools to appear, then ask me to run the verification prompt from this page.

Zed also provides an Add Remote Server action in Settings, AI, MCP Servers.

Connect

Connect your browser

Open the E2LLM setup wizard, install the browser extension, and sign in.

Add a remote server

Open Settings, AI, MCP Servers and choose Add Remote Server. Enter the endpoint, or add this settings entry:

{
  "context_servers": {
    "e2llm": {
      "url": "https://mcp.e2llm.com/mcp"
    }
  }
}

Authorize E2LLM

Start the server. With no Authorization header configured, Zed opens the standard MCP OAuth flow.

Official client mechanics: Zed supports remote context servers by URL, its Add Remote Server UI, standard MCP OAuth, and tool-list updates. Read Zed's MCP documentation →

Verify the connection

Confirm that Zed 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: Zed returns the tabs, captures the active page, and reports details from that page through real tool calls.

Worked use case

Trace a keyboard-focus bug from rendered control to source

Zed keeps the implementation and edits close while E2LLM supplies roles, labels, relationships, and the current browser state.

Trace the keyboard-focus issue in my active application tab.

1. Inspect this project for the dialog or menu component involved.
2. Use E2LLM to capture the active tab and inspect the relevant interactive controls.
3. Compare rendered labels, roles, and relationships with the component implementation.
4. Apply the smallest focus-management fix.
5. Ask me to reload, then recapture and verify the rendered control structure.

Use read-only browser tools throughout this diagnosis.

The result connects Zed's project editing loop with field-level evidence from the current page.

Troubleshoot the connection

The server is absent: confirm e2llm is nested under context_servers.
The status shows an error: open Settings, AI, MCP Servers and read the indicator tooltip.
OAuth needs another attempt: remove any manual Authorization header, restart e2llm, and follow the OAuth prompt.
No tabs appear: connect the browser extension with the same account.
Tools require repeated approval: review Zed's Agent tool permissions for mcp:e2llm: keys.

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.