Skip to main content
Glama
xiuchuan666

revit-tunnel-mcp

by xiuchuan666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to revit-tunnel-mcp

No user-submitted related servers found.

    Related Servers

    • Revit MCP Server

      pradeepmisal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with Autodesk Revit for building design, editing, analysis, clash detection, MEP, interop, documentation, and model persistence via 48 tools.
      MIT

    • revit-mcp

      Mohamed-Elnahla
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Autodesk Revit to query project data, manage elements, and execute generated code via the Model Context Protocol. It provides full compatibility with GitHub Copilot and Claude to automate BIM modeling workflows.
      13
      123 npm
      MIT

    • TopoSpatial-CAD MCP

      Nihalmannath
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with CAD software through semantic spatial topology and architectural ontology, supporting drawing, block/layer/entity management, and safe preview-apply transaction workflows for AutoCAD, ZWCAD, GstarCAD, and BricsCAD.
      1
      Apache 2.0

    • revit-bridge

      revitbridge
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to execute designer-confirmed code and reusable capability packs inside a running Autodesk Revit instance.
      5
      MIT

    • rvt-mcp

      bimwright
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that bridges AI agents to Autodesk Revit, enabling local tool-based interaction with Revit models, including query, create, and modify operations, with an optional personal tool baking system.
      46
      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.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource (catalog, backend status, segments, rings) and action (list, get, preview, inspect, create). Preview vs. inspect are clearly differentiated: preview validates and returns tokens, while inspect returns detailed properties by batch ID.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun snake_case pattern, using verbs like list, get, preview, inspect, and create paired with clear nouns (tunnel_segment_catalog, tunnel_segments, tunnel_rings). Minor variations like segment_batch vs batch still follow the same style.

    Tool Count5/5

    8 tools is well within the ideal range and each tool earns its place, covering catalog, status, preview, inspect, and create for two related domain objects (segments and rings). No redundant or missing tools at the surface level.

    Completeness4/5

    The server covers the full preview->create->inspect lifecycle for both tunnel segments and rings, plus backend status and catalog listing. Missing update/delete operations are not critical for a creation-focused server, but could be a minor gap if modifications are needed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources