Vision MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Vision MCP Serverdescribe what's happening in this image: https://example.com/photo.jpg"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Vision MCP Server
Ever wanted to use a model like GLM-4.6 or other great AI models that just don't have vision capabilities? This MCP server solves that problem by adding vision capabilities to any model through OpenRouter's vision models.
The Problem
Some really good AI models don't support vision. You're stuck choosing between your preferred model or vision capabilities. This server bridges that gap by providing seamless vision capabilities through OpenRouter's vision models.
Related MCP server: Vision MCP
The Solution
This MCP server provides a simple analyze_image tool that can:
Analyze images from URLs, file paths, or base64 data
Use any vision model available on OpenRouter (Claude 3.5 Sonnet, GPT-4 Vision, etc.)
Return detailed analysis results
Handle errors gracefully with proper validation
System Requirements
Before installing, make sure you have:
Node.js 18.0.0 or higher (recommended: Node.js 20+)
npm 8.0.0 or higher (comes with Node.js)
Check Your Versions
node --version # Should show v18.0.0 or higher
npm --version # Should show 8.0.0 or higherInstall/Update Node.js
If you need to install or update Node.js:
Download from official site: nodejs.org (recommended for beginners)
Using Node Version Manager (nvm):
# Install nvm first, then: nvm install 20 nvm use 20Using package managers:
macOS:
brew install nodeWindows:
winget install OpenJS.NodeJSUbuntu/Debian:
sudo apt install nodejs npm
Important: This server is written in TypeScript and uses dependencies (like
node-fetchv3) that require Node.js 18+. Older versions (like Node.js 16 or below) will not work.
Quick Start
Step 1: Get Your OpenRouter API Key
Go to OpenRouter
Sign up or log in to your account
Navigate to "Keys" in your dashboard
Click "Create Key"
Copy your API key (starts with
sk-or-v1-...)Keep this key safe - you'll need it in Step 3
Step 2: Install the MCP Server
Option A: Install from npm (Recommended)
npm install -g @thenomadinorbit/vision-mcp-serverSuccess! The package is now globally available as
vision-mcpcommand.
Option B: Install from Source (Development)
git clone https://github.com/TheNomadInOrbit/vision-mcp-server.git
cd vision-mcp-server
npm install
npm run build
npm install -g .Note: Use this method if you want to modify the source code or contribute to the project.
Step 3: Configure Your MCP Client
Add this server configuration to your MCP client:
{
"mcpServers": {
"vision-analyzer": {
"command": "vision-mcp",
"type": "stdio",
"timeout": 60,
"disabled": false,
"autoApprove": [],
"env": {
"OPENROUTER_API_KEY": "your_api_key_here",
"OPENROUTER_MODEL": "anthropic/claude-3-5-sonnet"
}
}
}
}Step 4: Test Your Installation
Important: The vision-mcp command requires an OpenRouter API key to run. You cannot test it directly without configuration.
Quick Test (with your API key):
OPENROUTER_API_KEY="your_api_key_here" vision-mcp --helpYou should see the server start up with logs like:
Application initialized successfully
Starting Vision MCP Server...
MCP server started successfully
Vision MCP Server is running on stdioPress Ctrl+C to stop the test.
What happens if you run vision-mcp without the API key?
vision-mcpYou'll get this error (this is normal and expected):
Error: OPENROUTER_API_KEY environment variable is requiredThis means the installation worked! The server is just protecting you from running without proper configuration.
Verify Installation Status:
# Check if the command is available
which vision-mcp
# Check if the package is installed
npm list -g @thenomadinorbit/vision-mcp-serverš§ Configuration Options
Basic Configuration
"vision-analyzer"- Server name (you can change this to anything you like)"command": "vision-mcp"- Required: The global command to run the server"type": "stdio"- Required: Communication protocol for MCP"timeout": 60- Optional: Timeout in seconds (default: 60)"disabled": false- Optional: Set totrueto disable the server
Auto-Approve Settings
Configure which tools can run without asking for permission:
"autoApprove": []Options:
[](empty) - Requires approval for all tools (safest)["list_models"]- Auto-approve listing available models only["analyze_image"]- Auto-approve vision analysis (convenient but less safe)["analyze_image", "list_models"]- Auto-approve all tools (most convenient)
Model Configuration
You can use any vision model from OpenRouter:
"env": {
"OPENROUTER_API_KEY": "your_api_key_here",
"OPENROUTER_MODEL": "anthropic/claude-3-5-sonnet"
}Popular Models:
anthropic/claude-3.5-sonnet(recommended - best for vision)openai/gpt-4o-2024-08-06(excellent vision capabilities)google/gemini-2.0-flash-001(fast and cost-effective)anthropic/claude-3-opus(most powerful for complex analysis)
Complete Example Configuration
{
"mcpServers": {
"vision-analyzer": {
"command": "vision-mcp",
"type": "stdio",
"timeout": 60,
"disabled": false,
"autoApprove": ["list_models"],
"env": {
"OPENROUTER_API_KEY": "sk-or-v1-your-actual-key-here",
"OPENROUTER_MODEL": "anthropic/claude-3.5-sonnet",
"MAX_IMAGE_SIZE": "10485760"
}
}
}
}Available Tools
Once configured, your AI assistant can use these tools:
analyze_image
Analyze images with AI vision models
Input: Image URL, file path, or base64 data
Output: Detailed analysis of the image content
list_models
List all available vision models from OpenRouter
Input: None
Output: Array of available models with their capabilities
Usage Examples
Once configured, you can ask your AI assistant to analyze images like this:
Real-World Example
You: "Can you analyze this image: https://example.com/image.jpg"
What happens behind the scenes:
Your AI assistant receives your request
It calls the
analyze_imagetool from this MCP serverThis server downloads the image and sends it to OpenRouter's vision model
The vision model analyzes the image
Results are returned to your AI assistant
Your AI assistant presents the analysis to you
You see: Detailed image analysis from your AI assistant You don't see: All the technical MCP communication happening behind the scenes
Example Conversations
Analyze an image from URL:
"Can you analyze this image: https://example.com/image.jpg"
Analyze a local image:
"Please analyze the image at /Users/username/Pictures/photo.png"
Get available models:
"What vision models are available?"
Detailed analysis:
"Analyze this image and tell me about the objects, colors, and mood: https://example.com/artwork.jpg"
Compare images:
"Can you analyze these two images and tell me the differences: image1.jpg and image2.jpg"
Environment Variables
You can customize the server with these environment variables:
Variable | Description | Default | Required |
| Your OpenRouter API key | - | Yes |
| AI model to use |
| No |
| Max image size in bytes |
| No |
Troubleshooting
Common Mistakes
"I installed it but vision-mcp gives an error!"
The Error:
Error: OPENROUTER_API_KEY environment variable is requiredWhy this happens: You're trying to run vision-mcp directly from the command line. This MCP server is designed to be used through an MCP client (like Claude Code), not run directly.
The Fix:
Correct: Configure it in your MCP client (Step 3 above)
Incorrect: Running
vision-mcpdirectly in terminal
Quick test only: If you want to test the installation, use:
OPENROUTER_API_KEY="your_key" vision-mcp --help"How do I actually use this?"
This server doesn't have a web interface or CLI commands. It's an MCP server that adds vision capabilities to your AI assistant through the MCP protocol.
Workflow:
Install the server globally (
npm install -g @thenomadinorbit/vision-mcp-server)Configure it in your MCP client (Claude Desktop, etc.)
Ask your AI assistant to analyze images
The AI assistant uses this server behind the scenes
Command not found: vision-mcp
For npm installation: Make sure you ran
npm install -g @thenomadinorbit/vision-mcp-serverFor source installation: Make sure you ran
npm install -g .after buildingTry running
npm list -g @thenomadinorbit/vision-mcp-serverto verify installationRestart your terminal
"Server not found" or "Connection failed"
Verify the command is
vision-mcp(not a file path)Make sure you ran
npm run buildCheck that the global installation worked:
which vision-mcpRestart your MCP client
"API key invalid"
Double-check your OpenRouter API key
Make sure it starts with
sk-or-v1-Verify you have credits in your OpenRouter account
"Vision analysis failed"
Try with a smaller image (under 10MB)
Make sure the image format is supported (JPG, PNG, WebP)
Check your OpenRouter account has sufficient credits
Still not working?
Check your MCP client logs for error messages
Make sure your configuration file has valid JSON syntax
Try restarting your computer
Reporting Issues
Found a bug or have a suggestion? Feel free to open an issue with:
Clear description of the problem
Steps to reproduce
Expected vs actual behavior
Your environment details (Node.js version, OS, etc.)
Development Setup
If you want to fork and modify for your own use:
git clone https://github.com/TheNomadInOrbit/vision-mcp-server.git
cd vision-mcp-server
npm install
npm run buildSecurity
If you discover a security vulnerability, please open a security issue with the "security" label.
Changelog
See CHANGELOG.md for a detailed history of changes.
License
MIT - Use it however you want.
Available Tools
2 toolsanalyze_imageC
Analyze an image using AI vision models. Supports file paths and URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | Image source: file path or URL | |
| model | No | AI model to use for analysis (optional, uses Claude 3.5 Sonnet if not specified). You can use any model available on OpenRouter. | |
| prompt | No | Custom analysis prompt (optional, uses default if not specified) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'AI vision models' and support for file paths/URLs but lacks details on permissions, rate limits, output format, or error handling. This is inadequate for a tool with potential complexity in AI analysis.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences that directly state the tool's function and input support. There is no wasted language, and it's front-loaded with the core purpose, making it efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of AI image analysis, no annotations, and no output schema, the description is insufficient. It doesn't explain what the analysis entails, the types of results returned, or any behavioral traits, leaving significant gaps for the agent to understand the tool's full context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning 'file paths and URLs' for the source parameter, but doesn't provide additional context beyond what's in the schema, meeting the baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Analyze an image') and the method ('using AI vision models'), which is specific and understandable. However, it doesn't differentiate from its sibling tool 'list_models', which appears to be a different function entirely, so it doesn't fully address sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives or in what context. It mentions support for 'file paths and URLs' but doesn't specify scenarios or prerequisites for usage, leaving the agent with minimal direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_modelsB
Get list of available AI vision models for vision analysis
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool's function but fails to describe traits like whether it's read-only, has rate limits, requires authentication, or what the return format looks like (e.g., list structure, pagination). This leaves significant gaps for an agent to understand how to interact with it effectively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words or fluff. It is front-loaded and appropriately sized for a simple tool with no parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (0 parameters, no output schema), the description is minimally adequate but incomplete. It lacks behavioral context (e.g., read-only nature, response format) and usage guidelines relative to the sibling tool, which are important for an agent to operate correctly in this context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't add parameter details, aligning with the schema's completeness, which justifies a baseline score of 4 for this dimension.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get list') and resource ('available AI vision models for vision analysis'), making the purpose evident. However, it doesn't explicitly differentiate from the sibling tool 'analyze_image', which appears to be for performing analysis rather than listing models.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the sibling 'analyze_image' or any alternatives. The description implies usage for obtaining model information but lacks context on prerequisites, timing, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
v1.0.4- First observed
analyze_image - First observed
list_models
TDQS
The two tools have clearly distinct purposes: analyze_image performs image analysis using vision models, while list_models retrieves available models. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun pattern (analyze_image, list_models) with clear, descriptive names that align well with their functions. The naming is uniform and predictable.
With only 2 tools, the server feels thin for a vision analysis domain. While it covers basic analysis and model listing, typical vision servers might include additional operations like batch processing, model details, or image preprocessing, making this count borderline minimal.
The tool surface is severely incomplete for vision analysis. It lacks essential operations such as getting model details, preprocessing images, batch analysis, or managing analysis results, which could lead to agent failures in complex workflows.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Analyze images and videos with Gemini to get fast, reliable visual insights. Handle content from Uā¦
Video, audio, and image processing for AI agents: convert, transcribe, upscale - 150+ operations.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Related MCP Servers
- FlicenseCqualityDmaintenanceEnables image captioning and analysis through natural language by processing images from URLs or local files. Supports both OpenRouter's Gemini 2.5 Flash and local vision models for generating concise, descriptive captions.4-
- AlicenseAqualityDmaintenanceEnables image analysis and understanding using Vision Language Models through OpenAI-compatible APIs. Supports analyzing images from URLs or local files with custom prompts.12MIT
- AlicenseNot gradedqualityDmaintenanceEnables text-only LLMs to analyze images by routing them to an OpenAI-compatible vision backend, supporting local files, URLs, and data URLs.26MIT
- AlicenseAqualityCmaintenanceEnables image analysis using any OpenAI-compatible vision API, supporting URLs, local files, or base64 input with custom prompts.1MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheNomadInOrbit/Vision-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server