MCP Chrome Feedback - 提供MCP服务与Chrome扩展交互的反馈收集功能
If you already use MCX, the mcx mcp server is the piece that lets your assistant work with it directly. MCP Chrome Feedback - 提供MCP服务与Chrome扩展交互的反馈收集功能.
mcp-chrome-feedback@latest - 清理npm缓存: npm cache clean --forceThe toolset is worth reading before you wire it up, because it tells you what the integration is really for:
summary — AI工作摘要 (默认: "我已完成了您请求的任务。")timeout — 超时时间(秒) (默认: 600)project_directory — 项目目录 (默认: ".")limit — 返回记录数量 (默认: 10)MCP_CHROME_PORT — Chrome扩展通信端口 (默认: 8797，如端口被占用会自动递增到可用端口)interactive_feedback — The interactive_feedback tool exposed by this serverget_feedback_history — The get_feedback_history tool exposed by this serverget_extension_status — The get_extension_status tool exposed by this serverclear_feedback_history — The clear_feedback_history tool exposed by this servermcp-chrome-feedback on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: MCP_CHROME_PORT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCX's toolset — summary, timeout, project_directory and 6 more — is a fair guide to whether it matches your workflow. It is maintained by 2019-02-18; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| summary | AI工作摘要 (默认: "我已完成了您请求的任务。") |
| timeout | 超时时间(秒) (默认: 600) |
| project_directory | 项目目录 (默认: ".") |
| limit | 返回记录数量 (默认: 10) |
| MCP_CHROME_PORT | Chrome扩展通信端口 (默认: 8797，如端口被占用会自动递增到可用端口) |
| interactive_feedback | The interactive_feedback tool exposed by this server. |
| get_feedback_history | The get_feedback_history tool exposed by this server. |
| get_extension_status | The get_extension_status tool exposed by this server. |
| clear_feedback_history | The clear_feedback_history tool exposed by this server. |
{
"mcpServers": {
"chrome-feedback": {
"command": "npx",
"args": ["mcp-chrome-feedback@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_CHROME_PORT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.