Autodesk Assistant and MCP in Revit: Querying models and creating sheets

What you’ll learn in this guide

Autodesk Assistant can be used within Revit to access help content and request certain model-related tasks using natural language. Autodesk’s documentation highlights contextual help, model queries, and model changes as key use cases. Example workflows show how to create a floor plan, apply a view template, tag rooms, prepare sheets, and export PDFs.

This guide focuses on trying these tasks in a controlled way. The sample prompts are based on the capabilities described in the documentation; there is no guarantee they will produce the same results in every project. It’s important to check Assistant’s results in the model, especially before sheet and delivery tasks.

Requirements and version notes

Before you begin, open Revit and sign in to your Autodesk account. Autodesk’s Revit 2027 help explains that you can access the Assistant panel by signing in and clicking the Assistant icon next to Help in the title bar. Alternatively, use View > User Interface > Autodesk Assistant from the Revit menu. If the panel doesn’t appear, Autodesk recommends closing and restarting Revit.

Like other panels, the Assistant panel can be moved, docked, or placed on a second screen. Drag it by its title bar to reposition it. According to Autodesk’s help, the panel can be grouped in the same area as the Properties palette and Project Browser.

Note the version distinction: Autodesk’s help lists Revit MCP Server as a local technical preview and public beta that works with Revit 2027.2 models. This does not mean that the same MCP access is available in every Revit installation. The Assistant documentation also notes that the icon may look different before 2027.3. These sources do not specify subscription, pricing, hardware requirements, or which accounts have access to all features.

Step by step: Open Assistant and try prompts

1. Sign in and open the panel. Sign in to Revit with your Autodesk account. Select the Assistant icon in the title bar. If you don’t see it, try View > User Interface > Autodesk Assistant; if the panel still doesn’t open, restart Revit.

2. Start with a model query. Assistant supports queries for finding and analyzing model elements. Begin with a narrowly scoped request. This makes it easier to check in the model whether the result covers the expected category and level.

Zemin Kat seviyesindeki kapıları bul ve sonuçları bu seviyeye göre listele.

This prompt is designed to test the model-query capability. Verify the results in the relevant Revit view; the sources don’t detail how query results will be presented in every model.

1. Try creating a floor plan. Autodesk’s example workflow includes creating a new plan view, applying a view template, and tagging rooms. Use a clear name in your own project and check that the operation is performed for the correct level.

2. Kat için “A-02 Sunum” adlı yeni bir kat planı oluştur ve uygun görünüm şablonunu uygula.

This prompt tests the ability to create a plan view and apply a template in one go. Review whether the template Assistant selects meets your project’s presentation standards; keep in mind that “appropriate” may not, on its own, explain project-specific requirements.

1. Have Assistant add room tags. Room management is listed among the MCP tool groups supported by Assistant. Limiting the tagging request to a specific view makes it clear which plan to work on.

A-02 Sunum plan görünüşündeki odaları etiketle.

Once the operation is complete, check that the tags match the right rooms in the view and are legible at sheet scale. The sources do not provide detailed prompt syntax for managing tag placement or display settings.

1. Handle sheet and PDF tasks carefully. Autodesk’s example video includes creating separate sheets for new plans, editing sheet names, and exporting PDFs. Check the plan views are final before requesting these tasks.

A-02 Sunum planı için yeni bir pafta oluştur, pafta adının başına “Kontrol” ekle ve paftayı PDF olarak dışa aktar.

This example is designed to let you try the documented sheet-management and export workflow with a single prompt. Assistant saying it has completed the task is not, by itself, a delivery check: open and review the sheet, its name, and the resulting PDF file.

Common mistakes and checkpoints

Writing vague prompts: A request like “prepare the plan” doesn’t specify the scope, level, view name, or output type. State the target level and task clearly. Autodesk’s general MCP documentation also emphasizes clear inputs, but doesn’t provide a specific Revit prompt format or a required list of words.

Proceeding without checking the result: Creating a view doesn’t necessarily mean the view template is correct or that every room has been tagged. After each step, inspect the relevant view in Revit; for model edits, make sure the scope is correct as well.

Overlooking beta status and availability: Revit MCP Server is identified as a technical preview and public beta in Autodesk’s help. Don’t interpret its being listed as meaning it’s ready in every Revit version or enterprise installation. Verify access in your own environment.

Skipping privacy and permissions checks: Autodesk says MCP servers manage access through identity and permissions, validate requests, and enforce operation limits. Assistant chat history and the prompt library are stored in the cloud in connection with your Autodesk account. Autodesk says this data and customer-confidential data are not used to train language models. For office workflows, assess as a team what model context is shared and what access permissions apply.

Impact on architecture and visualization workflows

The documented tasks—such as floor plans, room tags, sheet layouts, and PDF exports—make Assistant suitable for teams in architecture and interior design to try on repetitive documentation tasks. Searching for model elements can also be a starting point for locating a particular category or level in large projects. However, the sources do not say these tasks can be completed without human review or that they will save time in every project.

For archviz teams, the use case documented here is interaction with Revit models and documentation workflows, not image generation. Teams should still verify office standards, sheet naming, and output checks. Since the sources do not explain hardware requirements, pricing, or licensing terms, check the latest details separately before making a purchase or rollout decision.

Next steps

Start with a copied or test project and try one query and one view operation. After checking the result, try tagging, sheet creation, and export as separate tasks. This makes it easier to track which prompt produced each change.

If the tool is to be used across a team, define prompts and approval steps according to your project standards. Autodesk says Assistant’s capabilities may expand over time and that targeted updates may arrive independently of Revit’s general release cycle. Revisit the help documentation when the interface or capabilities change.

Sources and licensing

This guide was independently prepared based on Autodesk’s “Using Autodesk MCP Servers” help page, Autodesk MCP Servers product page, and “Autodesk Assistant in Revit” help document. The source records identify these pages as license=free. The sample prompts were written for this guide; official sample prompts have not been copied.