mcp-vision
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 |
|---|---|
| vision_screenshotB | Take a screenshot and analyze it with Ollama vision model |
| vision_cameraC | Take a photo with camera and analyze it |
| vision_analyze_imageB | Analyze an image file with Ollama vision model |
| helpA | Get comprehensive documentation for all vision functions |
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 4 tools
Each tool targets a distinct input source: screenshot captures the screen, camera captures from a physical camera, and analyze_image works with existing files. The help tool is clearly auxiliary and separate from the vision functions.
Three tools share a 'vision_' prefix, but the structure varies: 'screenshot' and 'camera' are single nouns used as verbs, while 'analyze_image' follows verb_noun. The 'help' tool breaks the prefix pattern entirely, making the naming inconsistent.
With four tools, the server is well-scoped for its purpose. It covers the three primary vision input methods (screen, camera, file) plus documentation, with no redundancy or unnecessary bloat.
The core vision analysis workflows are covered: capturing and analyzing from screen or camera, and analyzing existing images. However, there are minor gaps such as no way to capture an image without analysis, no model management, and no URL-based image input, though these are not critical for the server's stated purpose.