MarkLayer

<p align="center"> <a href="https://marklayer.app"> <img src=".github/icon.svg" width="112" height="112" alt="MarkLayer logo"> </a> </p> <h1 align="center">MarkLayer</h1> <p align="center"><strong>Website feedback your AI agent can act on.</strong></p> <p align="center"> Draw, highlight, and comment on any live webpage, then share one link. A human reviews it in real time, or an AI agent connects over MCP and works it like a to-do list: acknowledge, fix, resolve, reply. </p> <p align="center"> <a href="https://marklayer.app"><strong>Try MarkLayer</strong></a> · <a href="https://chromewebstore.google.com/detail/marklayer/fnfobegjifomgobgilaemihpcpidjamc">Add to Chrome</a> · <a href="#built-for-ai-agents">Connect an agent</a> · <a href="#self-hosting--development">Build from source</a> </p> <p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-5b47d6?style=flat-square" alt="Apache-2.0 license"></a> <a href="https://marklayer.app"><img src="https://img.shields.io/badge/no%20account-required-1f9d68?style=flat-square" alt="No account required"></a> <a href="https://www.npmjs.com/package/marklayer-mcp"><img src="https://img.shields.io/npm/v/marklayer-mcp?style=flat-square&label=mcp&color=5b47d6" alt="marklayer-mcp on npm"></a> <a href="https://github.com/thevrus/MarkLayer"><img src="https://img.shields.io/github/stars/thevrus/MarkLayer?style=flat-square" alt="GitHub stars"></a> </p> <p align="center"> <a href="https://marklayer.app"><img src="https://raw.githubusercontent.com/thevrus/MarkLayer/main/apps/worker/static/product-review-wikipedia.webp" alt="A MarkLayer review board open on Wikipedia, showing highlights, threaded comments, and live cursors" width="900"></a> </p> ## One URL. A shared board. A faster decision. MarkLayer turns any webpage into a collaborative review surface. Instead of passing screenshots back and forth, send a link. Teammates or clients can open the original page in their own browser, leave feedback where it belongs, and see changes land live. So can an AI agent: each comment arrives with the exact element it refers to already attached. - **For AI-assisted work**: give an agent the share link over MCP and it works the annotations as a live queue: acknowledge, fix, resolve. Nothing to install. Or inspect an element yourself for a stable selector and an AI-ready markdown snapshot. - **For client feedback**: let clients point to exactly what they mean, without an account or extension. - **For design review**: sketch ideas, highlight details, and keep the conversation attached to the page. - **For QA**: pin reproducible issues to the actual UI, then share a clean link with the team. ## How it works 1. **Open a page**: paste any public URL at [marklayer.app](https://marklayer.app), or use the Chrome extension on the page you are already viewing — including a page on your own `localhost` dev server, which never has to be reachable from the internet. 2. **Make the feedback visible**: draw, highlight text, measure space, pin a threaded comment, or inspect an element. 3. **Share one link**: collaborators join the same board and see cursors, marks, replies, and calls in real time. Point an AI agent at the same link over MCP instead, and the thread becomes its work queue. No sign-up. No trial clock. No client install. ## What you can do | | | |---|---| | **Send an agent to work the page** | Every share link is also a remote MCP server, so an AI agent can watch annotations and acknowledge, fix, and resolve them live, or review the page and leave notes of its own. | | **Annotate freely** | Pen, highlighter, eraser, shapes, arrows, text, and text-selection highlights. | | **Keep feedback in context** | Pin threaded comments to the page, reply inline, and track status. | | **Review live** | Real-time cursors, drawings, and comments via WebSocket, plus peer-to-peer voice and video chat. | | **Hand off agent-ready context** | Inspect an element for a stable selector, computed styles, parent layout, viewport details, and framework component info, packaged as markdown built for a coding agent's prompt. | | **Measure the UI** | Check element dimensions and edge-to-edge gaps between two elements. | | **Share or export** | Create shareable links with preview cards, or export annotations to PNG. | | **Make it yours** | Reorder toolbar tools; drafts persist locally and restore when you return. | ## Built for AI agents Every annotation is part of a structured queue: an agent can read it, act on it, and report back, the same way a human would. **Connect over MCP, with nothing installed.** Every share link is also a remote MCP server. Add `/mcp` to it: ~~~bash claude mcp add --transport http marklayer https://marklayer.app/s/<id>/mcp ~~~ Any client that accepts a remote (Streamable HTTP) server URL takes the same address. Add `?agent=cursor`, or any name, so the people in the room can see who is doing the work. The share panel on every link shows the command with the id filled in. If a client only runs local servers, [`marklayer-mcp`](apps/mcp) has the same tools as a stdio package, installed once for every room: ~~~bash claude mcp add marklayer -- npx -y marklayer-mcp ~~~ Then just ask: *"Watch my MarkLayer annotations. For each one, acknowledge it, make the fix, then resolve it with a summary."* The agent calls `marklayer_watch_annotations` in a loop, and the human watches every status change land live. It can go first, too: `read_page` hands it the page's text and controls with their selectors, so an agent asked to review a page leaves its own comments and suggests exact copy edits as diffs. The full toolset is documented in [apps/mcp](apps/mcp/README.md). **Every mark carries the context an agent needs.** Inspecting an element captures its CSS selector, computed styles, parent layout, and framework component info as a markdown snapshot, so a comment arrives with the exact node attached instead of a vague description. **Or from inside the browser.** On a browser agent with WebMCP support, the same list, acknowledge, resolve, and reply actions are exposed straight from the page via `document.modelContext`. Nothing to configure. **Agents can open their own boards, too.** The share id is the access token, so minting a room is one unauthenticated POST, handy for seeding a review per URL ahead of time: ~~~bash curl -X POST https://marklayer.app/api/$ID \ -H 'Content-Type: application/json' \ -d '{"ops":[],"url":"https://example.com","width":1440}' ~~~ **Discoverable machine-first.** [`/llms.txt`](https://marklayer.app/llms.txt), [`/llms-full.txt`](https://marklayer.app/llms-full.txt), [`/.well-known/api-catalog`](https://marklayer.app/.well-known/api-catalog), an [MCP server card](https://marklayer.app/.well-known/mcp/server-card.json), an [agent skill](https://marklayer.app/.well-known/agent-skills/index.json), and a full [OpenAPI spec](https://marklayer.app/api/openapi.json) describe the whole surface for an agent that's never seen MarkLayer before. ## Built to respect the reviewer's time and privacy - **No accounts or tracking**: start reviewing immediately. - **Links expire thoughtfully**: shared boards expire 90 days after their last view. - **Open source and self-hostable**: MarkLayer is released under [Apache-2.0](LICENSE), so your workflow is not tied to a pricing change. Want the non-technical version? Read [How MarkLayer works](https://marklayer.app/guides/how-marklayer-works). ## Self-hosting & development ~~~bash git clone https://github.com/thevrus/MarkLayer.git cd MarkLayer bun install bun run dev ~~~ For the Chrome extension in development: 1. Build or run the extension app. 2. Open <code>chrome://extensions/</code> and turn on **Developer mode**. 3. Choose **Load unpacked** and select <code>apps/extension/.output/chrome-mv3-dev</code>. ### Repository layout ~~~ ├── apps/extension/ Chrome extension (WXT + Preact) ├── apps/worker/ Cloudflare Worker, API, real-time rooms, proxy, OG generator ├── apps/site/ Static marketing site (Astro) ├── apps/mcp/ MCP server for AI agents (published as marklayer-mcp) ├── packages/types/ Shared TypeScript types └── packages/agent-tools/ Agent tool contract shared by the MCP server ~~~ ### Stack | Area | Technologies | |---|---| | Frontend | Preact, Signals, Tailwind CSS, Vite | | Extension | WXT, Chrome APIs | | Backend | Cloudflare Workers, Hono, Durable Objects | | Storage | D1 (SQLite), R2 | | Real-time | WebSockets, WebRTC | | Agent integration | MCP (remote at every share link, plus a stdio package), WebMCP, OpenAPI | ### Scripts | Command | What it does | |---|---| | <code>bun run dev</code> | Run the workspace in development mode | | <code>bun run build</code> | Build all apps | | <code>bun run check</code> | Type-check the workspace | | <code>bun run lint</code> | Lint and format-check with Biome | | <code>bun run lint:fix</code> | Apply lint and formatting fixes | | <code>cd apps/worker && bun run deploy</code> | Deploy the Worker to Cloudflare | | <code>cd apps/mcp && bun run build</code> | Build the MCP server (<code>marklayer-mcp</code>) to <code>dist/cli.js</code> | | <code>cd apps/site && bun run indexnow:submit</code> | Ping IndexNow (Bing and friends) after a deploy that changed pages | ## Contributing Found a bug or have an idea? [Open an issue](https://github.com/thevrus/MarkLayer/issues). Contributions are welcome. ## License [Apache License 2.0](LICENSE) © [Dean Rusin](https://github.com/thevrus) --- <p align="center"> <a href="https://marklayer.app">Try MarkLayer</a> · <a href="#built-for-ai-agents">Connect an agent</a> · <a href="https://chromewebstore.google.com/detail/marklayer/fnfobegjifomgobgilaemihpcpidjamc">Add to Chrome</a> · <a href="https://github.com/thevrus/MarkLayer/issues">Report a bug</a> · <a href="https://github.com/thevrus/MarkLayer/issues">Request a feature</a> </p>