原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MarkLayer

作者:thevrus版本 0.6.1i★ –i在你的电脑上运行
注册名称io.github.thevrus/marklayer

安装

概览

作者提供的说明(英文原文)

Work visual annotations on a live webpage: watch, acknowledge, resolve, reply, or leave your own.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 网页与浏览器

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: MARKLAYER_ROOM, MARKLAYER_API_BASE, MARKLAYER_AGENT

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "marklayer": {
      "command": "npx",
      "args": [
        "-y",
        "marklayer-mcp"
      ],
      "env": {
        "MARKLAYER_ROOM": "your-value",
        "MARKLAYER_API_BASE": "your-value",
        "MARKLAYER_AGENT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add marklayer --env MARKLAYER_ROOM=your-value --env MARKLAYER_API_BASE=your-value --env MARKLAYER_AGENT=your-value -- npx -y marklayer-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "marklayer": {
      "command": "npx",
      "args": [
        "-y",
        "marklayer-mcp"
      ],
      "env": {
        "MARKLAYER_ROOM": "your-value",
        "MARKLAYER_API_BASE": "your-value",
        "MARKLAYER_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "marklayer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "marklayer-mcp"
      ],
      "env": {
        "MARKLAYER_ROOM": "your-value",
        "MARKLAYER_API_BASE": "your-value",
        "MARKLAYER_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • MARKLAYER_ROOM env
    Same as --room: the share URL or room id to join at startup.
  • MARKLAYER_API_BASE env
    Override the MarkLayer worker base URL. Defaults to https://marklayer.app; useful against a local dev worker.
  • MARKLAYER_AGENT env
    Name shown to the humans in the room for this agent. Defaults to claude-code.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 thevrus 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

  • 星标数多于此分类中其他 878 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 878 个服务器的 84% 更新
  • 基础检查结果等于或优于此分类中其他 878 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MarkLayer 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.6.1)于6天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者:browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT17天前更新
安装

Chrome DevTools MCP

作者:ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.015天前更新
安装

MCP Server Browser

作者:bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

marklayer-mcp

MCP (Model Context Protocol) server that bridges MarkLayer annotations to AI coding agents.

When users annotate any webpage with MarkLayer, your agent receives the comments as a structured work queue: it can acknowledge, resolve, dismiss, and reply to each one — and the human sees the status updates live. It also works the other way: point an agent at a room and ask it to review the page, and it can leave its own comments and copy-edit suggestions for the human to triage.

Install

You may not need to. Every MarkLayer share link is already a remote MCP server at the same address plus /mcp, so a client that supports remote (Streamable HTTP) servers connects with nothing installed:

claude mcp add --transport http marklayer https://marklayer.app/s/abc123/mcp

Append ?agent=cursor, or any name, so the people in the room see who is working; it defaults to agent. That endpoint is bound to its room, so it has every tool below except marklayer_connect_room.

This package is the stdio version of the same tools, with no Claude-specific wiring. Use it when a client cannot reach remote servers, or when you want one install that covers every room (Claude Code, Cursor, Windsurf, VS Code, Codex CLI, etc.):

# Claude Code:

claude mcp add marklayer -- npx -y marklayer-mcp

Or pre-connect to a specific room:

claude mcp add marklayer -- npx -y marklayer-mcp --room https://marklayer.app/s/abc123

For any other MCP client, add a stdio server entry pointing at the same command (adjust the config file/key to your client — Cursor's ~/.cursor/mcp.json, Windsurf's mcp_config.json, VS Code's .vscode/mcp.json, etc.):

{

"mcpServers": { "marklayer": { "command": "npx", "args": ["-y", "marklayer-mcp"], "env": { "MARKLAYER_AGENT": "cursor" } } } }

Set MARKLAYER_AGENT (or --agent) to identify which agent this is — it's what humans see as the comment author and the "assigned to" badge, so a non-Claude client should not leave it at the default.

Usage

In your agent prompt:

Watch my MarkLayer annotations. For each one, acknowledge it, make the fix, then resolve it with a summary.

The agent will call marklayer_watch_annotations in a loop and process incoming feedback as it arrives.

Tools

ToolDescription
marklayer_connect_roomConnect to a room by share URL or bare id.
marklayer_room_infoPage URL, viewport width, timestamps.
marklayer_read_pageThe page's headings, text, links and controls, with selectors. Lets the agent review a page nobody has annotated yet.
marklayer_list_annotationsList annotations, optionally filtered by status.
marklayer_get_annotationFull detail + reply thread for one annotation.
marklayer_watch_annotationsBlock until new annotations arrive, return a batch.
marklayer_acknowledgeMark in-progress and tag with this agent.
marklayer_resolveMark resolved, optionally posting a reply with the summary.
marklayer_dismissMark dismissed with a reason the human will see.
marklayer_replyPost a reply without changing status (e.g. clarifying questions).
marklayer_create_annotationLeave a new comment yourself — proactive feedback rather than a response.
marklayer_suggest_editPropose an exact copy/grammar fix for a piece of text, as a diff the human can accept.
marklayer_share_previewOpen a new review room on a URL you built and connect to it. Same repo + branch as the room you are in (or previous) makes it the next version.
marklayer_set_next_stepsPublish an ordered checklist, each step linked to annotation ids. Replaces the previous list.
marklayer_complete_next_stepTick a step off; reviewers see it live.
marklayer_askPut a 2-6 option poll to the room. One vote per reviewer, revotable.
marklayer_get_feedbackOne read: annotation counts by status, open annotations, checklist progress, poll tallies.

Options

--room <url-or-id>   Connect at startup; otherwise call marklayer_connect_room.

--api-base Override worker URL (default https://marklayer.app). --agent Identifier shown to humans (default "claude-code").

Equivalent env vars: MARKLAYER_ROOM, MARKLAYER_API_BASE, MARKLAYER_AGENT.

Troubleshooting

"Connection closed" on first start. npx -y downloads the package on the first run, and a cold download can outlast the MCP client's startup timeout. Prime the cache once (npx -y marklayer-mcp --help) and reconnect, or install it up front with npm i -g marklayer-mcp and point the client at the binary.

Tools return "room is not connected". The WebSocket dropped — rooms are held open by a Durable Object and a long-idle agent can be disconnected. Call marklayer_connect_room with the same URL to reattach.

Creating rooms programmatically

This server *consumes* an existing share link. To *mint* one (or many) from code — e.g. seed a room per page in a batch of URLs before pointing the agent at it — POST directly to the public HTTP API:

curl -X POST https://marklayer.app/api/$ID \

-H 'Content-Type: application/json' \ -d '{"ops":[],"url":"https://example.com/page-1","width":1440,"expires_in":2592000}'

Share link: https://marklayer.app/s/$ID

For a review room on a preview build, POST /api/$ID/preview takes { url, title, repo?, branch?, sha?, note?, questions?, previous? } and never overwrites an existing id. Versions chain only through previous, a room you already hold: two rooms are never linked by repo and branch alone, because the version switcher shows each room's neighbours. marklayer_share_preview calls this route over stdio; over HTTP (/s/:id/mcp) it creates the room in the Worker, chains from the room in the URL, and returns an mcpUrl to reconnect to, since that endpoint stays bound to its own room.

$ID is caller-supplied (use nanoid / crypto.randomUUID() — it's the access token). No auth, no SDK. Full details: https://marklayer.app/llms-full.txt

问 PopNx