Skip to main content
Glama
Revit MCP Automation

Revit MCP Automation

Related Servers

Alternatives to Revit MCP Automation

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to connect to Autodesk Revit sessions, discover and call native modeling and documentation tools, execute C# or Python inside Revit, and inspect change history or model snapshots.
      1
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Open-source MCP server for Autodesk Revit 2022 to 2027: read, audit and edit live models with 89 tools, one Undo entry per change, and a workstation read-only lock.
      89
      17
      MIT
    • 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
      178 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients and an in-Revit chat pane to drive Autodesk Revit 2025+, exposing 100+ commands for model querying, QA/QC, modeling, rebar, sheets and schedules, plus running custom single-file .cs commands and C# scripts with undoable edits. Includes a headless 'virtual hand' mode that operates Revit's own commands and UI when no API exists, with view screenshots returned to the AI.
      1
      GPL 3.0

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct step in the managed-Revit lifecycle: status probe, model open, dialog inspection, dialog interaction, and result retrieval. The only mild overlap is between get_revit_automation_status and get_revit_operation_result, though the descriptions make clear one reports instance state and the other reports an async operation's outcome.

    Naming Consistency5/5

    All five tools use snake_case with a predictable verb_noun pattern (get_/open_/click_) and a consistent revit namespace segment. No mixing of conventions or vague verbs.

    Tool Count5/5

    Five tools is tightly scoped to the stated purpose of driving a separate managed Revit instance and resolving its dialogs. Each tool earns its place as a distinct phase of that workflow.

    Completeness3/5

    The dialog-handling lifecycle is closed-loop (detect, click, retrieve result) and status/open are present, but there is no way to close or reset the managed instance and no tool to actually issue a model operation whose result would be retrieved. Agents depend on external tools for anything beyond opening a file.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues