Search for "RevitMCP" and you will find more than one product. LUBIMKA publishes a RevitMCP connector through the Autodesk App Store, and a separate site, revitmcp.com, belongs to Nonica. Both connect AI assistants to Revit using the Model Context Protocol, which is why the names collide. They are still different software from different publishers, each with its own installer, documentation and terms. If colleagues have been collecting tutorials on their own, check which product each one describes before anyone follows the setup steps.
This guide covers the LUBIMKA product: what it is, what its listing says it does, and what else you need to use it.
Telling the two RevitMCP products apart
The easiest way to stay on the right product is to keep the publisher's name attached to it. LUBIMKA's version has two identifiers. One is its Autodesk App Store listing, which names LUBIMKA as publisher (LUBIMKA RevitMCP help page). The other is the public GitHub repository where LUBIMKA posts releases (LUBIMKA release history). Nonica's product is at revitmcp.com. Autodesk adds a third: alongside Revit Assistant in Revit 2027, it now offers its own public Revit MCP Technical Preview with Read, Write and Experimental extensions (Autodesk's Revit 2027.3 and 2027.4 update). That one comes from Autodesk, not LUBIMKA.
When a tutorial, forum post or video mentions RevitMCP, look for one of those identifiers. Instructions, version support and pricing for one product don't apply to the other. If you mix them, you can easily lose an afternoon troubleshooting a setup that was never going to work.
What an MCP connector does
The Model Context Protocol is a standard way for an AI client to use tools that another program provides. A Revit MCP connector runs alongside Revit and offers Revit operations as tools. You talk to your AI client. When your request needs information from the model or a change to it, the client calls the connector. The connector does the work in the open model and sends the result back into the conversation.
In practice, the connector is only half of the setup. You supply the AI client, and the connector gives it access to Revit. Our Revit MCP guide explains the difference between having that connection and having a complete project workflow.
LUBIMKA RevitMCP Autodesk App Store
According to its Autodesk App Store help page, LUBIMKA's RevitMCP runs on Windows with Revit 2024, 2025, 2026 and 2027, and it connects to MCP-capable AI clients. The listing describes live operations on elements, parameters, families, schedules, views and sheets. That means a connected client should be able to query the model and make changes to it while you work.
The connector is sold by subscription. The listing says it needs an active RevitMCP subscription, which is verified through your Autodesk sign-in. So the subscription is tied to an Autodesk account, and whoever sets it up will need to sign in with that account. The GitHub release history shows what changed between versions.
These are the publisher's descriptions. To find out whether a given operation works on your projects, try it on a copy of a real model. A good first request is one you can check yourself. For example, ask how many doors are on a level and compare the answer with a door schedule. If the count is right, the client is reading the model you think it is, and you can move on to edits.
Your AI client is a separate product
LUBIMKA's connector works with an MCP-capable client of your choosing, so the client is a separate product. It has its own account, its own pricing and its own data handling. Understand that split before you open a client's project with it.
The connector works on the model on your own machine, but that doesn't tell you where the conversation is processed. Your prompts are processed wherever the client sends them, and so is everything the connector passes back, such as element lists and parameter values. Read the client's privacy and data terms as well as LUBIMKA's. Check both against your firm's policies and any confidentiality requirements in your contracts.
Where ArchiLabs fits
A connector suits a team that already has an AI client it likes and wants to give it access to Revit. ArchiLabs Desktop is a single Windows application that puts the assistant and the Revit and AutoCAD work together. It edits native models in Revit 2023 through 2027. Revit 2023 is outside the range on LUBIMKA's listing, which matters if you still have projects on that version.
Desktop also takes in the material Revit work usually starts from. You can attach PDFs, specifications, spreadsheets, marked-up screenshots and narrated screen recordings in the same conversation as the model work. It starts at $19 a month plus usage credits (pricing). You can see what it does at ArchiLabs Desktop.
Understand Revit Model Context Protocol, Autodesk's Read and Write servers, Claude and OpenAI connection options, and where ArchiLabs Desktop fits.