MCP Vision Relay
Related Servers
Alternatives to MCP Vision Relay
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides an MCP tool that analyzes images from local paths, URLs, or data URLs via a vision language model, returning structured descriptions (brief, detailed, summary) so text-only LLMs can understand image content.-
- AlicenseNot gradedqualityAmaintenanceProvides a unified image-understanding tool for AI assistants without native vision, letting them analyze screenshots, error messages, UI layouts, and documents via multiple vision LLM providers. It supports local files, remote URLs, Data URIs, OCR, multi-crop processing, and standard MCP clients.866 npmMIT
- AlicenseAqualityCmaintenanceMCP server that exposes an analyze_image tool using Gemini vision models to describe or analyze images from local paths, URLs, or base64 data URIs.19 npmMIT
- AlicenseAqualityCmaintenanceEnables text-only LLMs to analyze images by sending files, URLs, or data URIs to a separate OpenAI-compatible vision model through a single MCP tool.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides multimodal vision MCP tools for image analysis, OCR, object detection, text-to-image generation, and image similarity, integrating OpenAI, Qwen, and Gemini.126 npmMIT
- AlicenseAqualityAmaintenanceWraps OpenAI-compatible text-to-image APIs as MCP tools, enabling image generation directly from conversations in Claude Code, Codex, Cursor, or Claude Desktop using the user's own API key.61Apache 2.0
TDQS
Scored across 2 tools
The two tools are essentially identical in purpose—both describe or analyze images using multimodal capabilities, differing only in the underlying model (Gemini vs. Qwen). An agent would have no clear basis to choose one over the other based on their descriptions, leading to confusion and misselection.
The tool names follow a perfectly consistent pattern: both use a clear 'model_verb_noun' structure (gemini_analyze_image, qwen_analyze_image). This consistency makes it easy to understand what each tool does at a glance.
With only two tools, the server feels thin for a vision-related domain, as it lacks coverage for common operations like image generation, editing, or filtering. The tools are redundant in functionality, making the count seem artificially low for the apparent scope.
The tool surface is severely incomplete for a vision server; it only offers image analysis via two similar models, with no support for tasks like image creation, transformation, or retrieval. This creates significant gaps that will limit agent capabilities in handling broader vision workflows.