CodingBaby Browser MCP server
CodingBaby-Browser-MCP
This is a Model Context Protocol (MCP) tool server designed to communicate with a Chrome browser extension via WebSocket for browser automation control.
Description
This server starts a WebSocket server and waits for a connection from the companion Chrome extension. Once connected, an MCP client can send commands through this server to the Chrome extension to control browser behavior, such as navigation, clicking, typing, scrolling, taking screenshots, etc.
Companion Chrome Extensio
This server requires a companion Chrome extension to perform the actual browser operations. Please ensure the extension is installed and enabled in your Chrome browser.
Available Tools (Registered in chrome-server.js)
navigate: Navigates to a specified URL.click: Performs a click operation at the specified coordinates (x,y) on the web page.type: Types text into the currently focused element.press_key: Simulates pressing a specific key on the keyboard (e.g., 'Enter', 'ArrowLeft').snapshot: Captures a screenshot of the current page (returns Base64 encoded image data).close: Closes the browser (or the tab controlled by the extension).scroll: Scrolls the page in a specified direction (up, down, left, right), optionally with a selector for the element to scroll.save_html: Saves the full HTML content of the current page to a temporary file on the server.set_viewport: Sets the size (width and height) of the browser viewport.area_screenshot: Take a screenshot of a specific area of the current page.get_saved_screenshots: Get a list of all saved screenshots.wait: Wait for a specified number of seconds and automatically returns a screenshot of the current page state after waiting.
Installation
If using the source code directly, navigate to the mcp/CodingBaby-Browser-MCP directory and run:
npm install
If using the published npm package:
npm install @sydneyassistent/codingbaby-browser-mcp
or globally:
npm install -g @sydneyassistent/codingbaby-browser-mcp
Running (from source)
node chrome-server.js
Or, using the script in package.json:
npm start
The server will start the WebSocket service on the default port 9876 and communicate with the MCP client via standard input/output (stdio).
Running (as installed package with npx)
If installed locally or globally, you can often run it using npx:
npx @sydneyassistent/codingbaby-browser-mcp
(This requires the package to be configured correctly, potentially using a bin entry in package.json pointing to chrome-server.js for direct execution, which might need adjustment.)
Notes
- On the first call to any browser operation tool, the server will automatically attempt to start the WebSocket server and wait for the Chrome extension to connect.
- Screenshots and HTML content are returned as part of the response or saved locally on the server.
Server Config
{
"mcpServers": {
"codingbaby-browser-mcp": {
"command": "npx",
"args": [
"-y",
"@sydneyassistent/codingbaby-browser-mcp"
]
}
}
}