LABSCO SUMMARY

Capturing the element, not just the complaint, is what makes browser feedback actionable.

A screenshot tells the agent what is wrong; the captured element tells it where. Without that, every piece of feedback starts with the agent guessing which component you meant. Keeping a history matters for the same reason it matters in any review loop — the second round needs to know what the first one said. The author credits their inspirations openly, which is a small good sign about a small project.

What it is

A pairing of a server and a Chrome extension so a person can leave feedback in the browser and an agent can read it, with the two connected over a live socket.

What you get

Interactive feedback collection through the extension interface
Text and image attachments
Real-time communication rather than polling
Feedback history, saved and managed automatically
Element capture and screenshots from the page

Requirements

The Chrome extension alongside the server. MIT licensed. Documentation is in Chinese.

Setup effort

One command — npm install -g mcp-chrome-feedback@latest

See installation options

USE CASES

01

Pointing at what is broken

Capture the element, not just a description.

interactive_feedbackget_extension_status

02

Attaching a picture

Images alongside the text.

interactive_feedback

03

Following up

Saved history across rounds.

get_feedback_historyclear_feedback_history

4 tools

Listed in project docs. Your client may show a different list.

interactive_feedback

get_feedback_history

get_extension_status

clear_feedback_history

BEFORE YOU INSTALL

What to know first

Tools you get

4 tools named in the project's documentation. interactive_feedback is the core tool; the other three manage feedback history and extension status. Element capture, screenshots and image paste belong to the Chrome extension, and nothing works until it is installed and connected.

Requires

npx on PATH

Where it runs

All 4 documented setups run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

npm install -g mcp-chrome-feedback@latest

MCP Clients

Cursor — npx

CURSOR — NPX · JSON

{
  "mcpServers": {
    "chrome-feedback": {
      "command": "npx",
      "args": [
        "mcp-chrome-feedback@latest"
      ]
    }
  }
}

Cursor — global install

CURSOR — GLOBAL INSTALL · JSON

{
  "mcpServers": {
    "chrome-feedback": {
      "command": "mcp-chrome-feedback"
    }
  }
}

Cursor — npx, fixed port

CURSOR — NPX, FIXED PORT · JSON

{
  "mcpServers": {
    "chrome-feedback": {
      "command": "npx",
      "args": [
        "mcp-chrome-feedback@latest"
      ],
      "env": {
        "MCP_CHROME_PORT": "8900"
      }
    }
  }
}

Cursor — local build

CURSOR — LOCAL BUILD · JSON

{
  "mcpServers": {
    "chrome-feedback": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_MCX>/mcp-chrome-feedback/build/index.js"
      ]
    }
  }
}

Chrome Feedback Collector