browser-ocr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDP_ENDPOINT | No | Chrome DevTools Protocol endpoint URL. Only needed for the browser_ocr tool. |
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 |
|---|---|
| ocr_imageA | Extract text from an image file or URL using local Tesseract.js OCR. No data leaves your machine. Accepts a file path (absolute) or an HTTP URL to the image. |
| browser_ocrA | Take a screenshot of the current browser page (via CDP connection to a shared Chromium instance) and extract all visible text using local OCR. Requires Chromium to be running with --remote-debugging-port=9222. |
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 2 tools
Both tools perform OCR but on clearly distinct inputs: one captures the current browser page via screenshot, the other processes an image file or URL. No ambiguity in their purposes.
Both tools use a consistent snake_case naming pattern with a source prefix (browser_, ocr_) followed by the action (ocr, image). The pattern is straightforward and predictable.
With only 2 tools, the server is lean but covers the core OCR use cases. While slightly below the typical 3-15 range, it feels appropriately scoped for a focused OCR utility.
The two tools cover the primary OCR scenarios: extracting text from the live browser page and from external images. Minor gaps like language configuration or PDF support exist but are not essential for basic usage.