Auto-Snap MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISPLAY | No | X11 display to use for capturing | :0 |
| AUTO_SNAP_OUTPUT_DIR | No | Custom directory for saving captured files | $HOME/auto-snap-captures |
| AUTO_SNAP_USE_DATE_SUBDIRS | No | Organize captures by date in subdirectories | false |
| AUTO_SNAP_INCLUDE_TIMESTAMP | No | Include timestamp in filenames | false |
| AUTO_SNAP_FILE_NAME_TEMPLATE | No | Custom template for file naming | doc_{page:04d} |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_windowsA | |
| capture_windowA | |
| capture_full_screenB | |
| capture_document_pagesA | |
| process_imagesC | |
| convert_to_pdfA | |
| directory_to_pdfB | |
| full_document_workflowB | |
| check_system_dependenciesB | |
| debug_window_detectionB | |
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 10 tools
Most tools have distinct purposes, but there is some overlap between capture_document_pages and full_document_workflow, as the latter encompasses the former's functionality. Similarly, convert_to_pdf and directory_to_pdf both handle PDF conversion, though with different input sources. The descriptions help clarify these distinctions, but an agent might occasionally misselect between these pairs.
All tool names follow a consistent verb_noun pattern using snake_case, such as capture_window, list_windows, and process_images. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the server.
With 10 tools, the server is well-scoped for document capture and processing workflows. Each tool serves a clear purpose, from window listing and capture to image processing and PDF conversion, without unnecessary redundancy or gaps, making the count appropriate for the domain.
The tool set covers core workflows for document capture, processing, and PDF conversion comprehensively, including dependencies and debugging. However, there is a minor gap in direct OCR or text extraction tools, as process_images includes OCR but lacks standalone options, which might require workarounds for specific tasks.