Skip to main content
Glama
Nescript

rm_mcp

by Nescript
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rm_mcp

No user-submitted related servers found.

    Related Servers

    • ros-mcp

      husain-zaidi
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for ROS 2 that enables GitHub Copilot and other AI agents to interact with ROS 2 systems. This server provides tools for monitoring, debugging, and managing ROS 2 nodes, topics, services, and TF2 frames.
      15
      80
      MIT

    • ros2-mcp

      ai2robot-network
      A
      license
      A
      quality
      C
      maintenance
      ROS2 MCP server that bridges AI agents (Claude Code, OpenClaw, Cursor) to ROS2, allowing them to read topics, call services, control robots, and wrap telemetry into verifiable hash-chained proof bundles.
      6
      MIT

    • RobotMCP

      manykarim
      A
      license
      A
      quality
      A
      maintenance
      RobotMCP is a comprehensive Model Context Protocol (MCP) server that bridges the gap between human language and Robot Framework automation. It enables AI agents to understand test intentions, execute steps interactively, and generate complete test suites from successful executions.
      19
      113
      Apache 2.0

    • VLA-Diff-MCP

      zhywwyzh
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect and control a robotic VLA system via MCP, offering read-only tools for ROS topics, processes, tmux, and logs, as well as write tools for publishing prompts, issuing tmux commands, restarting services, and running shell commands inside containers.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation3/5

    Several tool pairs overlap in function: list_topics/get_topic_info, list_nodes/get_node_info, capture_topic_sync/capture_inject_sync, and the three analysis tools (analyze_step_response, analyze_gimbal_pid, diagnose_gimbal_tuning). While descriptions clarify the differences, the boundaries are not always obvious to an agent.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_topics, get_param, set_param, etc.). Exceptions like 'preflight' and 'launch' are bare verbs, and 'capture_inject_sync' is a compound. Overall the pattern is consistent enough.

    Tool Count2/5

    With 26 tools, the surface is heavy, and there is notable redundancy (e.g., three analysis tools, two capture tools). Some tools could be merged, making the count feel inflated for the stated purpose.

    Completeness4/5

    The core gimbal tuning workflow is well covered: parameter read/write, injection, capture, recording, and analysis. Minor gaps exist, such as a generic service caller or generic publish tool, but agents can work around these using existing tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources