Skip to main content
Glama
liangjunglj-cpu

Almond MCP

by liangjunglj-cpu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Almond MCP

No user-submitted related servers found.

    Related Servers

    • Rhino MCP

      3d-mcp
      A
      license
      Not graded
      quality
      C
      maintenance
      It connects MCP-compatible assistants to Rhino 8 for checking status and describing the current selection, with optional explicitly enabled native Python scripting access.
      MIT

    • rhino-mcp

      Aaradhya-Dev-Tamrakar
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Rhinoceros 3D and Grasshopper, enabling generative NURBS geometry, parametric definition solving, layer manipulation, and viewport capture.
      MIT

    • Rhino MCP

      quocvibui
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered 3D modeling in Rhino 8 through 135+ tools for geometry, transformations, booleans, layers, materials, and more, using natural language.
      6
      MIT

    • RhinoMCP

      kbangaru-cyber
      A
      license
      C
      quality
      C
      maintenance
      Enables AI-driven 3D modeling, analysis, diagnostics, and Grasshopper integration within Rhino 3D through 90+ tools via the Model Context Protocol.
      105
      2
      MIT

    • GH_mcp_server

      veoery
      A
      license
      B
      quality
      F
      maintenance
      An MCP server that enables designers to interact with Rhino and Grasshopper via LLMs, analyze .3dm files, perform 3D modeling, and automatically generate GHPython code in Grasshopper based on user guidance.
      8
      31
      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 33 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action (e.g., get vs list vs place for different asset types). The only potential overlap between publish_objects_to_chestnut and publish_to_chestnut is clearly differentiated by their descriptions (detailed vs simplified). No two tools serve the same purpose.

    Naming Consistency5/5

    All 33 tools follow a consistent verb_noun snake_case pattern (e.g., apply_drawing_style, create_design_scene, list_capsules). No mixing of conventions like camelCase or different verb styles.

    Tool Count4/5

    33 tools cover a broad domain (scene creation, asset management, scripts, physics, publishing, validation). While slightly high compared to typical well-scoped servers (3-15), the number is justified by the breadth of functionality and each tool serves a clear purpose.

    Completeness4/5

    The surface covers core workflows: creation, retrieval, placement, execution, validation, and publishing. Minor gaps exist, such as lack of explicit delete/remove tools for objects or scenes, and no update tool for scenes. However, most lifecycle stages are present.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources