Chrome MCP Server Ngg

🚀 Chrome MCP Server

We are building a server for interacting with Chrome. This project has two main objectives:

1. Provide an MCP implementation that does not rely on the MCP library provided by Anthropic.
2. Create a Chrome MCP server so that we can use it in Cursor to capture screenshots of pages and verify its implementation.

⚠️ Important Note

This is not a reference implementation of the MCP protocol. It is a learning exercise to better understand the protocol and how it works.

A more robust implementation is located in the app folder.

🚀 Quick Start

✨ Features

This is a simple implementation of the MCP Protocol, so we have not implemented all the features of the MCP protocol. We focused on building the first set of functions to make the implementation work.

📦 Installation

You can run the demo implementation by executing the following command:

uv run uvicorn demo_implementation.main:app --reload

Then test it by running the MCP inspector:

npx @modelcontextprotocol/inspector node build/index.js

In the inspector, you can connect to our server using the URL http://0.0.0.0:8000.

💻 Usage Examples

Basic Usage

The demo implementation mainly has two main components:

1. An event stream for sending messages from the server to the client.
2. A POST endpoint for sending messages from the client to the server.

The initialization process is divided into three parts:

1. The client first calls the /sse endpoint to obtain the session URI.
2. The client sends an initialize message to the server, and the server responds with the supported features.
3. The client sends a notifications/initialized message to notify the server that the initialization is complete.

Once implemented, the client can start sending messages to the server to use the tool.

Advanced Usage

The demo implementation has some limitations, including lack of error handling and no proper session cleanup. We added a more robust implementation in app/main.py, which relies on the MCP Python SDK to handle connections and messages.

The robust implementation relies on the MCP Python SDK to handle connections and messages. This implementation is located in app/main.py.

Since we only need to define three functions to be used as tools, the implementation is much simpler. Once these functions are defined, we can test the implementation by running the following command:

# Start the server
mcp run app/main.py --transport sse

Then start the MCP inspector in another terminal:

npx @modelcontextprotocol/inspector node build/index.js