Domscribe MCP server
Commit Nov 14, 2026Lets AI coding agents inspect live DOM, props, and state from a running web app and map browser elements back to exact source files and lines.
Also known as patchorbit/domscribe
- Stars
- 195
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- MIT
What is Domscribe MCP?
Domscribe lets AI coding agents inspect live DOM, props, and state from a running web app and map browser elements back to exact source files and lines.
Summary generated from the project's README
About Domscribe MCP server
Connecting AI coding agents to the live state of a running web application is what Domscribe enables. It allows developers to bridge the gap between source code and the browser by providing agents with visibility into the DOM, component props, and internal state. This works by using build-time stable IDs and deep runtime inspection to map browser elements directly back to specific files and line numbers in your repository.
To use this, you must install the appropriate framework package for your stack, such as React, Vue, Next.js, or Nuxt, and integrate it with your bundler like Vite, Webpack, or Turbopack. Once the app-side is configured, you connect an MCP-compatible agent like Claude Code, GitHub Copilot, Gemini, or Kiro using the provided plugins. The system is designed for local development and includes automatic PII redaction to ensure sensitive data like tokens or emails are scrubbed before being sent to the agent.
What you can do with it
- 1Inspect live component stateAsk your agent to check the current props and state of a specific component directly from the running browser.
- 2Implement UI changes from clicksPoint to an element in the browser overlay and tell the agent to modify its appearance or behavior.
- 3Debug CSS and attributesInstruct the agent to verify specific CSS classes or attributes on a live element before attempting a code fix.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablepatchorbit/domscribe is public and reachablegithub.com/patchorbit/domscribe ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-01github.com/patchorbit/domscribe ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubAI coding agents edit your source files blind — they can't see your running frontend, and your frontend can't tell them where to look.
Domscribe bridges both directions: click a DOM element to tell your agent what to change, or let your agent query any source location to see exactly what it looks like live in the browser. Build-time stable IDs, deep runtime context (props, state, DOM), framework-agnostic, any MCP-compatible agent. Zero production impact.
Getting Started
npx domscribe init
The setup wizard walks you through two steps:
- Connect your coding agent — select your agent (Claude Code, Copilot, Gemini, Kiro, or others) and the wizard installs the plugin automatically.
- Add to your app — select your framework and bundler, the wizard installs the right package and shows you the config snippet to add.
That's it. Start your dev server and you're ready to go.
Prefer to set things up manually, or need finer control? See the manual setup instructions below.
Features
Code → UI: Let the agent see the browser
Your agent calls domscribe.query.bySource with a file path and line number and gets back the live DOM snapshot, current props, component state, and rendered attributes — directly from the running browser. No human interaction needed.
[!TIP] Agents don't spontaneously query runtime state — prompt them explicitly: "Fix the button color — use domscribe to check what CSS classes it has before changing anything." Your dev server must be running with the target page open in the browser.
UI → Code: Point and tell
Click any element in the browser overlay, describe the change in plain English, and submit. Domscribe captures the element's source location, runtime context, and your instruction as an annotation. The agent claims it, navigates to the exact file and line, and implements the change. The overlay shows the agent's response in real time via WebSocket.
More
- 🎯 Build-time stable IDs — deterministic
data-dsattributes injected via AST, stable across HMR and fast refresh - 🧩 Framework-agnostic — React 18-19, Vue 3, Next.js 15-16, Nuxt 3+, with an extensible adapter interface
- 📦 Any bundler — Vite 5-8, Webpack 5, Turbopack (Vite 8 support requires Domscribe 0.7.0 or later)
- 🔍 Deep runtime capture — live props, state, and DOM snapshots via React fiber walking and Vue VNode inspection
- 🛡️ Zero production impact — all instrumentation stripped in production builds, enforced in CI
- 🔒 PII redaction — emails, tokens, and sensitive patterns automatically scrubbed before leaving the browser
- 📁 Annotations live in your repo — stored as JSON files in
.domscribe/annotations/, exposed via REST APIs that MCP wraps for agent access - 📡 Real-time feedback — WebSocket relay pushes agent responses to the browser overlay as they happen
Manual Setup
[!NOTE]
npx domscribe inithandles both steps below automatically. Use manual setup only if you need finer control.
Domscribe has two sides: app-side (bundler + framework plugins) and agent-side (MCP for your coding agent). Both are needed for the full workflow.
App-Side — Add to Your Bundler
// next.config.ts
import type { NextConfig } from 'next';
import { withDomscribe } from '@domscribe/next';
const nextConfig: NextConfig = {};
export default withDomscribe()(nextConfig);
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@domscribe/nuxt'],
});
Vite plugin:
// vite.config.ts
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import { domscribe } from '@domscribe/react/vite';
export default defineConfig({
plugins: [react(), domscribe()],
});
Webpack plugin:
// webpack.config.js
const { DomscribeWebpackPlugin } = require('@domscribe/react/webpack');
const isDevelopment = process.env.NODE_ENV !== 'production';
module.exports = {
module: {
rules: [
{
test: /\.[jt]sx?$/,
exclude: /node_modules/,
enforce: 'pre',
use: [
{
loader: '@domscribe/transform/webpack-loader',
options: { enabled: isDevelopment },
},
],
},
],
},
plugins: [
new DomscribeWebpackPlugin({
enabled: isDevelopment,
overlay: true,
}),
],
};
Vite plugin:
// vite.config.ts
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
import { domscribe } from '@domscribe/vue/vite';
export default defineConfig({
plugins: [vue(), domscribe()],
});
Webpack plugin:
// webpack.config.js
const { DomscribeWebpackPlugin } = require('@domscribe/vue/webpack');
const isDevelopment = process.env.NODE_ENV !== 'production';
module.exports = {
module: {
rules: [
{
test: /\.[jt]sx?$/,
exclude: /node_modules/,
enforce: 'pre',
use: [
{
loader: '@domscribe/transform/webpack-loader',
options: { enabled: isDevelopment },
},
],
},
],
},
plugins: [
new DomscribeWebpackPlugin({
enabled: isDevelopment,
overlay: true,
}),
],
};
Vite plugin:
// vite.config.ts
import { defineConfig } from 'vite';
import { domscribe } from '@domscribe/transform/plugins/vite';
export default defineConfig({
plugins: [domscribe()],
});
Webpack plugin:
// webpack.config.js
const {
DomscribeWebpackPlugin,
} = require('@domscribe/transform/plugins/webpack');
const isDevelopment = process.env.NODE_ENV !== 'production';
module.exports = {
module: {
rules: [
{
test: /\.[jt]sx?$/,
exclude: /node_modules/,
enforce: 'pre',
use: [
{
loader: '@domscribe/transform/webpack-loader',
options: { enabled: isDevelopment },
},
],
},
],
},
plugins: [
new DomscribeWebpackPlugin({
enabled: isDevelopment,
overlay: true,
}),
],
};
Working examples: See
packages/domscribe-test-fixtures/fixtures/for complete app setups across every supported framework and bundler combination.
For plugin configuration options, see the @domscribe/transform README.
Monorepos
If your frontend app is in a subdirectory (e.g. apps/web), pass --app-root during init:
npx domscribe init --app-root apps/web
Or run npx domscribe init and follow the prompts — the wizard asks if you're in a monorepo.
This creates a domscribe.config.json at your repo root that tells all Domscribe tools where your app lives. CLI commands (serve, stop, status) and agent MCP connections automatically resolve the app root from this config — no extra flags needed.
Agent-Side — Connect Your Coding Agent
Domscribe exposes 12 tools and 4 prompts via MCP. Agent plugins bundle the MCP config and a skill file that teaches the agent how to use the tools effectively.
Claude Code
claude plugin marketplace add patchorbit/domscribe
claude plugin install domscribe@domscribe
GitHub Copilot
copilot plugin install patchorbit/domscribe
Gemini CLI
gemini extensions install https://github.com/patchorbit/domscribe
Amazon Kiro
Open the Powers panel → Add power from GitHub → enter https://github.com/patchorbit/domscribe/tree/main/domscribe-power.
Cursor
Any agent (Skills and MCP)
Install the Domscribe skills:
npx skills add patchorbit/domscribe
Then add this MCP config to your agent:
{
"mcpServers": {
"domscribe": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@domscribe/mcp"]
}
}
}
How It Works
1. Inject. The bundler plugin parses each source file, injects HMR-stable data-ds IDs via xxhash64, and records each mapping in .domscribe/manifest.jsonl.
2. Capture. Framework adapters (React fiber walking, Vue VNode inspection) extract live props, state, and component metadata. The overlay UI lets you click any element and see its full context.
3. Relay. A localhost Fastify daemon connects the browser and your agent via REST, WebSocket, and MCP stdio. A file lock prevents duplicate instances across dev server restarts.
4. Agent. Your coding agent connects via MCP to query by source (see what any line looks like live) or process annotations (claim, implement, and respond to UI change requests).
Comparison
| Feature | Domscribe | Stagewise | DevInspector MCP | React Grab | Frontman |
|---|---|---|---|---|---|
| Build-time stable IDs | ✅ data-ds via AST |
❌ Runtime (CDP) | ❌ No stable IDs | ❌ _debugSource |
❌ Runtime framework introspection |
| DOM→source manifest | ✅ JSONL, append-only | ❌ | ❌ | ❌ | ❌ |
| Code→live DOM query | ✅ Agent queries source, gets live runtime | ❌ | ❌ | ❌ | ❌ |
| Runtime props/state | ✅ Fiber + VNode walking | ⚠️ Shallow | ⚠️ DOM-level + JS eval | ❌ HTML + component names only | ⚠️ Props only (framework APIs) |
| Multi-framework | ✅ React · Vue · Next.js · Nuxt · extensible | ⚠️ React only | ✅ React + Vue + Svelte + Solid + Preact | ❌ React only | ⚠️ Next.js + Astro + Vite |
| Multi-bundler | ✅ Vite + Webpack + Turbopack | ❌ N/A (Electron browser) | ✅ Vite + Webpack + Turbopack | ❌ N/A | ❌ Dev server middleware |
| MCP tools | ✅ 12 tools + 4 prompts | ❌ Proprietary protocol (Karton) | ✅ 9 tools | ⚠️ Lightweight add-on | ❌ Internal MCP only |
| Agent-agnostic | ✅ Any MCP client | ❌ Bundled Electron agent | ✅ | ✅ | ❌ Bundled Elixir agent |
| In-app element picker | ✅ Lit shadow DOM | ✅ Built-in browser selector | ✅ Inspector bar | ✅ Hover-to-capture | ✅ Chat interface |
| Source mapping | ✅ Deterministic (AST IDs) | ⚠️ AI-inferred | ⚠️ AST-injected (not stable) | ⚠️ _debugSource (workaround needed) |
⚠️ Runtime framework introspection |
| License | ✅ MIT | ⚠️ AGPL | ✅ MIT | ✅ MIT | ⚠️ Apache + AGPL |
No single competitor combines build-time stable IDs, deep runtime capture, bidirectional source↔DOM querying, and an MCP tool surface in a framework-agnostic way.
MCP Tools
The agent-facing surface — tools, prompts, wire schemas, and error envelope — is listed below as a human-readable index.
| Tool | Description |
|---|---|
domscribe.query.bySource |
Query a source file + line and get live runtime context (props, state, DOM snapshot) |
domscribe.manifest.query |
Find manifest entries by file path, component name, or element ID |
domscribe.manifest.stats |
Manifest coverage statistics (entry count, file count, component count, cache hit rate) |
domscribe.resolve |
Resolve a data-ds element ID to its source location (file, line, col, component) |
domscribe.resolve.batch |
Resolve multiple element IDs in one call |
domscribe.annotation.process |
Atomically claim the next queued annotation (prevents concurrent agent conflicts) |
domscribe.annotation.respond |
Attach agent response and transition to PROCESSED |
domscribe.annotation.updateStatus |
Manually transition annotation status |
domscribe.annotation.get |
Retrieve annotation by ID |
domscribe.annotation.list |
List annotations with status/filter options |
domscribe.annotation.search |
Full-text search across annotation content |
domscribe.verify.baseline |
Capture a pre-edit style/geometry snapshot of a rendered element |
domscribe.verify.afterEdit |
Compare the element against the baseline — deterministic verdict + per-property deltas |
domscribe.status |
Relay daemon health, manifest stats, queue counts |
See the @domscribe/mcp README for detailed tool schemas, response formats, and prompt definitions.
Packages
| Package | Description |
|---|---|
@domscribe/core |
Zod schemas, RFC 7807 error system, ID generation, PII redaction, constants |
@domscribe/manifest |
Append-only JSONL manifest, IDStabilizer (xxhash64), BatchWriter, ManifestCompactor |
@domscribe/relay |
Fastify HTTP/WS server, MCP stdio adapter, annotation lifecycle |
@domscribe/transform |
Parser-agnostic AST injection (Acorn, Babel, VueSFC), bundler plugins |
@domscribe/runtime |
Browser-side ElementTracker, ContextCapturer, BridgeDispatch |
@domscribe/overlay |
Lit web components (shadow DOM), element picker, annotation UI |
@domscribe/react |
React fiber walking, props/state extraction, Vite + Webpack plugins |
@domscribe/vue |
Vue 3 VNode resolution, Composition + Options API support, Vite + Webpack plugins |
@domscribe/next |
withDomscribe() config wrapper for Next.js 15 + 16 |
@domscribe/nuxt |
Nuxt 3+ module with auto-relay and runtime plugin |
domscribe |
CLI binary (domscribe serve, status, stop, init, mcp) |
@domscribe/mcp |
Standalone MCP server binary (domscribe-mcp) |
@domscribe/test-fixtures |
Black-box integration + e2e suite (not published) |
Contributing
pnpm install
nx run-many -t build test lint typecheck
Conventions are in .claude/rules/. PRs welcome.
For an isolated browser replay check through the Docker Node SDK, see the Docker Cloud replay smoke test.
Portable issue-packet CLI commands are being developed on main; see the source-only handoff guide for availability, privacy options and fresh-checkout inspection.
License
Domscribe MCP questions
What does Domscribe do for AI coding agents?
It bridges a running web app and its source code, letting agents query live DOM, props, and state for a source location or receive annotations from clicking elements in the browser.
How do I set up Domscribe?
Run the init wizard, which connects your coding agent and adds the right package to your app, or follow the manual setup steps.
Does Domscribe affect production builds?
No, all instrumentation is stripped from production builds.
How does Domscribe handle sensitive data?
Emails, tokens, and other sensitive patterns are automatically redacted before data leaves the browser.