sulus-web-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind host | 0.0.0.0 |
| MCP_PATH | No | Bind path | /mcp |
| MCP_PORT | No | Bind port | 3000 |
| DENY_HOSTS | No | Optional host list to deny | |
| ALLOW_HOSTS | No | Optional host list to allow | |
| MAX_OUTPUT_CHARS | No | Maximum output characters per tool call | 18000 |
| MCP_ALLOWED_HOSTS | No | Allowed Host header values | |
| MCP_SHARED_SECRET | Yes | Bearer token required on /mcp | |
| ALLOW_INSECURE_HTTP | No | Set true only for local http:// testing | |
| NAVIGATION_TIMEOUT_MS | No | Navigation timeout in milliseconds | 25000 |
| RATE_LIMIT_PER_MINUTE | No | Rate limit per bearer token per minute | 30 |
| BROWSER_MAX_CONCURRENT | No | Maximum number of concurrent browser contexts | 3 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browse_pageA | Use this when you need the content of a live public web page. It opens the URL in a headless browser, waits for the document, and returns the title, final URL, and cleaned markdown (or links/title only). Returns extracted text, not a screenshot. Does not log in or fill forms. |
| extract_linksA | Use this when you need outbound links from a public page. It opens the URL and returns unique hrefs with link text. Returns a markdown list. Optionally restrict to the same origin. |
| search_pageA | Use this when you need excerpts matching a query on a public page. It opens the URL, extracts text, and returns up to N case-insensitive snippets around the query. Returns markdown snippets. |
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 3 tools
Each tool has a clearly distinct purpose: browse_page returns page content, extract_links retrieves outbound links, and search_page provides matching snippets. No ambiguity exists between them despite all operating on URLs.
All tool names follow a consistent verb_noun pattern (browse_page, extract_links, search_page) using snake_case. The pattern is predictable and uniform across the three tools.
Three tools is a well-scoped count for a web browsing server. Each tool handles a distinct aspect (content, links, search) and none are redundant or missing for the core functionality.
The tool surface covers the primary browsing capabilities (content extraction, link discovery, and targeted searching). Minor gaps like screenshot capture or form interaction exist, but they are beyond the stated scope and the tools together handle the typical use cases effectively.