obscura-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSCURA_PATH | No | Path to custom Obscura binary | |
| MCP_HTTP_HOST | No | HTTP transport host | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP transport port | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio or streamable-http | stdio |
| CDP_REQUEST_TIMEOUT_MS | No | Milliseconds to wait for CDP response | 10000 |
| OBSCURA_NAVIGATION_WAIT_MS | No | Milliseconds to wait after page navigation | 3000 |
| OBSCURA_STARTUP_TIMEOUT_MS | No | Milliseconds to wait for Obscura CDP to start | 15000 |
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_urlA | Fetch a URL using Obscura's lightweight CDP engine. To access authenticated pages, pass cookies previously exported from browse_cookies. |
| browse_evaluateA | Navigate to a URL and execute JavaScript in the page context. Returns the evaluated result as a string. Supports extracting data, clicking elements, filling forms, and reading page state. |
| browse_cookiesA | Navigate to a URL and retrieve all cookies set by the page. Returns cookie name, value, domain, path, and expiry for each cookie. |
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 serves a distinct purpose: retrieving cookies, executing JavaScript, and fetching a URL. There is no ambiguity between the three operations.
All tool names follow the consistent pattern 'browse_<operation>', using snake_case and a common prefix, ensuring predictability.
With only 3 tools, the surface is thin for a browser automation server. It covers basic actions but feels minimal, so it is borderline appropriate.
The set covers URL fetching, cookie extraction, and JS execution, but lacks direct interaction tools (e.g., clicking, form filling, waiting). Workarounds are possible via JS, but gaps exist.