Skip to main content
Glama
NEWSLabNTU

Autoware MCP Server

by NEWSLabNTU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Autoware MCP Server

No user-submitted related servers found.

    Related Servers

    • ROS & LLM Integration Bridge

      Ankit-Paliwal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables large language models to interact with ROS robots seamlessly, allowing natural language control, real-time sensor monitoring, and autonomous task execution without modifying existing robot code.
      Apache 2.0

    • 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

    • Principia Robotica

      EngineerAbdullahBinZafar
      A
      license
      Not graded
      quality
      B
      maintenance
      World-first unified MCP gateway + Control Barrier Function (CBF-QP) safety engine for agentic robotics, enabling LLMs to control physical robots with mathematically proven safety.
      MIT

    • UnrealEngine Bridge

      JosephOIbrahim
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive bridge connecting AI agents to Unreal Engine 5.7 through 39 MCP tools for scene manipulation, asset management, and blueprint control. It enables real-time perception and editor automation using the Remote Control API and file-based protocols.
      25
      2
      MIT

    • mavlink-mcp

      hieutachi
      A
      license
      A
      quality
      C
      maintenance
      Connects AI agents to MAVLink drones (PX4, ArduPilot) via a capability layer with safety guardrails, enabling telemetry, flight control, and mission management through natural language.
      12
      2
      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 57 tools

    Disambiguation4/5

    Most tools have distinct purposes, covering ROS2 operations, vehicle control, perception, monitoring, routing, launch management, and code generation. Minor overlaps exist (e.g., set_route/set_route_points, validate_launch_file/test_launch_file, get_detected_objects/analyze_driving_scene) but descriptions help disambiguate.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_ros2_topics, get_vehicle_state, send_velocity_command). No mixing of conventions or camelCase, ensuring predictability.

    Tool Count2/5

    With 57 tools, the server exceeds the recommended 25-tool threshold for coherence. While Autoware is complex, several tools could be merged (e.g., validate/test launch, route variants) to reduce bloat and cognitive load.

    Completeness4/5

    The tool set covers core Autoware workflows: perception, localization, routing, control, monitoring, launch management, and code generation. Minor gaps exist (e.g., bag recording, dynamic parameter adjustment), but the surface is largely complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources