Revit Agents vs Revit MCP: What's the Difference?

Revit MCP and Revit Agents are frequently used as if they mean the same thing. They describe different layers of the same stack, and the distinction matters as soon as automation moves beyond one workstation.

In short

Revit MCP is the local protocol layer that exposes Autodesk Revit API operations to a language model as tools. Revit Agents is the governance layer above it, controlling which agents, prompts and tools are approved, who can run them, and how runs are previewed, authorised and audited.

Two layers, two different jobs

The confusion is understandable — both names contain the word that matters, and in a one-person proof of concept the two layers collapse into the same terminal window. They separate as soon as a second person, a second project or a second machine is involved.

Revit MCP — the capability layer: Runs locally. Exposes Revit API operations as tools. Answers 'what can technically be done to this model?'
Revit Agents — the governance layer: Runs as an authenticated console. Decides which agents, prompts and tools are approved, who may run them, and what is recorded. Answers 'what should be done, by whom, and with what evidence?'

Side by side

A useful analogy: Revit MCP is the set of power tools; Revit Agents is the method statement, the permit and the site record that make using them acceptable on a live job.

Scope: MCP is per-workstation. Revit Agents is per-company and per-project, spanning many workstations.
Prompts: MCP has no opinion about prompts. Revit Agents versions them, with draft and active states so an approved prompt is never silently overwritten.
Permissions: MCP grants whatever the server exposes. Revit Agents applies role-based access and least-privilege tool grants per agent.
Approval: MCP will run a write tool the moment it is called. Revit Agents distinguishes analysis and preview from an authorised applied run.
Evidence: MCP leaves whatever its own logs contain. Revit Agents records runs, approvals and outcomes against a project.
Where execution happens: Identical in both cases — on the workstation. Revit Agents never moves your model to the cloud.

How they work together

Revit Agents does not replace an MCP server, and it does not reimplement the Revit API. It sits in front of one. Policy checks happen server-side in the console; execution is dispatched through a secure connector to a specific paired workstation, where the local agent runtime and MCP server do the actual work.

Capability is detected per workstation rather than assumed — if a connector or tool is not genuinely reachable, the console reports that instead of pretending a feature is live.

Combined path

Revit Agents console       policy · approvals · audit
        ↓  authenticated server functions
Secure connector           paired workstation identity
        ↓  workstation-local
Local agent runtime → Revit MCP server → Revit API → Revit

Which do you need?

If you are a single developer testing whether an LLM can read your model, a local MCP server is sufficient and Revit Agents adds nothing you need yet.

The moment automation is expected to behave the same way for a colleague on another project, or someone asks who approved a change that reached a live model, you need the governance layer as well. Most practices arrive at that question shortly after the first successful demo.