visionMCP
Enables any MCP-capable agent to perform vision tasks like describing images, answering questions, OCR, and comparing images using supported vision backends.
README
visionMCP 👁️
The eyes of a bigger reasoning LLM.
visionMCP is a Model Context Protocol server that
gives any MCP-capable agent real vision. A text-only reasoning model can delegate
anything it cannot see to this server: describe a screenshot, answer a question about a
photo, OCR a document, or compare two images — the server does the seeing and hands back
text.
It works with all three major vision backends, chosen at runtime from a single
config.json:
| Provider | API | Example models |
|---|---|---|
| Ollama | OpenAI-compatible (http://localhost:11434/v1) |
llama3.2-vision, qwen2.5vl, llava |
| OpenAI | Chat Completions vision API | gpt-4o, gpt-4o-mini |
| Anthropic | Claude Messages vision API | claude-3-5-sonnet-latest, claude-3-7-sonnet-latest |
Features
- 🔍 Four vision tools for a reasoning LLM to call:
describe_image— full natural-language descriptionask_about_image— targeted Q&A about any imageextract_text— OCR / transcriptioncompare_images— side-by-side comparison
- 🖼️ Every source accepted: local file paths,
http(s)URLs, and base64data:URIs. - 📦 Zero image prep: oversized images are auto-downscaled and re-encoded as JPEG to fit provider payload limits.
- 🔌 Three transports:
stdio(default, for local MCP clients),http(Streamable HTTP for remote hosting), orsse(legacy Server-Sent Events). - ⚙️ One
config.jsoncontrols provider, API key, API URL, and model. Environment variables and CLI flags can override anything. - 🚀
uv-managed, installable, runnable, and hostable.
Quick start
1. Install
Requires uv and Python ≥ 3.10.
cd visionMCP
uv sync
2. Configure
The shipped config.json already works with a local Ollama. Switch providers by
editing the file:
// config.json
{
"provider": "openai", // "ollama" | "openai" | "anthropic"
"api_key": "sk-...", // or leave "" and export OPENAI_API_KEY
"api_url": "", // "" = provider default
"model": "" // "" = provider default
}
See docs/configuration.md for every option, and docs/providers.md for per-provider setup.
Security: keep real API keys out of git — copy
config.jsontoconfig.local.json(auto-ignored) or use environment variables. The server never logs your key.
3. Run
uv run vision-mcp # stdio transport (default)
uv run vision-mcp --transport http --host 0.0.0.0 --port 8100 # host remotely
uv run vision-mcp --show-config # print resolved config (key masked)
Wiring into an MCP client
opencode (opencode.json)
{
"mcpServers": {
"visionMCP": {
"type": "stdio",
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/visionMCP", "vision-mcp"]
}
}
}
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"visionMCP": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/visionMCP", "vision-mcp"]
}
}
}
Generic MCP client (stdio)
{
"mcpServers": {
"visionMCP": {
"command": "/path/to/visionMCP/.venv/bin/vision-mcp",
"args": ["--config", "/path/to/visionMCP/config.json"]
}
}
}
The server never sends image content to the vision API beyond what the tool call provides. Image bytes are kept in memory and never written to disk.
Tools reference
| Tool | Arguments | Returns |
|---|---|---|
describe_image |
image (path/URL/data-URI) |
Full description in plain text |
ask_about_image |
image, question |
Focused answer |
extract_text |
image |
Transcribed / OCR'd text |
compare_images |
image_a, image_b, optional question |
Comparison in plain text |
server_status |
— | Provider, model, transport |
An image argument accepts any of:
/path/to/photo.png # local file
https://example.com/x.jpg # URL (downloaded at call time)
data:image/png;base64,iVBORw0KGgo... # base64 data URI
How it works
Everything funnels through one function in src/vision_mcp/pipeline.py:
image (path / URL / data URI) → base64 + mime → vision model → text
_read() _encode() API[provider] look()
The server tools are thin wrappers: pipeline.look(cfg, [image], prompt).
Documentation
- Configuration reference — every config option, env var, and precedence rules
- Provider setup — Ollama, OpenAI, and Anthropic, step by step
- Deployment — hosting over HTTP/SSE, Docker, hardening
Development
uv sync --group dev
uv run ruff check .
uv run pytest
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。