MCP.so
登录

Chrome MCP Server

@jverre

基本信息

分类

其他

许可证

MIT

传输方式

stdio

作者

jverre

关于 Chrome MCP Server

MCP server to interact with Chrome

Chrome MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "chrome-mcp-server": {
      "command": "uv",
      "args": [
        "run",
        "uvicorn",
        "demo_implementation.main:app",
        "--reload"
      ]
    }
  }
}

Chrome MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Chrome MCP Server?

Chrome MCP Server is an implementation of the Model Context Protocol (MCP) designed to interact with Chrome. It was built as a learning exercise to understand the MCP protocol and to provide a server that can be used in Cursor to take screenshots of a page and validate implementation.

How to use Chrome MCP Server?

For the demo implementation, run uv run uvicorn demo_implementation.main:app --reload and connect via the MCP inspector at http://0.0.0.0:8000. For the robust implementation (which uses the MCP Python SDK), start the server with mcp run app/main.py --transport sse and then use the MCP inspector.

Key features of Chrome MCP Server

  • Provides an MCP implementation independent of Anthropic’s library.
  • Supports taking screenshots of a webpage.
  • Allows validation of implementation in Cursor.
  • Includes a demo implementation with initialization over SSE and POST endpoints.
  • Offers a more robust implementation using the MCP Python SDK.

Use cases of Chrome MCP Server

  • Taking screenshots of pages for visual verification.
  • Validating implementation in Cursor during development.
  • Learning the MCP protocol through a hands‑on example.

常见问题

1

Is Chrome MCP Server a reference implementation of the MCP protocol?

No, it is not a reference implementation. It was built as a learning exercise to understand the protocol.

2

What are the limitations of the demo implementation?

The demo implementation has several limitations, including lack of error handling and inadequate cleanup of sessions.

3

How does the initialization process work in the demo implementation?

Initialization is done in three steps: 1) an initial call to `/sse` to get the session URI, 2) the client sends an `initialize` message, and 3) the client sends a `notifications/initialized` message.

4

What transport does the robust implementation use?

The robust implementation uses SSE (Server‑Sent Events) transport.

评论

其他 分类下的更多 MCP 服务器