MCP Screen Text
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| capture_screenC | Captures a screenshot of the specified display |
| capture_application_screenC | Captures a screenshot of a specific application window |
| list_applicationsB | Lists all running applications that can be captured |
| extract_textC | Extracts text from an image using OCR |
| capture_screen_and_extract_textA | Captures a screenshot and extracts text from it in one operation. Can capture full screen or a specific application window. |
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 5 tools
Multiple tools have overlapping purposes that could cause confusion. For example, capture_application_screen and capture_screen_and_extract_text both handle application window screenshots, while capture_screen and capture_screen_and_extract_text both handle full-screen captures. The descriptions help somewhat, but the boundaries between tools are unclear, especially for agents trying to choose between similar options.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., capture_screen, extract_text, list_applications). There are no deviations in naming style, making the set predictable and easy to parse programmatically.
With 5 tools, the count is well-scoped for a screen text capture domain, though it feels slightly thin. Each tool appears to serve a purpose, but the overlap suggests some tools could be consolidated, making the count borderline but still reasonable for the server's functionality.
The tool set covers core operations like capturing screens, extracting text, and listing applications, but there are notable gaps. For instance, there's no way to manage or delete captured images, and the OCR functionality is split across tools without clear update or configuration options, which could lead to agent workarounds for full lifecycle handling.