Skip to main content
Glama
MikeyBeez

mcp-vision

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-vision

No user-submitted related servers found.

    Related Servers

    • ollama-vision-mcp

      ducnm9
      F
      license
      A
      quality
      C
      maintenance
      MCP server enabling LLM clients without vision capability to process images by delegating to local Ollama vision models. Supports describing images, OCR, asking questions, and processing clipboard images.
      4
      -

    • local-vision-mcp

      tmchao7
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local Ollama vision analysis, enabling text-only agents like Claude Code to inspect images via a single tool. Processes images locally with Ollama, keeping image bytes on the machine and returning text reports.
      2
      MIT

    • pic-id-mcp

      HaoyueQin
      A
      license
      Not graded
      quality
      A
      maintenance
      Local vision-capable MCP server that lets AI agents describe screenshots, UI, charts, and photos via vision and OCR tools, with support for multiple providers and automatic fallback.
      6
      MIT

    • llm-vision-mcp

      ghbalf
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables any LLM to describe images from file paths, URLs, or base64 data by forwarding them to a supported vision provider such as OpenAI, Anthropic, or local Ollama models.
      844 npm
      10
      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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct input source: screenshot captures the screen, camera captures from a physical camera, and analyze_image works with existing files. The help tool is clearly auxiliary and separate from the vision functions.

    Naming Consistency3/5

    Three tools share a 'vision_' prefix, but the structure varies: 'screenshot' and 'camera' are single nouns used as verbs, while 'analyze_image' follows verb_noun. The 'help' tool breaks the prefix pattern entirely, making the naming inconsistent.

    Tool Count5/5

    With four tools, the server is well-scoped for its purpose. It covers the three primary vision input methods (screen, camera, file) plus documentation, with no redundancy or unnecessary bloat.

    Completeness4/5

    The core vision analysis workflows are covered: capturing and analyzing from screen or camera, and analyzing existing images. However, there are minor gaps such as no way to capture an image without analysis, no model management, and no URL-based image input, though these are not critical for the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources