Skip to main content
Glama
Sign In
vision-mcp

vision-mcp

by pongsakornp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vision-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • my-own-vision-mcp

      vectorequa
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables text-only AI agents to see images on demand by calling any OpenAI-compatible vision API for OCR, image analysis, structured extraction, image comparison, and GUI screenshot-to-accessibility-tree conversion.
      1
      MIT

    • Hydra Vision MCP

      carlory
      A
      license
      A
      quality
      C
      maintenance
      Connects a text-only coding agent to an OpenAI-compatible vision model so it can analyze images, screenshots, and UI mockups. Provides tools for general image understanding, OCR and code transcription, error-screenshot diagnosis, technical diagram and chart interpretation, UI-to-code/spec generation, and expected-versus-actual UI comparison.
      7
      40 npm
      MIT

    • Atlas Vision MCP

      QuangThai
      A
      license
      A
      quality
      A
      maintenance
      Enables text-only coding agents to analyze local images using a dedicated vision provider, returning markdown and structured JSON evidence for screenshots, diagrams, UI mockups, and error captures.
      11
      90 npm
      11
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly separated by media type: images versus videos. An agent can easily select the right tool based on the file extension or input format, with no meaningful overlap.

    Naming Consistency5/5

    Both tools follow the exact same verb_noun snake_case pattern: analyze_image and analyze_video. The naming is clean, predictable, and immediately signals what each tool does.

    Tool Count4/5

    Two tools is minimal but reasonable for a vision server focused on content description of static and moving media. Each tool earns its place, though the set feels slightly thin compared to broader vision-capable servers.

    Completeness4/5

    The core workflow of analyzing visual media is covered: images and videos both have a dedicated tool. Minor gaps exist, such as no URL-based input and no specialized vision capabilities like OCR or object detection, but these are not clearly implied by the server's stated scope.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources