Skip to main content
Glama
Sign In
RoboParty MCP

RoboParty MCP

Official
by Roboparty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to RoboParty MCP

No user-submitted related servers found.

    Related Servers

    • boop-mcp-rag

      ttacleinad-boop
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local RAG orchestration with MCP, providing context retrieval, in-memory text ingestion, explicit tool invocation, and transport-neutral tool discovery.
      -

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • Green MCP Toolbox

      fvegiard
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a centralized, deterministic MCP endpoint with routing, logging, and browser automation, enabling multiple LLMs to share a consistent set of tools including jq, ripgrep, Git, Python, and headless Chromium.
      MIT

    • ros2-mcp-server

      darshan-kt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language control and monitoring of ROS 2 robots through standardized MCP tools, with a deterministic safety layer and automatic capability discovery.
      Apache 2.0
    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 7 tools

    Disambiguation4/5

    The four docs tools form a clear retrieve-narrow-read chain (list_manuals -> list_toc -> search_docs -> get_page), though list_manuals and list_toc both enumerate material at different granularity and could occasionally be swapped. The three system1_laya tools are cleanly split between inference (analyze), status (health), and configuration (info), so boundaries are clear overall.

    Naming Consistency4/5

    Both namespaces use a predictable prefix plus action pattern: docs_<verb>_<noun> and system1_laya_<action>. Minor deviation only in that health and info are noun-like states rather than verbs like analyze, but everything stays snake_case and readable.

    Tool Count5/5

    Seven tools is well within the sweet spot, and each one covers a distinct step: enumerate sources, browse a category, search full text, open a page, plus three model-introspection calls. No filler or duplicate tools are present.

    Completeness5/5

    The docs surface covers the full discovery-to-read lifecycle (list manuals, list TOC, search, fetch page with section/limit options), and the Laya surface covers inference plus health and configuration introspection. The only 'gap' is robot control, which is explicitly out of scope for this analysis-only server, so no dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources