Skip to main content
Glama
sharafutdinovdi

Revit Model MCP

by sharafutdinovdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Revit Model MCP

No user-submitted related servers found.

    Related Servers

    • 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
      60 npm
      MIT

    • revit-mcp

      HoareLea
      A
      license
      A
      quality
      F
      maintenance
      Enables AI to interact with Revit via MCP, allowing data retrieval and element creation, modification, and deletion.
      13
      60 npm
      MIT

    • 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

    • NavisworksMCP

      shuotao
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI platforms to control Autodesk Navisworks via natural language, supporting model analysis, selection, data extraction, and visual management.
      7
      -
    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

    A4.4/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: catalog discovery, element queries, view summaries, view-scoped elements, warnings, health checks, links, coordinates, relations, and export are all separated cleanly. Cross-references explicitly direct which tool to prefer, so an agent is unlikely to misselect between similarly scoped tools like query_elements and view_elements.

    Naming Consistency4/5

    All names share the revit_ prefix and use lowercase snake_case, which makes the set feel uniform. The minor inconsistency is that some names are verb-led (list_, query_, export_) while others are noun-led (document_info, model_health, links_status), but the pattern remains readable and predictable.

    Tool Count4/5

    At 18 tools, the server is slightly above the typical 3-15 range, but the breadth is justified by the wide read-only inspection surface covering elements, views, warnings, links, coordinates, parameters, and export. Each tool has a distinct role and there is no obvious redundancy, so the count feels reasonable rather than bloated.

    Completeness5/5

    For its apparent read-only Revit inspection and export scope, the server covers the full workflow: catalog discovery, paginated element queries, view analysis, element details, warnings, model health, links, shared coordinates, parameter fill, instance enumeration, and PNG export. There are no dead ends; tools are explicitly chained with next-step guidance, making the surface complete for its purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources