mcp-vision-server
With the mcp-vision-server you can analyze images using various OpenAI-compatible vision models via the analyze_image tool. It provides a unified API to switch between providers (e.g., Zhipu, OpenAI, OpenRouter) without changing client code. Images can be supplied as a URL, local file path, or Base64 string (auto-detected). Configuration settings like provider, base URL, API key, model, temperature, and max tokens are set globally through environment variables or overridden per request. The server integrates with MCP clients such as Claude Code, Codex, Cursor, and Zed.
Click on "Deploy 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-vision-server what's in this image?"
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-vision-server
One MCP server for every OpenAI-compatible vision model.
Configure once and use the same analyze_image tool across OpenAI, OpenRouter, Zhipu, Bailian, SiliconFlow and other compatible providers. It works with Claude Code, Codex, Cursor, Zed and any other MCP client.
Why use mcp-vision-server?
✅ Works with any MCP client – Claude Code, Codex, Cursor, Zed and more.
✅ Works with many providers – switch providers without changing prompts or tool calls.
✅ One unified API – one tool (
analyze_image) for every OpenAI-compatible vision endpoint.✅ Flexible image input – URL, local file or Base64 are detected automatically.
✅ Override anywhere – configure globally with environment variables or per request.
Related MCP server: vision-mcp
Quick Start
Install the server.
Set your provider and API key.
Add the MCP server to your client.
Ask:
Describe this screenshot.If everything is configured correctly, your MCP client will automatically call analyze_image and return the vision model's response.
Features
Single
analyze_imagetool with a consistent interface.Supports URL, local file and Base64 image inputs.
Supports 13 built-in provider presets.
Provider selection via
VISION_PROVIDERor theproviderparameter.Environment-level and request-level configuration overrides.
Example
Ask your MCP client to analyze an image:
Analyze this screenshot and tell me what UI is shown.The client calls the MCP tool:
{
"tool": "analyze_image",
"arguments": {
"image": "/path/to/screenshot.png",
"prompt": "Analyze this screenshot and tell me what UI is shown."
}
}The server normalizes the image input, sends it to the selected OpenAI-compatible vision provider, and returns a plain text answer to your MCP client.
Providers
Built-in presets make common OpenAI-compatible vision endpoints easy to use:
Provider | Preset |
Zhipu |
|
Bailian / DashScope |
|
OpenAI |
|
SiliconFlow |
|
OpenRouter |
|
Ark / Volcengine |
|
StepFun |
|
Kimi / Moonshot |
|
MiniMax |
|
ModelScope |
|
NVIDIA NIM |
|
Novita AI |
|
You can also use any other OpenAI-compatible vision endpoint by setting VISION_BASE_URL, VISION_API_KEY, and VISION_MODEL manually.
Install & Run
Requires Python ≥ 3.10 and uv.
cd mcp-vision-server
uv sync # install deps
uv run pytest -v # run tests
uv run ruff check . # lint
uv run mcp-vision-server # start stdio serverConfiguration
Option 1: Provider preset (recommended)
export VISION_PROVIDER=zhipu # default
export VISION_API_KEY=your_keySee Providers for the full preset list.
You can also use provider-specific env vars (e.g. DASHSCOPE_API_KEY, OPENAI_API_KEY) as fallback.
Option 2: Manual
Variable | Required | Description |
| Yes | API key |
| No | OpenAI-compatible endpoint |
| No | Model name |
Tool params (override env per call): image, prompt, image_type, provider, base_url, api_key, model, temperature, max_tokens.
MCP Client Setup
Claude Code (.mcp.json)
{
"mcpServers": {
"vision": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-vision-server", "mcp-vision-server"],
"env": {
"VISION_PROVIDER": "zhipu",
"VISION_API_KEY": "your_key"
}
}
}
}Claude Code Plugin
# After PyPI publish
claude plugins install RuyimgByCN/mcp-vision-server
# Local test
claude plugins install /path/to/mcp-vision-serverThe repo includes a .claude-plugin.json manifest — claude plugins install reads it automatically.
Codex (OpenAI Codex CLI)
Edit ~/.codex/config.toml:
[mcp_servers.vision]
command = "uvx"
args = ["mcp-vision-server"]
env = { VISION_PROVIDER = "zhipu", VISION_API_KEY = "your_key" }Or for local dev:
[mcp_servers.vision]
command = "uv"
args = ["run", "--directory", "/path/to/mcp-vision-server", "mcp-vision-server"]
env = { VISION_PROVIDER = "zhipu", VISION_API_KEY = "your_key" }Cursor / other uvx clients
Replace command with uvx, args with ["--from", "/path/to/mcp-vision-server", "mcp-vision-server"], same env.
Provider Examples
// Bailian
"env": { "VISION_PROVIDER": "bailian", "VISION_API_KEY": "your_key" }
// OpenAI
"env": { "VISION_PROVIDER": "openai", "VISION_API_KEY": "sk-xxx" }
// Fully custom
"env": {
"VISION_BASE_URL": "https://your-endpoint/v1",
"VISION_API_KEY": "your_key",
"VISION_MODEL": "your-model"
}Architecture
MCP Client (Claude Code / Codex / Cursor / Zed)
│
▼
mcp-vision-server
│
├── mcp_vision_server/server.py # MCP tool entrypoints
├── mcp_vision_server/config.py # env/provider/parameter resolution
├── mcp_vision_server/image.py # URL/file/base64 normalization
└── mcp_vision_server/providers.py # provider presets
│
▼
OpenAI-compatible Vision API
│
▼
Vision model responseFAQ
Why not call the vision provider directly?
This server gives MCP clients a single, reusable vision tool. You can switch providers without changing client prompts, MCP tool names, or client-side integration code.
Can I use a provider that is not listed?
Yes. Use manual configuration with VISION_BASE_URL, VISION_API_KEY, and VISION_MODEL for any OpenAI-compatible vision endpoint.
Can I override the provider per request?
Yes. Use the provider, base_url, api_key, or model tool parameters to override environment-level configuration for a single call.
What image formats are supported?
The server accepts image URLs, local file paths, and Base64 strings. Input type can be auto-detected or specified with image_type.
Development
uv sync --all-groups
uv run ruff check .
uv run ruff format .
uv run pytest -v
uv build
uv run twine check dist/*Release checklist
Update the version in
pyproject.toml.Run
uv run ruff check .,uv run pytest -v,uv build, anduv run twine check dist/*.Create and push a version tag, for example
v0.1.2.Let GitHub Actions publish to PyPI through trusted publishing.
Roadmap
Add more provider presets when stable OpenAI-compatible vision endpoints are available.
Add richer examples for Claude Code, Codex, Cursor, and other MCP clients.
Add optional streaming response support if MCP client UX benefits from it.
Split provider-specific behavior into plugins only when providers require custom request logic.
About
Author: RuyimgByCN
License: Personal use only. Commercial use is prohibited — see LICENSE for details. Contact the author for commercial licensing.
中文说明: 个人使用免费,禁止商用。商业授权请联系作者。详见 README_ZH.md。
Available Tools
2 toolsanalyze_imageB
Analyze or understand an image.
Use this tool when an MCP client needs image understanding, screenshot analysis, OCR-like text recognition, visual Q&A, or UI restoration.
Inputs: image (required), model, prompt, api_key, +5 more. Returns: result
list_providersA
List all supported provider presets as a JSON array.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have entirely distinct purposes: analyze_image for image understanding and list_providers for listing provider presets. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (analyze_image, list_providers), making naming predictable and clear.
Only two tools for a vision server feels slightly thin. While the count is not extreme, it borders on insufficient for typical vision tasks.
The server covers only basic image analysis and a provider listing, missing common vision operations like generation, manipulation, or filtering. The tool surface is significantly incomplete.
Maintenance
Related MCP Connectors
Chat, image, video, and audio models from many vendors behind one remote MCP server and one key.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- FlicenseBqualityDmaintenanceOpenAI-compatible MCP server for running image analysis tools against your own vision model endpoint.717 npm-
- AlicenseAqualityDmaintenanceMCP server that provides an analyze_image tool using OpenAI-compatible vision LLMs to describe images from file paths, URLs, or base64 data.121 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for analyzing images using multiple vision LLM providers (OpenCode, OpenAI, Anthropic, Google, and custom OpenAI-compatible endpoints). Provides tools to analyze single or multiple images, list providers, and test vision capabilities.MIT
- AlicenseAqualityAmaintenanceMCP server that provides vision understanding to non-multimodal agents via 4 tools (analyze/describe/OCR image, list providers), supporting 13 vision providers with automatic fallback and secure URL handling.4281 npmMIT