vision-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_IMAGE_MB | No | Maximum allowed image size in MB | 20 |
| OPENROUTER_MODEL | Yes | Model identifier (e.g. google/gemma-4-31b-it:free) | |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key | |
| OPENROUTER_BASE_URL | No | API base URL override | https://openrouter.ai/api/v1 |
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 |
|---|---|
| analyze_imageB | Send an image (URL or local path) with a prompt to a vision model via OpenRouter |
| screenA | Capture a screenshot of an application window by PID or process name (e.g. wezterm) |
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 2 tools
The two tools have clearly distinct purposes: analyze_image sends an image to a vision model, while screen captures a screenshot. No overlap in functionality.
Both tool names follow a simple pattern, but 'screen' is a single noun used as a verb, while 'analyze_image' is verb_noun. The inconsistency is minor given only two tools.
For a vision-related server, two tools are very minimal. Typical vision servers have at least 5-10 tools for different operations (list models, describe, compare, etc.).
The server lacks essential operations like listing available models, configuring parameters, or handling multiple image inputs. The surface is too narrow for a comprehensive vision tool.