An icon of the Revit plug-in Start MCP by BIMO Tools

Start MCP

Launch a local BIMO MCP Server and connect clients to Revit context and BIMO commands.

Starts a local MCP (Model Context Protocol) server managed by BIMO Toolbar.Unlike “command-only bridges”, BIMO MCP Server is planned to be useful out of the box:- Revit Core Tools — work with documents, selection, element queries, parameters, and views- BIMO Command Platform — access to toolbar commands: - BIMO Library commands - user-generated commands from Dynamo, Python, and C# static classes - presets & variants (deterministic “modes” of a command)

This page is an interest check. The feature is in development. Want early access or a demo? Use the form at the bottom.

Why it matters

One install, no extra runtimes

Start MCP is designed to work with BIMO installation and updater — no manual Node/Python setup, no terminal workflows.

A real Revit endpoint

Clients get access to common Revit operations (read + limited safe write) without requiring users to hunt for third-party Revit MCP servers.

Your commands become reusable building blocks

Everything you already have in BIMO becomes callable from automation:

  • the same tool can run from UI, hotkeys, or automation pipelines

  • presets & variants ensure repeatable results

  • generated commands turn scripts into maintainable “products”


What you can access through BIMO MCP

Revit Core Tools (built-in)

Planned built-in capabilities include:

  • active document info and open documents list

  • current selection (read/set)

  • element queries (by category + parameter filters)

  • read element parameters

  • safe parameter writing (validated + transactional)

  • views list and view activation

The exact tool list may evolve, but the goal is clear: BIMO MCP should be useful even before you integrate anything custom.

BIMO Command Platform

With MCP running, clients can discover and run:

  • BIMO Library commands available on your toolbar

  • custom commands generated from:

    • Dynamo graphs (.dyn)

    • Python scripts

    • C# static classes

  • presets & variants — run the same command in multiple “modes”


Examples (use cases)

1) Deterministic automation with presets/variants

Run the same command with different presets, reliably:

  • “Export IFC (Client A profile)”

  • “Export IFC (Client B profile)”

  • “QA Check — Strict / Normal / Fast”

2) Turn scripts into managed commands

Your Dynamo/Python tools become discoverable, documented commands:

  • predictable execution

  • consistent settings model

  • easier reuse across projects and team members

3) AI assistants that can actually execute actions

Instead of just “suggesting steps”, an assistant can call a specific command or preset through MCP — in a controlled, auditable way.

4) Integration-friendly workflows

Connect Revit workflows with company services:

  • issue trackers

  • CDE processes

  • internal databases and rule sets


How it works (concept)

  1. You click Start MCP in BIMO Toolbar

  2. BIMO starts a local MCP server (localhost) and shows status + connection details

  3. An external client connects and can:

    • use Revit core tools

    • list and execute BIMO commands with presets/variants


Security and reliability

BIMO MCP is designed with a secure-by-default approach:

  • localhost binding by default (127.0.0.1)

  • authentication token for tool calls

  • clear separation of read tools vs write tools

  • transactional write operations (validated)

For teams, we plan governance features (allowlists, scopes, audit) based on demand.


MVP scope (planned)

MVP includes:

  • Start/Stop/Status

  • logs + connection test

  • Revit core tools (read + limited safe write)

  • list BIMO commands (library + generated)

  • execute BIMO commands with preset/variant

  • jobs model (status + cancel) for long operations

Next (if demand is confirmed):

  • multiple MCP profiles

  • workspace governance (allowlist/scopes)

  • audit and analytics

  • generator tools (rescan/regenerate sources) via MCP


FAQ

Do I need pyRevit?

No. The plan is a .NET-first implementation with no pyRevit dependency.

Do I need Node.js or Python installed?

The goal is to avoid manual runtime installation for the default path. (Advanced scenarios may appear later, but “one install” is the default promise.)

Will it work offline?

The server is local. Your integrations may depend on your internal systems.

Is this feature available now?

Not yet — this page is an interest check.


Get early access / request a demo

If you want to influence the MVP and get early access, send a request using the form below include:

  • Revit version (2020–2026)

  • team size

  • what you want to automate (Revit core tools, BIMO commands, generated commands, presets/variants)

  • any security/governance requirements

Want to give it a try?

We'll reach out and help you get started

Your name or company
Email or Telegram
Share your ideas or expectations (optional)
An error has occurred. This app may no longer respond until reloaded. Reload 🗙