AI agents can write code, search the web, and call APIs — but giving them real browser access without mixing your accounts has been unsolved until now. EazySessions MCP connects Claude, ChatGPT, and Cursor to isolated browser sessions running on your own machine, so the AI can open URLs, fill forms, and take screenshots without ever touching the wrong account context.

This post explains exactly how it works, what tools are available, and how to set it up in four steps.

Why Browser Isolation Matters for AI Agents

When you ask an AI agent to "log into my client's dashboard and check the campaign stats," the first question is: which browser session? If your AI has access to a generic browser, it's operating in your default Chrome profile — the one with your email, your Stripe account, your personal Facebook tab open in the background.

EazySessions MCP sidesteps this entirely by giving the AI a dedicated, isolated session for each task. The session has its own separate cookies, storage, and login state. It cannot bleed into your other sessions. You can give the AI access to "Client A's Google Ads session" and the AI stays confined to exactly that context.

The other advantage: the MCP server runs completely locally. There's no remote browser service, no third-party cloud receiving your credentials. The AI client (Claude, ChatGPT, Cursor) talks to a local MCP server on your machine, which in turn talks to the EazySessions desktop Agent via a local WebSocket. Nothing leaves your machine except the URLs the AI opens.

What the MCP Server Can Do

Once connected, the AI client gains 14 tools for session management and browser control. The tools fall into two groups.

Session management tools

Browser automation tools

The standard automation loop — screenshot → click field → type_text → press_key Enter → screenshot to verify — gives the AI a complete form-filling and navigation capability within the isolated context.

The Architecture: How It All Connects

There are three components working together:

AI client (Claude / ChatGPT / Cursor)
    ↕ stdio MCP protocol
EazySessions MCP server (local process)
    ↕ WebSocket ws://127.0.0.1:5088
EazySessions desktop Agent (Electron app)
    ↕ Chrome extension API
EazySessions Chrome extension (your sessions)

The MCP server is a lightweight Node.js process that the AI client launches as a subprocess. It speaks the standard MCP protocol over stdio, so it works with any MCP-compatible client.

The desktop Agent is an Electron app that bridges the MCP server to your Chrome extension. It runs a local WebSocket server on port 5088. Authentication uses a dedicated API key (prefixed eazy_) that you generate in the extension — the key is stored locally and never transmitted to EazySessions servers.

The Chrome extension manages the actual isolated sessions. The Agent communicates with it via the Chrome extension API to create, start, stop, and interact with sessions.

This means your AI controls sessions, but you control the Agent. Revoke the API key from the extension at any time to immediately cut off all AI access.

Setup: Four Steps

Step 1: Install the extension and Agent

Install the EazySessions Chrome extension. Then open the extension and install the desktop Agent from within it. Keep the Agent running — it's the bridge between your AI client and your sessions.

Step 2: Add the MCP configuration

Add this block to your AI client's config file. For Claude (.mcp.json in your project root):

{
  "mcpServers": {
    "eazysessions": {
      "command": "/bin/sh",
      "args": ["/Applications/EazySessions Agent.app/Contents/Resources/EazySessions MCP.sh"]
    }
  }
}

For Cursor (~/.cursor/mcp.json), the same JSON block applies. For ChatGPT/Codex (~/.codex/config.toml):

[mcp_servers.eazysessions]
command = '/bin/sh'
args = ['/Applications/EazySessions Agent.app/Contents/Resources/EazySessions MCP.sh']
startup_timeout_sec = 30

Windows paths use cmd.exe with the %LOCALAPPDATA%\Programs\EazySessionsAgent\EazySessions MCP.cmd launcher. The full setup guide at eazysessions.com/mcp has the exact snippets for each client and platform with a copy button.

Step 3: Restart and generate an API key

Fully restart your AI client so it discovers the EazySessions MCP server. Then open the EazySessions extension, go to API keys, generate a new key, and copy it immediately — the full key is only shown once.

Step 4: Connect the key

In your AI client, send this message once:

Use the EazySessions MCP configure_api_key tool with this API key: YOUR_API_KEY

After that succeeds, all other EazySessions MCP tools are ready to use.

What You Can Actually Do With It

Here are some real prompts that work once the setup is complete:

Account isolation for client work

"Create a session for my client's LinkedIn Company Page, open linkedin.com/company/[slug]/admin, and tell me what the current follower count is."

The AI creates an isolated session, opens the URL, takes a screenshot, and reads the page — without touching your personal LinkedIn.

Morning workflow setup

"Start my saved 'Morning Dashboard' session and open my analytics, email, and ad account tabs in sequence."

The AI uses start_saved_session then open_url to open each URL as a new page in the same session.

Form navigation

"In my AdWords session, click into the campaign budget field and change it to 500."

The AI runs screenshot → identifies the field coordinates → click → type_text "500" → press_key Enter → screenshot to verify.

Proxy-based session launch

"Start a fresh session through a US residential proxy and open the regional pricing page."

The start_session tool accepts a proxy configuration — host, port, username, password, and protocol (HTTP or SOCKS5) — so the session opens from the specified IP.

Current Limitations

Be clear-eyed about what this can and can't do:

Bottom Line

EazySessions MCP is the cleanest way to give an AI agent real browser access without compromising session isolation. The sessions it controls stay completely separate from your other accounts — the AI can't accidentally post from the wrong identity, access the wrong account, or leave traces in your personal browser context. Setup takes under ten minutes, and the automation loop (screenshot → click → type) covers most real-world browser tasks.

If you're already using EazySessions for multi-account work, the MCP connection adds AI control to sessions you already have organised. If you're new to EazySessions, the one-month free trial gives you time to set up your sessions and test the MCP integration before committing.

If you manage multiple social or brand accounts, see also: Best Browser Setup for Social Media Managers.