MCP Servers / development / Domscribe

Domscribe

JSON →
stdionone168development

Build-time DOM-to-source mapping for coding agents

Install
How to run this server
[ { "cmd": "npx domscribe", "imports": [] } ]
server path: domscribe
Tools
What this server exposes
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.status
Relay daemon health, manifest stats, queue counts
Configuration
Environment & auth
authnone
Resources
Domscribe — MCP Server · libregistry