omni-web-mcp
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pagesA | Returns the live web pages attached to the local hub. Each entry has a clientId, url, title and lastSeenAt. Use the clientId with the other tools to target a specific page. |
| get_dom_treeA | Extracts the visible page as structured data: rendered text, a heading outline, and a numbered list of interactive elements (links, buttons, inputs, selects, contenteditable). Action tools target elements by their numeric id. |
| click_elementA | Performs a real click (focus + click) on the element that get_dom_tree numbered with the given id. Returns the refreshed page state and whether a navigation may have happened. |
| input_textB | Sets the value of an editable element identified by its numeric id, dispatching input/change so modern frameworks react. Optionally submits the surrounding form. |
| scroll_pageA | Scrolls in a direction or to the top/bottom. When an element id is given, scrolls that container instead of the window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: listing available pages, extracting DOM structure, clicking, entering text, and scrolling. Their descriptions explicitly explain how they compose, such as using clientId from list_pages and numeric ids from get_dom_tree.
All tool names follow a consistent snake_case verb_noun pattern: list_pages, get_dom_tree, click_element, input_text, scroll_page. The convention is predictable and readable.
Five tools is well-scoped for a focused browser-interaction server. Each tool earns its place in the inspect-and-act workflow without obvious redundancy.
The core loop of listing pages, inspecting the DOM, clicking, typing, and scrolling is covered. However, there is no tool to open or navigate directly to a URL, close a page, take a screenshot, or wait for async state, which are notable gaps for general web automation.