Skip to main content
Glama
di-omics

plr-mcp

by di-omics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to plr-mcp

No user-submitted related servers found.

    Related Servers

    • otie-mcp

      koji
      F
      license
      A
      quality
      C
      maintenance
      MCP server for controlling Opentrons robots (OT-2/Flex) via HTTP API v2 and Python Protocol API, enabling protocol validation, upload and execution, status monitoring, run control, and documentation search.
      6
      -

    • my-mcp-server

      kcbabo
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server built with FastMCP that enables dynamic tool loading and configuration from individual Python files. It provides a flexible framework for automatically discovering, testing, and running tools via Stdio or HTTP transport modes.
      1
      -

    • Device MCP Server

      akshitsinha
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for seamless integration with peripheral devices connected to your computer. Control, monitor, and manage hardware devices through a unified API.
      5
      MIT

    • mhs_demo_server

      sidman76
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes MCP tools to discover and operate simulated lab devices such as incubators and centrifuges, with read/write access, safety-limit enforcement, and interlock logic.
      -

    • hello-world-mcp

      niellevince
      A
      license
      A
      quality
      D
      maintenance
      A simple Model Context Protocol server that provides a hello world greeting tool, serving as a boilerplate template for quickly creating new MCP servers.
      1
      6 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

    A3.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation (aspirate, dispense, transfer, tip handling, deck setup, heater-shaker, thermocycler, plate reader) with no overlaps. Actions are clearly separated.

    Naming Consistency5/5

    All tool names use lower_snake_case with clear verb_noun patterns (e.g., pick_up_tips, drop_tips, read_plate). Naming is uniform and predictable.

    Tool Count5/5

    10 tools cover core liquid handling and lab equipment operations without being excessive. Each tool earns its place for a robotics lab server.

    Completeness4/5

    Covers setup, liquid transfers, tip management, temperature control, and reading. Minor gaps like explicit mixing or pause/move commands exist, but transfer can handle mixing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources