Skip to main content
Glama
royerlab

Napari MCP Server

by royerlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Napari MCP Server

No user-submitted related servers found.

    Related Servers

    • visual-understanding

      JayceVane
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for multimodal understanding and object grounding (bounding boxes) across images, videos, and documents, with support for multiple AI providers (Zhipu GLM-V, OpenAI GPT-4o, Anthropic Claude, or any OpenAI-compatible endpoint).
      1
      MIT

    • vision-mcp

      nikkoxgonzales
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives Claude and other clients vision capabilities including screenshot-to-code, OCR, error diagnosis, diagram analysis, data-viz insights, UI diff checks, and video analysis via any OpenAI-compatible vision endpoint.
      32,458 npm
      Apache 2.0

    • GPT Maps

      SiddharthGoel-07
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables LLMs to create and control interactive MapLibre maps by placing markers, drawing paths, and rendering polygons directly in Claude Desktop.
      -
    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.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct operation or query. Add/remove/reorder layers are clearly separate; set_layer_properties and apply_to_layers differ in scope; execute_code and read_output serve different purposes. No overlapping tools.

    Naming Consistency5/5

    All tools use consistent snake_case with a verb_noun pattern (e.g., add_layer, list_layers, close_viewer). No mixed conventions or irregular naming.

    Tool Count5/5

    16 tools is well-scoped for the napari viewer domain. Each tool serves a clear purpose without redundancy or unnecessary sprawl.

    Completeness4/5

    Core workflows (viewer lifecycle, layer manipulation, data I/O, code execution) are covered. Minor gaps exist, such as no dedicated file import for non-image layers, but these can be addressed via execute_code.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources