MCP OpenVision
MCP OpenVision is a server that enables image analysis using OpenRouter's vision models, providing a simple interface for AI assistants to interpret and extract information from images.
Capabilities include:
Image Analysis: Process images from various sources (base64, URLs, local file paths)
Custom Queries: Guide the analysis with specific instructions
System Prompts: Customize the model's behavior for specialized analysis
Model Selection: Choose specific OpenRouter vision models or use defaults
Parameter Control: Adjust generation parameters (temperature, max_tokens, etc.)
Path Support: Use relative or absolute file paths with optional project_root reference
Integration: Works with AI assistants like Claude Desktop or Cursor via MCP configuration
Provides a way for users to support the development of the MCP OpenVision server through donations.
Hosts the project repository and provides integration with GitHub Actions for CI/CD workflows.
Supports OpenAI's vision models (GPT-4o) for analyzing images through the OpenRouter API.
Enables installation of the MCP OpenVision package through the Python Package Index.
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., "@MCP OpenVisionanalyze this product photo and suggest improvements for the lighting"
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.

MCP OpenVision
Overview
MCP OpenVision is a Model Context Protocol (MCP) server that provides image analysis capabilities powered by OpenRouter vision models. It enables AI assistants to analyze images via a simple interface within the MCP ecosystem.
Related MCP server: MCP Read Images
Installation
Installing via Smithery
To install mcp-openvision for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @Nazruden/mcp-openvision --client claudeUsing pip
pip install mcp-openvisionUsing UV (recommended)
uv pip install mcp-openvisionConfiguration
MCP OpenVision requires an OpenRouter API key and can be configured through environment variables:
OPENROUTER_API_KEY (required): Your OpenRouter API key
OPENROUTER_DEFAULT_MODEL (optional): The vision model to use
OpenRouter Vision Models
MCP OpenVision works with any OpenRouter model that supports vision capabilities. The default model is qwen/qwen2.5-vl-32b-instruct:free, but you can specify any other compatible model.
Some popular vision models available through OpenRouter include:
qwen/qwen2.5-vl-32b-instruct:free(default)anthropic/claude-3-5-sonnetanthropic/claude-3-opusanthropic/claude-3-sonnetopenai/gpt-4o
You can specify custom models by setting the OPENROUTER_DEFAULT_MODEL environment variable or by passing the model parameter directly to the image_analysis function.
Usage
Testing with MCP Inspector
The easiest way to test MCP OpenVision is with the MCP Inspector tool:
npx @modelcontextprotocol/inspector uvx mcp-openvisionIntegration with Claude Desktop or Cursor
Edit your MCP configuration file:
Windows:
%USERPROFILE%\.cursor\mcp.jsonmacOS:
~/.cursor/mcp.jsonor~/Library/Application Support/Claude/claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"openvision": {
"command": "uvx",
"args": ["mcp-openvision"],
"env": {
"OPENROUTER_API_KEY": "your_openrouter_api_key_here",
"OPENROUTER_DEFAULT_MODEL": "anthropic/claude-3-sonnet"
}
}
}
}Running Locally for Development
# Set the required API key
export OPENROUTER_API_KEY="your_api_key"
# Run the server module directly
python -m mcp_openvisionFeatures
MCP OpenVision provides the following core tool:
image_analysis: Analyze images with vision models, supporting various parameters:
image: Can be provided as:Base64-encoded image data
Image URL (http/https)
Local file path
query: User instruction for the image analysis tasksystem_prompt: Instructions that define the model's role and behavior (optional)model: Vision model to usetemperature: Controls randomness (0.0-1.0)max_tokens: Maximum response length
Crafting Effective Queries
The query parameter is crucial for getting useful results from the image analysis. A well-crafted query provides context about:
Purpose: Why you're analyzing this image
Focus areas: Specific elements or details to pay attention to
Required information: The type of information you need to extract
Format preferences: How you want the results structured
Examples of Effective Queries
Basic Query | Enhanced Query |
"Describe this image" | "Identify all retail products visible in this store shelf image and estimate their price range" |
"What's in this image?" | "Analyze this medical scan for abnormalities, focusing on the highlighted area and providing possible diagnoses" |
"Analyze this chart" | "Extract the numerical data from this bar chart showing quarterly sales, and identify the key trends from 2022-2023" |
"Read the text" | "Transcribe all visible text in this restaurant menu, preserving the item names, descriptions, and prices" |
By providing context about why you need the analysis and what specific information you're seeking, you help the model focus on relevant details and produce more valuable insights.
Example Usage
# Analyze an image from a URL
result = await image_analysis(
image="https://example.com/image.jpg",
query="Describe this image in detail"
)
# Analyze an image from a local file with a focused query
result = await image_analysis(
image="path/to/local/image.jpg",
query="Identify all traffic signs in this street scene and explain their meanings for a driver education course"
)
# Analyze with a base64-encoded image and a specific analytical purpose
result = await image_analysis(
image="SGVsbG8gV29ybGQ=...", # base64 data
query="Examine this product packaging design and highlight elements that could be improved for better visibility and brand recognition"
)
# Customize the system prompt for specialized analysis
result = await image_analysis(
image="path/to/local/image.jpg",
query="Analyze the composition and artistic techniques used in this painting, focusing on how they create emotional impact",
system_prompt="You are an expert art historian with deep knowledge of painting techniques and art movements. Focus on formal analysis of composition, color, brushwork, and stylistic elements."
)Image Input Types
The image_analysis tool accepts several types of image inputs:
Base64-encoded strings
Image URLs - must start with http:// or https://
File paths:
Absolute paths: full paths starting with / (Unix) or drive letter (Windows)
Relative paths: paths relative to the current working directory
Relative paths with project_root: use the
project_rootparameter to specify a base directory
Using Relative Paths
When using relative file paths (like "examples/image.jpg"), you have two options:
The path must be relative to the current working directory where the server is running
Or, you can specify a
project_rootparameter:
# Example with relative path and project_root
result = await image_analysis(
image="examples/image.jpg",
project_root="/path/to/your/project",
query="What is in this image?"
)This is particularly useful in applications where the current working directory may not be predictable or when you want to reference files using paths relative to a specific directory.
Development
Setup Development Environment
# Clone the repository
git clone https://github.com/modelcontextprotocol/mcp-openvision.git
cd mcp-openvision
# Install development dependencies
pip install -e ".[dev]"Code Formatting
This project uses Black for automatic code formatting. The formatting is enforced through GitHub Actions:
All code pushed to the repository is automatically formatted with Black
For pull requests from repository collaborators, Black formats the code and commits directly to the PR branch
For pull requests from forks, Black creates a new PR with the formatted code that can be merged into the original PR
You can also run Black locally to format your code before committing:
# Format all Python code in the src and tests directories
black src testsRun Tests
pytestRelease Process
This project uses an automated release process:
Update the version in
pyproject.tomlfollowing Semantic Versioning principlesYou can use the helper script:
python scripts/bump_version.py [major|minor|patch]
Update the
CHANGELOG.mdwith details about the new versionThe script also creates a template entry in CHANGELOG.md that you can fill in
Commit and push these changes to the
mainbranchThe GitHub Actions workflow will:
Detect the version change
Automatically create a new GitHub release
Trigger the publishing workflow that publishes to PyPI
This automation helps maintain a consistent release process and ensures that every release is properly versioned and documented.
Support
If you find this project helpful, consider buying me a coffee to support ongoing development and maintenance.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
1 toolimage_analysisA
Analyze an image using OpenRouter's vision capabilities.
This tool allows you to send an image to OpenRouter's vision models for analysis.
You provide a query to guide the analysis and can optionally customize the system prompt
for more control over the model's behavior.
Args:
image: The image as a base64-encoded string, URL, or local file path
query: Text prompt to guide the image analysis. For best results, provide context
about why you're analyzing the image and what specific information you need.
Including details about your purpose and required focus areas leads to more
relevant and useful responses.
system_prompt: Instructions for the model defining its role and behavior
model: The vision model to use (defaults to the value set by OPENROUTER_DEFAULT_MODEL)
max_tokens: Maximum number of tokens in the response (100-4000)
temperature: Temperature parameter for generation (0.0-1.0)
top_p: Optional nucleus sampling parameter (0.0-1.0)
presence_penalty: Optional penalty for new tokens based on presence in text so far (0.0-2.0)
frequency_penalty: Optional penalty for new tokens based on frequency in text so far (0.0-2.0)
project_root: Optional root directory to resolve relative image paths against
Returns:
The analysis result as text
Examples:
Basic usage with a file path:
image_analysis(image="path/to/image.jpg", query="Describe this image in detail")
Basic usage with an image URL:
image_analysis(image="https://example.com/image.jpg", query="Describe this image in detail")
Basic usage with a relative path and project root:
image_analysis(image="examples/image.jpg", project_root="/path/to/project", query="Describe this image in detail")
Usage with a detailed contextual query:
image_analysis(
image="path/to/image.jpg",
query="Analyze this product packaging design for a fitness supplement. Identify all nutritional claims,
certifications, and health icons. Assess the visual hierarchy and how the key selling points
are communicated. This is for a competitive analysis project."
)
Usage with custom system prompt:
image_analysis(
image="path/to/image.jpg",
query="What objects can you see in this image?",
system_prompt="You are an expert at identifying objects in images. Focus on listing all visible objects."
)
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | ||
| query | No | Describe this image in detail | |
| system_prompt | No | You are an expert vision analyzer with exceptional attention to detail. Your purpose is to provide accurate, comprehensive descriptions of images that help AI agents understand visual content they cannot directly perceive. Focus on describing all relevant elements in the image - objects, people, text, colors, spatial relationships, actions, and context. Be precise but concise, organizing information from most to least important. Avoid making assumptions beyond what's visible and clearly indicate any uncertainty. When text appears in images, transcribe it verbatim within quotes. Respond only with factual descriptions without subjective judgments or creative embellishments. Your descriptions should enable an agent to make informed decisions based solely on your analysis. | |
| model | No | ||
| max_tokens | No | ||
| temperature | No | ||
| top_p | No | ||
| presence_penalty | No | ||
| frequency_penalty | No | ||
| project_root | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It explains the core behavior (image analysis via OpenRouter's vision models) and mentions customization options, but doesn't disclose important behavioral traits like rate limits, authentication requirements, error conditions, or what happens with invalid inputs. The examples help but don't cover edge cases.
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 well-structured with clear sections (overview, args, returns, examples) and front-loads the core purpose. While comprehensive, some sentences could be more concise, particularly in the parameter explanations where some details are repeated across multiple examples.
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 complexity (10 parameters, no annotations, no output schema), the description provides substantial context through detailed parameter explanations and multiple examples. However, it lacks information about return format details beyond 'text' and doesn't cover error handling or operational constraints that would be important for a vision analysis tool.
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 description provides extensive parameter documentation beyond the schema, which has 0% description coverage. It explains each parameter's purpose, format requirements (base64, URL, file path), ranges (max_tokens 100-4000), defaults, and provides detailed guidance for the query parameter. This fully compensates for the schema's lack of descriptions.
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 tool 'analyzes an image using OpenRouter's vision capabilities' and specifies it's for sending images to vision models for analysis. It provides a specific verb ('analyze') and resource ('image'), but since there are no sibling tools, it doesn't need to differentiate from alternatives.
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 implied usage through examples showing different scenarios (basic usage, detailed contextual queries, custom system prompts). However, it lacks explicit guidance on when to use this tool versus alternatives or any prerequisites for successful invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'image_analysis' has a clearly defined purpose that cannot be confused with any other tool in this server.
The single tool follows a clear verb_noun pattern ('image_analysis'), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and descriptive.
A single tool is too few for a server named 'MCP OpenVision' that implies broader vision capabilities. While the tool is well-described, the server feels thin and limited in scope, lacking complementary tools like image generation, comparison, or batch processing that would make it more complete.
The server is severely incomplete for a vision domain. It only provides image analysis, missing essential operations like image generation, editing, transformation, or multi-image processing. Agents will hit dead ends when needing to perform common vision tasks beyond analysis.
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
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The OpenRouter MCP server plugs OpenRouter into the AI tools you already use. Once connected, your assistant can pull live OpenRouter data (models, prices, your credits, rankings, and docs) and send quick test messages, all without leaving your editor.
A Model Context Protocol server for Wix AI tools
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA powerful server that integrates the Moondream vision model to enable advanced image analysis, including captioning, object detection, and visual question answering, through the Model Context Protocol, compatible with AI assistants like Claude and Cline.19Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server for analyzing images using OpenRouter vision models, offering capabilities like automatic image resizing, model configuration, and handling custom queries about images.10MIT
- AlicenseAqualityDmaintenanceMCP OpenVision is a Model Context Protocol (MCP) server that provides image analysis capabilities powered by OpenRouter vision models. It enables AI assistants to analyze images via a simple interface within the MCP ecosystem.116MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides multimodal vision tools such as image description, OCR, visual Q&A, and object detection, powered by any vision model via OpenRouter.MIT
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/mikeysrecipes/mcp-openvision'
If you have feedback or need assistance with the MCP directory API, please join our Discord server