FreezeText MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREEZETEXT_API_PORT | No | Port of FreezeText's local HTTP API | 9876 |
| FREEZETEXT_API_TOKEN | No | Bearer token — only if set in FreezeText Settings |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_screenA | Freezes the screen and recognizes text via OCR (Apple Vision). Returns the recognized text from the current screen. |
| capture_regionA | Captures a specific screen region and recognizes its text via OCR. Coordinates in screen points. |
| ocr_imageB | Runs OCR on a provided base64-encoded image (PNG or JPEG) and returns the recognized text. |
| list_historyA | Lists all captured-text history entries (id, text, displayName, timestamp, colorTag). |
| search_historyB | Searches the capture history by text. Optional sorting by date or text. |
| get_history_entryA | Returns a single history entry by its UUID. |
| add_historyC | Adds a text entry to the capture history. |
| delete_history_entryB | Deletes a history entry by its UUID. |
| clear_historyA | Deletes all history entries. |
| export_historyA | Exports the full capture history as JSON or CSV. |
| get_ocr_languagesA | Returns the currently configured OCR recognition languages. |
| set_ocr_languagesC | Sets the OCR recognition languages (e.g. en-US, de-DE). |
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 12 tools
Each tool has a clearly distinct purpose: capture actions (full screen vs region), history management (add, list, get, search, delete, clear, export), direct OCR on images, and language configuration. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., capture_region, clear_history, export_history). There are no deviations or mixed conventions.
With 12 tools covering screen capture, OCR, history management, and language configuration, the count fits the domain well. Each tool serves a necessary function without redundancy.
Core workflows (capture, OCR, history CRUD, export) are covered. The only minor gap is whether capture tools automatically add to history or require explicit add calls, but the set provides all needed operations.