Skip to main content
Glama
hal666

vision-mcp

by hal666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to vision-mcp

No user-submitted related servers found.

    Related Servers

    • Vision MCP Server

      itcomgroup
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides free and unlimited vision capabilities for AI coding assistants using the Groq API and Meta Llama 4 Vision model. It enables users to perform image analysis, OCR, UI layout description, and error diagnosis directly from screenshots and documents.
      -

    • llm-vision-mcp

      KuaaMU
      A
      license
      A
      quality
      C
      maintenance
      Gives text-only LLM coding agents vision by routing images to a multimodal model and returning detailed textual descriptions. Supports local files, URLs, clipboard, base64, raw bytes, and multiple providers like OpenAI, Anthropic, and Gemini.
      1
      53 npm
      13
      MIT

    • Luma MCP

      mateuszpanagiotou0628
      A
      license
      Not graded
      quality
      A
      maintenance
      Grants image-understanding capabilities to AI coding assistants that lack native vision by routing screenshots, error messages, UI mockups and documents through a single unified analysis tool. Supports multiple vision model providers such as GLM, DeepSeek-OCR, Qwen-VL, Doubao and Hunyuan, with automatic multi-crop, compression and retry handling for text-dense images.
      866 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely separate purposes: 'vision_see' performs the core image analysis and description, while 'vision_status' checks configuration and clipboard state. There is no overlap or ambiguity in their roles.

    Naming Consistency5/5

    Both tools follow a consistent 'vision_verb' naming pattern: 'vision_see' and 'vision_status'. The prefix establishes the domain clearly, and the verbs are distinct and descriptive.

    Tool Count3/5

    With only 2 tools, the server is on the borderline of being too thin for a typical MCP server. While the two tools cover the essential workflow, the set feels minimal and lacks ancillary tools that might be expected (e.g., configuration or image management).

    Completeness4/5

    The server covers the core use case of analyzing an image and checking readiness. Minor gaps exist (e.g., no explicit error recovery or format listing), but agents can work around these by combining the existing tools or relying on user assistance.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources