SpidexLab's Multi-Tenant Browser MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SpidexLab's Multi-Tenant Browser MCPOpen a new tab and search for 'MCP server tutorials'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: OpenChrome
✨ 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-bridgeLoad 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.
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
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
chrome_screenshot- Advanced screenshot capture with element targeting, full-page support, and custom dimensions
chrome_network_capture_start/stop- webRequest API network capturechrome_network_debugger_start/stop- Debugger API with response bodieschrome_network_request- Send custom HTTP requests
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
chrome_click_element- Click elements using CSS selectorschrome_fill_or_select- Fill forms and select optionschrome_keyboard- Simulate keyboard input and shortcuts
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
📄 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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SpideXD/mcp-chrome'
If you have feedback or need assistance with the MCP directory API, please join our Discord server