vision-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | Grok/xAI API key (tried second). At least one API key is required. | |
| GEMINI_API_KEY | No | Gemini API key (tried first). At least one API key is required. | |
| VISION_GROK_MODEL | No | Grok model override. | grok-4-vision |
| VISION_TIMEOUT_MS | No | Per-backend request timeout in milliseconds. | 20000 |
| OPENROUTER_API_KEY | No | OpenRouter key (tried last). At least one API key is required. | |
| VISION_GEMINI_MODEL | No | Gemini model override. | gemini-2.5-flash |
| VISION_OPENROUTER_MODEL | No | OpenRouter model override. | google/gemini-2.5-flash |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_imageA | Analyze an image file (png, jpg, webp, bmp, gif, avif) and return a text description. Use for screenshots, diagrams, UI mockups, photos. Provide an absolute or relative path. |
| analyze_videoA | Analyze a video file (mp4, webm, mov, avi, mkv) by extracting keyframes and describing the content. Requires ffmpeg installed. |
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 are clearly separated by media type: images versus videos. An agent can easily select the right tool based on the file extension or input format, with no meaningful overlap.
Both tools follow the exact same verb_noun snake_case pattern: analyze_image and analyze_video. The naming is clean, predictable, and immediately signals what each tool does.
Two tools is minimal but reasonable for a vision server focused on content description of static and moving media. Each tool earns its place, though the set feels slightly thin compared to broader vision-capable servers.
The core workflow of analyzing visual media is covered: images and videos both have a dedicated tool. Minor gaps exist, such as no URL-based input and no specialized vision capabilities like OCR or object detection, but these are not clearly implied by the server's stated scope.