Vibe MCP
OfficialRelated Servers
Alternatives to Vibe MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.251Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local, open-source Chrome browser-automation MCP server for AI agents that controls real signed-in Chrome profiles with multi-profile routing and parallel tabs.138 npm12MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.1 npmISC
- AlicenseNot gradedqualityNot gradedmaintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC
- AlicenseNot gradedqualityCmaintenanceThis MCP server lets an AI agent drive the user's actual logged-in browser through a Chrome extension, running async scripts to interact with tabs, inspect network, console, and cookies, and save reusable automation flows.2 npm1Apache 2.0
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly stated.
The single tool name 'set_remote' follows a clear verb_noun convention, which is consistent and predictable. With only one tool, naming consistency is perfect.
A single tool feels insufficient for a server named 'Vibe MCP', especially since the description references browser tools that are missing. The tool is purely a configuration step, leaving the server with very limited functionality.
The tool set lacks any browser automation tools, which are the implied core functionality of the server. The description suggests that set_remote is a prerequisite for browser tools, but those tools are not present, creating a noticeable gap. The server cannot perform any useful task beyond configuration.