ProductDocsSetupSecurityGitHubnpm
01 // SETUP INITIATION
● LOCAL CONNECTION

Connect your AI agent to Chrome.

MiraiLens bridges MCP-compatible AI clients and a live Chrome session through a local browser connector.

Start setupView architecture
AI CLIENTClaude / Cursor / IDE
MIRAILENSMCP Server
CONNECTORChrome Extension
CHROMETarget Tab
02 // QUICK SUMMARY
01 // INSTALLATION

Install daemon

Run the local loopback WebSocket server in your command shell environment.

02 // CHROME EXTENSION

Connect extension

Install the Chrome Web Store client connector to interface with active browser sessions.

Chrome Web Store→
03 // AI CLIENT

Register MCP settings

Insert configuration parameters inside Claude, Cursor, Windsurf, or Cline JSON files.

Select config client→
03 // DAEMON INSTALLATION
TERMINAL SHELL
$ npx mirailens@latest
# Loading WebSocket server on localhost loopback...
# Binds active port 8080. Ready for chrome extension connector...

SYSTEM REQUIREMENTS

Node.js
Version 18+
npm
Package run
Browser
Chrome browser
AI Model
MCP Client
04 // CHROME BINDING

Connect Chrome

The MiraiLens Connector is the browser-side component that connects the local MCP server to an active Chrome session.

Install Chrome ExtensionView source
PORT LOGIC
MCP ServerActive
↓ WebSocket (127.0.0.1:8080)
ConnectorConnecting
↓ Extension Gate
Chrome TabTarget URL
Local by design: The connector communicates with the local MiraiLens MCP server through loopback networking. Browser-control communication does not require a remote MiraiLens backend.
Address: 127.0.0.1Port: 8080Protocol: ws://
05 // CLIENT CONFIGURATION

Configure your AI client

Select your preferred AI client or IDE below to view its exact configuration block, file path, and setup steps.

Claude Desktop CONFIGURATIONVERIFIED INTEGRATION

Config File Locations

macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Configuration Block (claude_desktop_config.json)
claude_desktop_config.jsonJSON
{
  "mcpServers": {
    "mirailens": {
      "command": "npx",
      "args": ["-y", "mirailens@latest"]
    }
  }
}

Setup Instructions

01

Open the Claude Desktop configuration settings file.

02

Add the MiraiLens configuration object inside your 'mcpServers' object.

03

Save the configuration file and restart Claude Desktop.

04

Launch a conversation and verify the MiraiLens browser tools are available.

06 // OBSERVABILITY PANEL

Verify your connection

Confirm system loopback statuses are green and active in the instrumentation panel.

MIRAILENS CONNECTION STATEMONITOR OK
MCP SERVERCONNECTED
CHROME CONNECTORCONNECTED
BROWSER SESSIONACTIVE
TOOLSAVAILABLE
07 // FIRST DIAGNOSTIC RUN
Test Command prompt
"Inspect the current browser tab and tell me its title and URL."
✓ MIRAILENS IS CONNECTED
MCP server statusConnected (127.0.0.1:8080)
Chrome Connector extensionConnected (WebSocket Bound)
Target tab contextActive (URL Evaluated)
System state transitions verified. Ready for browser automation workflows.
08 // AGENT CAPABILITIES

Now give your agent a browser.

NAVIGATE

Open and move between pages.

PROMPT EXAMPLE:"Open https://github.com and check notifications."
INSPECT

Understand the current browser state.

PROMPT EXAMPLE:"Analyze the layout elements on the page."
INTERACT

Click and interact with page elements.

PROMPT EXAMPLE:"Click on the settings dropdown and click logout."
INPUT

Enter information into form fields.

PROMPT EXAMPLE:"Type my username in the login input box."
EXTRACT

Retrieve relevant page information.

PROMPT EXAMPLE:"Read the table contents and list row values."
AUTOMATE

Execute multi-step browser workflows.

PROMPT EXAMPLE:"Navigate to docs, search for setup, and copy step 2."
09 // SYSTEM DEBUGGING

Troubleshooting

10 // ARCHITECTURAL SCHEMATIC

Under the hood

AI CLIENT AGENT
Issues automation requests
MCP transport
MIRAILENS MCP SERVER
Runs on local machine port 8080
Local WebSocket (127.0.0.1)
MIRAILENS CONNECTOR
Chrome Web Store Extension
GOOGLE CHROME
Live local browser tab
11 // SECURITY COMPLIANCE

Human stays in control

In browser automation, the AI client runs remote scripts. MiraiLens Connector protects against AI attempts to spoof authority.

STATE TRANSITIONS MONITORLOOP ACTIVE
IDLE
Awaiting next instruction
AGENT_RUNNING
AI is dispatching action
HUMAN_TAKEOVER
Human interaction detected
HUMAN_CONTROLLED
Human retains authority
AGENT_RESUMING
AI requests restart validation
COMPLETED
Task execution finished

Security by architecture

Control states reside in Chrome memory space. An active AI session is immediately aborted and transitioned to HUMAN_TAKEOVER when user interaction is detected. The AI cannot override this state.

Read security details →

Chrome Extension Permissions

The extension requires specific manifest profiles to interact with tabs and dispatch scripting requests.

12 // ADVANCED REGISTRY

Advanced configuration

Custom environments can change daemon paths or listening loops.

Keep MiraiLens up to date

Update the global or local registry packages to load security fixes and layout API updates.

$npm update -g mirailens

Uninstall Guide

To completely remove MiraiLens, delete the Chrome extension from your browser, clean the config block JSON files, and run npm uninstall -g mirailens.

Ready to build with MiraiLens?

Install the MCP server, connect your browser, and give your AI agent access to real web workflows.

Get StartedView DocumentationGitHubNPM