PeepIt MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Your OpenAI API key for using OpenAI vision models | |
| PEEPIT_CLI_PATH | No | Custom path to the Swift peepit CLI binary | |
| PEEPIT_LOG_FILE | No | Path to log file. If the directory isn't writable, PeepIt uses a temp folder | ~/Library/Logs/peepit-mcp.log |
| PEEPIT_LOG_LEVEL | No | Logging level: trace, debug, info, warn, error, or fatal | info |
| PEEPIT_CLI_TIMEOUT | No | Timeout for Swift CLI operations in milliseconds | 30000 |
| PEEPIT_AI_PROVIDERS | No | Comma or semicolon-separated list of AI providers for image analysis (e.g., 'openai/gpt-4o,ollama/llava:latest') | |
| PEEPIT_CONSOLE_LOGGING | No | Enable console logging. Set to 'true' to enable | false |
| PEEPIT_OLLAMA_BASE_URL | No | Base URL for Ollama API if not running at the default location | http://localhost:11434 |
| PEEPIT_DEFAULT_SAVE_PATH | No | Default directory for screenshots when no path is specified |
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 |
|---|---|
| imageA | Captures macOS screen content and optionally analyzes it. Targets can be entire screen, specific app window, or all windows of an app (via app_target). Supports foreground/background capture. Output via file path or inline Base64 data (format: "data"). If a question is provided, image is analyzed by an AI model (auto-selected from PEEPIT_AI_PROVIDERS). Window shadows/frames excluded. PeepIt MCP 1.0.0-beta.1 using openai/gpt-4o, ollama/llava:latest |
| analyzeA | Analyzes a pre-existing image file from the local filesystem using a configured AI model. This tool is useful when an image already exists (e.g., previously captured, downloaded, or generated) and you need to understand its content, extract text, or answer specific questions about it. Capabilities:
Example: If you have an image '/tmp/chart.png' showing a bar chart, you could ask: { "image_path": "/tmp/chart.png", "question": "Which category has the highest value in this bar chart?" } The AI will analyze the image and attempt to answer your question based on its visual content. PeepIt MCP 1.0.0-beta.1 using openai/gpt-4o, ollama/llava:latest |
| listA | Lists various system items on macOS, providing situational awareness. Capabilities:
Use Cases:
|
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
The three tools have clearly distinct purposes with no overlap: 'analyze' processes existing image files, 'image' captures macOS screens and optionally analyzes them, and 'list' provides system information. Each tool targets a different primary function (file analysis, screen capture, system listing), making them easily distinguishable.
All tool names follow a consistent, simple verb-based pattern: 'analyze', 'image', and 'list'. While 'image' is a noun rather than a verb, it functions as a clear action (capture image) and maintains a uniform, concise naming style across the set without mixing conventions.
With only 3 tools, the count is well-scoped for the server's purpose of macOS screen interaction and analysis. Each tool serves a distinct, essential function: listing system items for awareness, capturing screens, and analyzing images, covering the core workflow without unnecessary bloat.
The tool set covers the primary workflows for macOS screen automation: listing applications/windows, capturing screens, and analyzing images. A minor gap exists in lacking tools for direct interaction with windows (e.g., focus, resize) or file management, but agents can work around this using the provided tools for basic automation tasks.