Give Claude Code Browser Access to Your Open Tabs

Claude Code can work with the browser you already use through an MCP browser connection. With E2LLM, the practical path is:

  1. Install the E2LLM extension in Chrome, Edge or Firefox.
  2. Sign in to the extension.
  3. Add E2LLM as an MCP connection in Claude Code.
  4. Ask Claude Code to list your open tabs.
  5. Choose a tab and let Claude read, inspect or act on it.

What browser access means

Browser access is not the same as web search. Web search gives Claude public pages returned by a search engine. Browser access lets Claude work with a live tab in your browser, including a page you already opened and a session where you are already signed in.

That distinction matters when the task lives inside:

E2LLM provides the perception and action layer. Claude Code remains the model that plans the work.

Set up Claude Code browser access

1. Install the browser extension

Open the E2LLM setup page and choose your browser. The extension is the part that can see and act in the browser on your machine.

2. Sign in to E2LLM

Open the extension popup and complete sign-in. Keep the popup available while checking the first connection.

3. Add the MCP connection to Claude Code

Follow the current E2LLM setup guide for the supported MCP configuration. Use the documented endpoint and authentication flow rather than copying an old configuration from a forum post.

4. Verify the connection with list_tabs

The first useful test is simple:

List my open browser tabs.

If Claude returns the tabs you currently have open, the browser connection is working. A successful MCP login alone is not enough. The extension must also be signed in and connected.

5. Start with a read-only task

Before asking Claude to click or fill anything, try:

Read the active tab and summarize what this page is asking me to do.

This confirms that Claude can reach the intended tab and interpret its current state.

Can Claude Code use pages behind a login?

Yes, when the page is already open in the paired browser and your browser session has access to it. You do not need to export cookies or paste page content into the terminal.

The site still controls the session. If the login expires, the page asks for authentication again, or the browser is closed, Claude cannot bypass that state.

Why list_tabs is the right first check

A browser setup has several separate steps: the AI client connects to MCP, the extension signs in, and the extension connects to the browser relay. A partial setup can look successful while Claude still cannot use a tab.

list_tabs tests the working path. It proves that Claude can ask for a browser operation and receive the current tab list. For a stronger end-to-end check, follow it with a read-only page capture.

Common setup problems

Claude is connected, but no tabs appear

Open the extension popup and check its state. Confirm that the extension uses the same E2LLM account as the MCP connection and that it shows as connected.

The extension stays on "Logging in..."

Close and reopen the extension popup. If the control still hangs after a retry, restart the extension from the browser's extension manager, then sign in again. Pinning the extension only makes it easier to reopen; it does not repair authentication.

Claude can list tabs but cannot use one

The tab may have closed, navigated, expired its session or opened a browser-internal page where extensions cannot run. Switch to a normal web page and try a read-only capture.

What to ask Claude Code first

Try one of these:

Start with observation. Add clicks and form actions only after the correct page and state are established.

What about Claude.ai?

Claude.ai and Claude Code are different hosts, but the browser-access question has the same working test: can Claude list and read a tab from the browser you connected? E2LLM provides the browser extension and remote MCP connection. The host must support adding that connection and making its tools available to the conversation.

For Claude Code, follow the setup above. For Claude.ai, use its connector flow when that capability is available for your account and environment. Connect E2LLM, open the browser extension with the same account, then ask Claude to list your open tabs. A returned tab list establishes that Claude can reach the browser path. Follow with a read-only capture of the intended tab before enabling actions.

This workflow avoids pasting page contents into chat. The extension connects the live browser session, while MCP connects that browser capability to the Claude host. Claude can read open tabs only when the extension, account connection and MCP path are all active.

If Claude can see the MCP connection but cannot read tabs, check the browser extension state and account pairing. If the tab list works but one page does not, confirm that it is a normal web page where extensions may run and that the session is still active.

Browser-access questions

Connect E2LLM to your AI

For longer sessions, learn how to keep browser context within budget.