Domscribe MCP server
2026년 11월 14일 커밋AI 코딩 에이전트가 실행 중인 웹 앱의 live DOM, props, state를 검사하고 브라우저 요소를 정확한 소스 파일 및 라인으로 매핑할 수 있게 합니다.
다른 이름 patchorbit/domscribe
- 스타
- 195
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
Domscribe MCP란?
Domscribe은(는) MCP server입니다. AI 코딩 에이전트가 실행 중인 웹 앱의 live DOM, props, state를 검사하고 브라우저 요소를 정확한 소스 파일 및 라인으로 매핑할 수 있게 합니다.
프로젝트 README에서 생성된 요약
Domscribe MCP server 정보
Domscribe는 AI 코딩 에이전트를 실행 중인 웹 애플리케이션의 live state에 연결합니다. 에이전트에게 DOM, 컴포넌트 props, 내부 state에 대한 가시성을 제공함으로써 개발자가 소스 코드와 브라우저 사이의 간극을 메울 수 있도록 돕습니다. 이는 빌드 타임에 안정적인 ID를 사용하고 런타임 심층 검사를 수행하여 브라우저 요소를 저장소의 특정 파일 및 라인 번호로 직접 매핑하는 방식으로 작동합니다.
이를 사용하려면 React, Vue, Next.js 또는 Nuxt와 같이 사용하는 스택에 맞는 프레임워크 패키지를 설치하고 Vite, Webpack 또는 Turbopack과 같은 번들러에 통합해야 합니다. 앱 측 설정이 완료되면 제공된 플러그인을 사용하여 Claude Code, GitHub Copilot, Gemini 또는 Kiro와 같은 MCP 호환 에이전트를 연결합니다. 이 시스템은 로컬 개발을 위해 설계되었으며, 토큰이나 이메일과 같은 민감한 데이터가 에이전트로 전송되기 전에 삭제되도록 자동 PII 비식별 처리를 포함합니다.
활용 사례
- 1실시간 컴포넌트 state 검사실행 중인 브라우저에서 특정 컴포넌트의 현재 props와 state를 확인하도록 에이전트에게 요청하십시오.
- 2클릭을 통한 UI 변경 구현브라우저 오버레이에서 요소를 가리키고 에이전트에게 해당 요소의 외형이나 동작을 수정하도록 지시하십시오.
- 3CSS 및 속성 디버깅코드 수정을 시도하기 전에 에이전트에게 live 요소의 특정 CSS 클래스나 속성을 확인하도록 지시하십시오.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능patchorbit/domscribe is public and reachablegithub.com/patchorbit/domscribe ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-01github.com/patchorbit/domscribe ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기AI 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 질문
Domscribe가 AI 코딩 에이전트에게 제공하는 기능은 무엇인가요?
실행 중인 웹 앱과 소스 코드를 연결하여, 에이전트가 live DOM, props, state를 쿼리해 소스 위치를 찾거나 브라우저에서 요소를 클릭하여 주석을 받을 수 있도록 합니다.
Domscribe를 어떻게 설정하나요?
init wizard를 실행하여 코딩 에이전트를 연결하고 앱에 적절한 패키지를 추가하거나, 수동 설정 단계를 따르십시오.
Domscribe가 프로덕션 빌드에 영향을 미치나요?
아니요, 모든 인스트루멘테이션은 프로덕션 빌드에서 제거됩니다.
Domscribe는 민감한 데이터를 어떻게 처리하나요?
이메일, 토큰 및 기타 민감한 패턴은 데이터가 브라우저를 떠나기 전에 자동으로 비식별 처리됩니다.