What components make up the InBrowserMCP Project?
The project has three main parts: a React frontend (port 5173), a Node.js MCP server (port 3000), and a Chrome browser extension (WebSocket port 8081).
@LofiSu
Basic information
express框架搭建的mcp-sdk实例
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
The InBrowserMCP Project implements a system based on the Model Context Protocol (MCP) that allows an AI model to interact with a web browser via a browser extension. It consists of a React frontend, a Node.js MCP server, and a Chrome browser extension that communicate to execute browser actions.
Start the MCP server (cd mcp-server && pnpm dev), load the Browser Extension in Chrome (chrome://extensions/), start the Frontend (cd frontend && pnpm dev), then open the frontend application at http://localhost:5173 to send commands that control the browser.
The project has three main parts: a React frontend (port 5173), a Node.js MCP server (port 3000), and a Chrome browser extension (WebSocket port 8081).
The frontend sends user commands to the MCP server, which translates them into MCP tool calls. The server sends browser actions to the extension via WebSocket, and the extension executes them and returns results. The server then streams responses back to the frontend via SSE.
No, an AI model is not explicitly implemented in this project; it is assumed that the frontend or MCP server will interact with an external AI model as part of the system.
You need Node.js and pnpm for the server and frontend, and Google Chrome to load the browser extension. All communication uses localhost ports 5173, 3000, and 8081.
Follow the general workflow: start the MCP server, load the extension in Chrome, start the frontend, and open the frontend URL. Detailed instructions are in the respective README files for each component.
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP
CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.
Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
Comments