RevitAiTools
activeA C# plugin and an MCP server that drive Revit from an AI client: tools are called by the model and executed on the Revit thread.
Revit API / AI engineer
Revit API, AI and MCP in one engineering loop
I build tools that solve problems instead of repeating the lecturer's steps. The same approach — AI agents, MCP and an engineering process — transfers to any other task, not only Revit.
Revit plugins and AI agents that solve engineering problems
I build tools for Revit and the AI agents that drive them: from a first ExternalCommand to a built, tested plugin handed over to other people.
I run AI × Revit Community — a starter repository, an MCP server, a course and project walkthroughs. Every example follows the same route the landing page describes: task, plan with AI, development, verification, build, release.
Revit is the first domain and the practice ground here: the cost of a mistake is high, which is exactly why setting a task, checking the result and owning the change becomes visible. The skill itself transfers to spreadsheets, reports, integrations and internal utilities.
From a first ExternalCommand to a published repository.
Agents that write code and work with tools.
Connecting tools to models over a standard.
The same stack for any automation task.
A plugin starter repository, an MCP server, a course and project walkthroughs: the full path from an idea to a released tool.
A C# plugin and an MCP server that drive Revit from an AI client: tools are called by the model and executed on the Revit thread.
The environment around the repository: a course, an engineering library, a digest and a community of engineers.
Questions about the course, the repository and working together — through community support.
WriteProject materials and task walkthroughs live in the digest and the site articles.