mcp-web-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_WEB_AGENT_DATA_DIR | No | Root directory for cache DB and session files. Both the SQLite watch/crawl cache and session state files live under this directory. | <cwd>/.mcp-web-agent |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_scrapeA | Fetch a URL and return clean content — markdown by default, or specific fields via a CSS-selector schema. Tries a plain HTTP fetch first and only launches a browser if the page needs JS to render. |
| web_checkA | Verify something about a page (text present/absent, element present/absent, exact text match) without returning the whole page — just a pass/fail and a short evidence snippet. |
| web_diffB | Check whether a page (or a subtree of it) has changed since the last check. Returns changed=true/false and a short snippet — not the full content — so repeated monitoring stays cheap. |
| web_interactA | Run a sequence of actions (click, fill, select, press, waitFor) on a live page — for testing flows or reaching content behind interaction. Returns a text accessibility snapshot by default; pass screenshot=true only when you actually need to see pixels. |
| web_session_closeA | Delete persisted cookies and storageState for a given sessionId. |
| web_crawlA | Perform a BFS crawl starting at startUrl up to maxDepth/maxPages. Returns page titles, link structures, and excerpts, while caching full markdown for web_crawl_get_page. |
| web_crawl_get_pageB | Fetch cached page content discovered during a web_crawl call. |
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 7 tools
Most tools have distinct purposes: scraping, crawling, interaction, checking, diffing, and session management are clearly separate. However, web_scrape and web_crawl_get_page both return page content (one on-demand, one cached), and web_check vs web_diff both verify page state, creating slight overlap.
All tools share a 'web_' prefix, but the structure varies: mostly verb (web_scrape, web_check, web_interact, web_crawl), but web_session_close is noun-verb and web_crawl_get_page is verb-noun-noun. The pattern is readable but not entirely consistent.
Seven tools is well within the ideal range for a web agent server. Each tool serves a distinct function without redundancy, and the count feels appropriate for the domain of scraping, crawling, interaction, and monitoring.
The set covers core web operations: fetch, crawl, interact, check, diff, and session cleanup. Minor gaps include no explicit session creation tool (though implied by web_interact) and no dedicated screenshot tool (though web_interact supports screenshots). These are workable gaps, not critical failures.