User SWeb Agent MCP

Browser MCP: Autonomous Web Agent Kernel

[](https://github.com/vsrupeshkumar/User-sWeb-Agent---MCP) [](https://opensource.org/licenses/MIT)

Browser MCP is a high-performance Model Context Protocol (MCP) server designed to bridge the gap between Large Language Models (LLMs) and real-time browser environments. It facilitates secure, stealthy, and stateful browser automation by leveraging existing user profiles.

---

🏗 System Architecture

The following diagram illustrates the topological data flow between the LLM client, the MCP Kernel, and the Browser Runtime.

graph TD
    subgraph "AI Client (Claude/Cursor/VSCode)"
        Client[MCP Client]
    end

    subgraph "MCP Server Kernel"
        Server[MCP Server]
        Context[Context Manager]
        WS_Server[WebSocket Server]
    end

    subgraph "Browser Environment"
        Ext[Browser Extension]
        DOM[DOM Tree/Execution Context]
    end

    Client -- "JSON-RPC (stdio)" --> Server
    Server -- "Tool Call" --> Context
    Context -- "Binary/JSON" --> WS_Server
    WS_Server -- "Secure WebSocket" --> Ext
    Ext -- "CDP / Web API" --> DOM
    DOM -- "Mutation Events" --> Ext
    Ext -- "Response" --> WS_Server
    WS_Server -- "Result" --> Server
    Server -- "Final Output" --> Client

---

🔢 Formal Logic & Mathematical Foundation

1. State Transition Model

We define the browser automation process as a sequence of state transitions within a finite state machine (FSM).

Let $\mathcal{S}$ be the set of all possible browser states (DOM structure, cookies, local storage, etc.). Let $\mathcal{T}$ be the set of tools defined in the MCP schema. Let $\mathcal{A}$ be the domain of input arguments for these tools.

A tool execution is defined by the transition function $\delta$: $$\delta: \mathcal{S} \times \mathcal{T} \times \mathcal{A} \rightarrow \mathcal{S} \times \mathcal{R}$$

Where:

• $s_t \in \mathcal{S}$ is the current state.
• $t \in \mathcal{T}$ is the selected tool.
• $a \in \mathcal{A}$ is the argument vector.
• $r \in \mathcal{R}$ is the observation (text, image, or structured data) returned to the LLM.

2. Contextual Persistence

The MCP Server maintains a singleton context $\mathcal{C}$ that encapsulates the active WebSocket connection $\omega$: $$\mathcal{C} = \{ \omega \mid \omega \in \text{WebSocket}, \text{status}(\omega) = \text{'connected'} \}$$

The execution of any tool $t$ is conditional on the existence of a valid $\omega$: $$P(\text{Success} \mid t, a) = \begin{cases} 1 & \text{if } \omega \in \mathcal{C} \\ 0 & \text{if } \omega \notin \mathcal{C} \end{cases}$$

---

🚀 Core Features

• ⚡ Zero Latency Core: Optimized for local execution, minimizing network overhead between the LLM and the target DOM.
• 🛡 Stealth Protocol: Unlike traditional headless drivers, Browser MCP utilizes the user's authentic browser fingerprint, bypassing advanced anti-bot mechanisms and CAPTCHAs.
• 🔒 Privacy First Architecture: All automation logic and data handling occur locally. No sensitive browser data is ever transmitted to external third-party servers.
• 🔄 State Synchronization: Real-time synchronization between the browser extension and the MCP server via low-latency WebSockets.

---

🛠 Installation & Setup

Prerequisites

• Node.js (v18+)
• Model Context Protocol SDK

Build from Source

# Clone the repository
git clone https://github.com/vsrupeshkumar/User-sWeb-Agent---MCP.git

# Install dependencies
npm install

# Compile the kernel
npm run build

Configuration

Add the server to your MCP client configuration (e.g., claude_desktop_config.json):

{
  "mcpServers": {
    "browser-mcp": {
      "command": "node",
      "args": ["/path/to/dist/index.js"]
    }
  }
}

---

📜 License

This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.

---

Built with ❤️ by vsrupeshkumar

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: vsrupeshkumar
• Source: vsrupeshkumar/User-sWeb-Agent---MCP
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.