Mcp-DOM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List all recorded browser forensic debugging sessions with metadata, timestamps, and stats. |
| get_sessionA | Retrieve full metadata, capabilities, health status, and statistics for a specific debugging session. |
| export_sessionA | Export a complete recording session as a portable, self-contained JSON bundle. |
| import_sessionB | Import a recording session bundle from raw JSON string. |
| delete_sessionB | Delete a recording session from storage. |
| get_timelineB | Retrieve summary breakdown of events across the session timeline, including event categories and significant milestones. |
| get_eventsC | Query recorded events with filtering by category (DOM, USER, ERROR, CONSOLE, NETWORK, etc.), type, timestamp range, target node, or search query. |
| get_events_aroundA | Retrieve a focused contextual window of events occurring immediately before and after a specific timestamp or event ID. |
| get_dom_stateA | Reconstruct the complete DOM snapshot at an arbitrary timestamp or event ID using checkpoint delta replay. |
| get_dom_nodeB | Inspect detailed properties of a specific DOM node at a given timestamp (tag, attributes, text, parent, children, visibility state). |
| get_dom_subtreeA | Reconstruct and extract the HTML of a specific subtree (e.g. #app or .gpt-panel) at a given timestamp. |
| diff_domA | Compare two DOM states between timestamp T1 and T2 (or event E1 and E2) and return structured additions, removals, moves, attribute, style, and text changes. |
| trace_elementA | Trace the entire chronological lifecycle of a DOM element from creation, mounting, mutations, style changes to unmounting/removal. |
| find_disappearing_elementsC | Automatically scan the session and identify all elements that existed temporarily and were subsequently removed or hidden. |
| why_did_element_disappearA | Forensic root-cause diagnosis for why an injected or existing UI element disappeared. Pinpoints removal mechanism, ancestor container destruction, style changes, and correlated errors/network triggers. |
| get_diagnosticsA | Query recorded console messages, runtime errors, and unhandled promise rejections with stack traces. |
| get_network_eventsA | Query recorded network requests and responses correlated with timing and duration. |
| get_screenshotsA | List visual checkpoints and screenshot checkpoints captured during the recording session. |
| annotate_sessionC | Add an investigative annotation or hypothesis to the session timeline. |
| get_annotationsB | Retrieve all human and AI annotations created for a session. |
| get_recording_healthA | Run an automated integrity audit on a recording session to check sequence monotonicity, missing nodes, and capability health. |
| inspect_live_pageA | Inspect the current live browser page state, including URL, title, viewport dimensions, scroll positions, readyState, active and focused elements. |
| inspect_live_elementA | Deeply inspect a live DOM element on the active browser page by CSS selector, LogicalNodeId, or selectedElementRef, returning bounds, computed styles, visibility, attributes, state, role, aria, and parent context. |
| get_selected_elementA | Retrieve the DOM element visually selected by the user via Ctrl + Shift + Mouse Click in the live browser. |
| start_element_pickerA | Activate the interactive visual element picker mode in the live browser with hover highlighting and click selection. |
| stop_element_pickerA | Deactivate the visual element picker mode in the browser and restore normal cursor and interaction state. |
| capture_page_screenshotA | Capture a screenshot of the visible browser page viewport with temporal, scroll, and viewport metadata. |
| capture_element_screenshotB | Capture an element-specific screenshot bounded to the target element exact geometry and device pixel ratio. |
| interact_with_elementA | Perform an interaction (click, double_click, right_click, hover, focus, blur, type, clear, press_key, select_option, scroll_into_view, scroll) on a live element and return before/after state and effect measurements. |
| start_element_observationB | Start focused continuous recording and observation around a target element and its subtree/ancestors. |
| stop_element_observationA | Stop focused element observation and assemble a complete correlation bundle with mutations, diagnostics, network activity, and root-cause analysis. |
| get_live_dom_snapshotA | Capture the current live virtual DOM state snapshot of the active browser page in HTML or structured JSON format. |
| get_live_dom_subtreeA | Reconstruct and extract the live HTML or node structure of a specific subtree on the active browser page. |
| get_element_visual_stateA | Inspect detailed visual layout, occlusion, clipping, opacity, z-index, and viewport visibility for a live element. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose_disappearing_element | Run an autonomous root-cause investigation on why an injected web element disappeared. |
| compare_dom_states | Perform a structural diff and timeline causality analysis between two timestamps. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IrMaho/Mcp-DOM'
If you have feedback or need assistance with the MCP directory API, please join our Discord server