Cowork Qa

io.github.inSideos-designs由 GitHub 账号 inSideos-designs 发布v0.1.1更新于 Oct 24, 2026

Goal-driven Playwright browser sessions for LLMs, with full action traces and aria-snapshots.

已验证STDIO仅桌面浏览器自动化开发者工具

概览

AI 生成的概览

通过 Playwright 为助手提供真实的 Chromium 浏览器,记录朝既定目标执行的每一步操作,并返回结构化追踪记录供复核。

可以做什么
以目标驱动的方式运行浏览器会话,提供五个工具:session_start 打开标签页并返回会话 id,session_act 执行 goto、click、fill、press 或 eval,session_observe 返回当前 URL 和完整 aria 快照,session_end 关闭标签页并持久化追踪记录,qa_get_trace 返回目标、每一步操作、最终 URL 和最终 aria 快照。每个操作都会记录时间戳、操作后的 URL 以及页面 aria 快照,便于编排模型事后判断目标是否达成。
适用场景
适合需要让助手驱动真实浏览器完成明确目标、并希望留下可审计操作记录的场合,而不是无状态的点击加读取循环。适用于脚本化的网页检查以及浏览会话的事后评估。
运行要求
以 stdio 运行的本地进程;需要 Node 20 或更高版本,通过 npx 或 npm 安装(cowork-qa-mcp)。首次安装会通过 Playwright 的 postinstall 下载 Chromium(约 150 MB)。可选环境变量:COWORK_QA_DATA 指定追踪记录输出目录(默认 /.cowork-qa),COWORK_QA_HEADED=1 显示浏览器窗口而非无头运行。仅支持桌面端;未声明身份验证。
安装前请注意
浏览器会操作真实页面:click、fill、press 和 eval 可能提交表单、修改数据或触发购买,eval 会在页面中执行 JavaScript。追踪记录(包含页面 aria 快照和访问过的 URL)会以 JSON 文件写入 COWORK_QA_DATA 目录,请将该目录指向你愿意存放这些内容的位置。eval 不会把返回值交给调用方,session_observe 调用也不计入追踪记录的步骤数。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Cowork Qa,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

cowork-qa-mcp

[demo]

A Model Context Protocol server that gives an LLM a real Chromium browser, records every action it takes toward a stated goal, and hands back a structured trace so the LLM (or a second LLM) can decide whether the goal was actually achieved.

Built on Playwright. Five tools, one binary, no cloud dependency.

Why

Most browser-tool MCP servers are stateless — the LLM clicks, gets HTML back, repeats. There's no record of what happened, no way to grade the run after the fact, and no goal context.

cowork-qa-mcp flips that:

  • Every session starts with a goal in plain English.
  • Every action (goto, click, fill, press, eval) is recorded with timestamps, the URL after, and the page's aria-snapshot.
  • When the session ends, a JSON trace is persisted to disk and exposed via a single qa_get_trace call.

The orchestrating LLM can then reason over the trace ("did this run actually fulfill the goal, or did it click the wrong button?") instead of trusting the run-time chatter.

Tools

ToolWhat it does
session_startOpen a fresh tab, optional starting URL, return a session id
session_actRun one of: goto, click, fill, press, eval. Records the step.
session_observeReturn current URL + full aria-snapshot of the page
session_endClose the tab, persist the trace to disk, return the file path
qa_get_traceReturn the goal, every step, final URL, and final aria-snapshot — formatted for an LLM to read

Install

Requires Node 20+. The package is on npm — no clone needed.

bash
# Try it once, no installnpx cowork-qa-mcp
# Or install globallynpm install -g cowork-qa-mcp

The first install pulls Chromium via Playwright's postinstall (~150 MB).

Wire into your MCP-compatible client

Claude Code

bash
claude mcp add cowork-qa --scope user -- npx -y cowork-qa-mcp

To watch the browser instead of running headless:

bash
claude mcp add cowork-qa --scope user \  -e COWORK_QA_HEADED=1 \  -- npx -y cowork-qa-mcp

Verify with /mcp inside a fresh claude session — you should see cowork-qa ✓ connected and 5 tools.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "cowork-qa": {      "command": "npx",      "args": ["-y", "cowork-qa-mcp"]    }  }}

Cursor / Windsurf / other MCP clients

Any client that speaks the MCP stdio transport works. Point its server config at npx -y cowork-qa-mcp.

From source (for development)

bash
git clone https://github.com/inSideos-designs/cowork-qa-mcp.gitcd cowork-qa-mcpnpm installnpm run buildnode dist/server.js   # stdio server, expects an MCP client

MCP Registry

This server is also published on the official MCP Server Registry as io.github.inSideos-designs/cowork-qa — clients that auto-discover from the registry will find it without any manual config.

Environment variables

VariableDefaultPurpose
COWORK_QA_HEADEDunset (headless)Set to 1 to launch Chromium with a visible window
COWORK_QA_DATA<cwd>/.cowork-qaDirectory where <session-id>.json traces are written

Usage example

A typical end-to-end loop the orchestrating LLM runs:

session_start({ goal: "find the cheapest 14\" MacBook Pro on apple.com",                url: "https://www.apple.com/shop/buy-mac/macbook-pro" })  → { session_id: "abc-123" }
session_observe({ session_id: "abc-123" })  → URL + aria-snapshot
session_act({ session_id: "abc-123", action: "click",              target: "button:has-text('Continue')" })
# ... more acts / observes ...
session_end({ session_id: "abc-123" })  → { steps: 7, trace_path: "~/.cowork-qa/abc-123.json" }
qa_get_trace({ session_id: "abc-123" })  → Goal: ...    Steps (7 total): ...    Final URL: ...    Final aria-snapshot: ...

Trace format

Each trace is a JSON file:

json
{  "session_id": "abc-123",  "goal": "...",  "steps": [    {      "t": 142,      "action": "click",      "args": { "target": "...", "value": null },      "url_after": "...",      "aria_after": "..."    }  ],  "final": { "url": "...", "aria": "..." },  "path": "/.../abc-123.json"}

Limitations / known quirks

  • session_observe calls don't show up in the trace's step count — only session_act calls do. The final aria-snapshot is captured at session_end.
  • eval runs the JS expression but doesn't return the value to the caller — only side effects on the page are observable.
  • One Chromium process is shared across all sessions in a server instance; each session gets its own context (cookies, etc. are isolated).
  • Selectors are passed straight to Playwright. CSS, text-selectors (button:has-text("Send")), and role= selectors all work.

License

MIT — see LICENSE.

Contributing

PRs welcome. Keep it small: this is meant to stay a thin, auditable server.

来源:README.md,提交 bdf3971

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分