SpidexLab's Multi-Tenant Browser MCP
Enables multiple autonomous agents to concurrently control separate tabs in a single Chrome instance, with features like semantic search and network monitoring.
README
SpidexLab's Multi-Tenant Browser MCP 🚀
🌟 SpidexLab's Custom Fork for Autonomous Agents - This is a modified version of the Chrome MCP Server, specifically re-architected to support Multi-Tenant Tab Multiplexing and Concurrent Agents.
This is a specialized fork. For the original upstream project, please visit hangwin/mcp-chrome.
📖 Documentation: English
🎯 What makes this fork different?
The original Chrome MCP Server is an incredibly powerful tool that exposes Chrome browser functionality to AI assistants. However, it was built with a 1-to-1 connection limit in mind (one agent controlling one browser session).
The SpidexLab Modification (V3: The Multiplier): We have modified the native server bridging logic and extension messaging architecture to support a multi-tenant execution queue. This allows multiple autonomous AI agents to connect to the same browser instance concurrently. Each agent operates in its own isolated browser tab context, allowing 2, 5, or 10 agents to parallelize web research and automation tasks without connection resets or state collisions.
✨ Core Features
- 👯 Multi-Tenant Tab Multiplexing: Concurrent agents can operate simultaneously in isolated tab contexts.
- 😁 Chatbot/Model Agnostic: Let any LLM or chatbot client or agent you prefer automate your browser
- ⭐️ Use Your Original Browser: Seamlessly integrate with your existing browser environment (your configurations, login states, etc.)
- 💻 Fully Local: Pure local MCP server ensuring user privacy
- 🚄 Streamable HTTP: Streamable HTTP connection method
- 🏎 Cross-Tab: Cross-tab context
- 🧠 Semantic Search: Built-in vector database for intelligent browser tab content discovery
- 🔍 Smart Content Analysis: AI-powered text extraction and similarity matching
- 🌐 20+ Tools: Support for screenshots, network monitoring, interactive operations, bookmark management, browsing history, and 20+ other tools
🚀 Quick Start
Prerequisites
- Node.js >= 20.0.0 and pnpm/npm
- Chrome/Chromium browser
Installation Steps
-
Download the latest Chrome extension from GitHub Download the
chrome-mcp-server-latest.zipfrom thereleases/folder in this repository. -
Install mcp-chrome-bridge globally
npm install -g mcp-chrome-bridge
- Load Chrome Extension
- Open Chrome and go to
chrome://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select the unzipped extension folder
- Click the extension icon to open the plugin, then click connect to see the MCP configuration.
- Open Chrome and go to
Usage with MCP Protocol Clients
Using Streamable HTTP Connection (👍🏻 Recommended)
Add the following configuration to your MCP client configuration:
{
"mcpServers": {
"chrome-mcp-server": {
"type": "streamableHttp",
"url": "http://127.0.0.1:12306/mcp"
}
}
}
🛠️ Available Tools
Complete tool list: Complete Tool List
<details> <summary><strong>📊 Browser Management (6 tools)</strong></summary>
get_windows_and_tabs- List all browser windows and tabschrome_navigate- Navigate to URLs and control viewportchrome_switch_tab- Switch the current active tabchrome_close_tabs- Close specific tabs or windowschrome_go_back_or_forward- Browser navigation controlchrome_inject_script- Inject content scripts into web pageschrome_send_command_to_inject_script- Send commands to injected content scripts </details>
<details> <summary><strong>📸 Screenshots & Visual (1 tool)</strong></summary>
chrome_screenshot- Advanced screenshot capture with element targeting, full-page support, and custom dimensions </details>
<details> <summary><strong>🌐 Network Monitoring (4 tools)</strong></summary>
chrome_network_capture_start/stop- webRequest API network capturechrome_network_debugger_start/stop- Debugger API with response bodieschrome_network_request- Send custom HTTP requests </details>
<details> <summary><strong>🔍 Content Analysis (4 tools)</strong></summary>
search_tabs_content- AI-powered semantic search across browser tabschrome_get_web_content- Extract HTML/text content from pageschrome_get_interactive_elements- Find clickable elementschrome_console- Capture and retrieve console output from browser tabs </details>
<details> <summary><strong>🎯 Interaction (3 tools)</strong></summary>
chrome_click_element- Click elements using CSS selectorschrome_fill_or_select- Fill forms and select optionschrome_keyboard- Simulate keyboard input and shortcuts </details>
<details> <summary><strong>📚 Data Management (5 tools)</strong></summary>
chrome_history- Search browser history with time filterschrome_bookmark_search- Find bookmarks by keywordschrome_bookmark_add- Add new bookmarks with folder supportchrome_bookmark_delete- Delete bookmarks </details>
📄 License
This project is licensed under the MIT License - see the LICENSE file for details. Based on the original hangwin/mcp-chrome repository.
📚 More Documentation
- Architecture Design - Detailed technical architecture documentation
- TOOLS API - Complete tool API documentation
- Troubleshooting - Common issue solutions
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.