Skip to main content
Glama
leif-cipriani

nmos-mcp

by leif-cipriani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nmos-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-agent-proxy

      mashh-lab
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that acts as a proxy to connect MCP clients to agent frameworks like Mastra and LangGraph, enabling agent discovery, dynamic server connections, and recursive agent networks.
      5
      41 npm
      10
      MIT

    • OBS MCP Server

      royshil
      A
      license
      B
      quality
      D
      maintenance
      A server that provides tools to control OBS Studio remotely via the OBS WebSocket protocol, enabling management of scenes, sources, streaming, and recording through an MCP client interface.
      100
      306 npm
      137
      GPL 2.0

    • mcp-eveng

      madmickstar
      A
      license
      A
      quality
      B
      maintenance
      MCP server for controlling EVE-NG network emulator instances via REST API, enabling lab/node/network management, topology editing, and device operations through natural language.
      36
      MIT

    • nrs_llm

      eunseopsong
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for ROS 2 environments that connects via rosbridge WebSocket, enabling topic/service introspection, publish/subscribe, service calls, robot connectivity checks, and polishing pipeline operations.
      Apache 2.0

    • ucontrol-mcp

      codefitz
      F
      license
      B
      quality
      D
      maintenance
      MCP server for uControl, enabling read and write operations on schema, assets, and uMap via segregated tools with authentication.
      24
      -

    • quads-mcp

      grafuls
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.
      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

    B3.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct operation (list, get, connect, disconnect, enable, disable, stage, query, registry info) on specific resources (nodes, devices, sources, flows, senders, receivers). No two tools have overlapping functionality; the generic get_resource is clearly a fallback.

    Naming Consistency5/5

    All tools use a consistent verb_noun pattern (e.g., list_devices, connect_sender_to_receiver, disable_sender). Even bulk_connect follows the pattern with a compound verb. No mixing of styles.

    Tool Count4/5

    19 tools is slightly above the typical well-scoped range but still reasonable for an NMOS control server covering multiple resource types (nodes, devices, sources, flows, senders, receivers) and connection management. Each tool serves a clear purpose.

    Completeness4/5

    The tool set covers the core NMOS workflow: discovery, connection management, and transport file retrieval. Minor gaps exist, such as no subscription listing or resource creation, but these are not central to the server's apparent purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources