Skip to main content
Glama
vagotec

ros2_dev_mcp

by vagotec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ros2_dev_mcp

No user-submitted related servers found.

    Related Servers

    • ros2_mcp

      vagotec
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables MCP clients to interact with ROS 2 systems, providing runtime access and safe project creation and modification.
      Apache 2.0

    • Void MCP Filesystem Server

      EdibleTuber
      F
      license
      Not graded
      quality
      D
      maintenance
      A secure, sandboxed MCP server that provides Void Editor with safe filesystem access, enabling AI to create, read, modify, and delete files with comprehensive security controls.
      1
      -

    • shemcp

      acartine
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides sandboxed shell command execution with configurable security policies, enabling safe AI-assisted command runs within a project repository.
      3
      4 npm
      2
      MIT

    • warden

      dsvxmedia
      A
      license
      Not graded
      quality
      C
      maintenance
      A sandboxed MCP server that executes shell commands inside ephemeral, locked-down Docker containers with no network by default, dropped capabilities, and an audit log, enabling secure agent-driven command execution.
      3 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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct artifact or action in the ROS 2 development lifecycle: workspace, package, node, launch file, parameter file, tests, building, and running tests. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create_* for scaffolding actions and build_project/run_tests for build/test actions. No mixed conventions or vague verbs.

    Tool Count5/5

    8 tools is well-scoped for a ROS 2 development server, covering the essential create, build, and test operations without unnecessary redundancy. The count feels proportionate to the server's purpose.

    Completeness4/5

    The server covers the core Python ROS 2 scaffolding workflow: workspace, package, node, launch, parameters, tests, build, and test. Missing operations like C++ package support or custom interface generation, but the stated Python-focused scope makes these minor gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources