Skip to main content
Glama
README.md
# BAMROC MCP Server

<!-- mcp-name: io.github.Deepansu180102/bamroc -->

Detect and resolve **MEP clashes in Autodesk Revit** with **BAMROC Move and Bend**, from your own AI app (Claude,
Cursor, VS Code, ...). Then ask that AI to build what you need on top of it: your own agent, a script, a scheduled
check, or a Revit button. No coding needed: the server tells the AI how.

---

## For BIM modellers (no coding)

**You need:** Windows with **Revit 2024** (2026/2027: coming), a **Vavetek account with BAMROC tokens**, and an AI app.

1. **Connect BAMROC to your AI app.** Easiest: ask Claude Code (or any AI with a terminal)
   *"Install the BAMROC MCP server from https://github.com/Deepansu180102/BAMROC_MCP_Server and connect it."*
   Or add it yourself, see [Connect an AI app](#connect-an-ai-app).
2. **Ask:** *"Check my BAMROC setup."* The first time, it offers to install the **BAMROC Connector** in Revit: a small
   invisible add-in (no ribbon, no buttons, no panel). Say yes, then restart Revit and open your model.
3. **Use it, or build with it:**
   - *"Find the clashes in my model. Which ones can BAMROC fix? Show me the worst one."*
   - *"Resolve the MEP vs MEP clashes with Move, but skip sprinklers."*
   - *"Build me an agent I can double-click that fixes the pipe vs duct clashes every morning."*
   - *"Make me a Revit button that resolves only cable tray clashes with Bend."*

**Safety:** anything that spends BAMROC tokens, changes your model or installs something is confirmed by you first.
Every applied fix is one **Ctrl+Z** in Revit. Save a copy of the model before your first apply.

---

## For AI agents

You are connecting a user to BAMROC. Follow this, and the instructions the server sends when you connect.

1. **Install** (Python 3.10+, Windows): `pip install git+https://github.com/Deepansu180102/BAMROC_MCP_Server.git`
   or, without installing: `uvx --from git+https://github.com/Deepansu180102/BAMROC_MCP_Server.git bamroc-mcp`.
2. **Add it as a stdio MCP server** named `bamroc`: command = the **full path of the python.exe** you installed it
   into (`python -c "import sys; print(sys.executable)"`), args `["-m", "bamroc_mcp"]`. Prefer this over the
   `bamroc-mcp` command: pip often puts that in a Scripts folder that is not on PATH. Ask before editing the user's
   app settings.
3. **Call `CheckSetup`**, then read `BamrocGuide` topic `getting-started`. If the connector is missing, explain it, get
   a yes, call `InstallRevitConnector`, and ask the user to restart Revit.
4. **Building something** (agent, script, button)? Read `BamrocGuide` first: `build-an-agent`, `build-a-revit-button`,
   `call-from-code`, `tool-results`. Tested templates and the exact commands for the user's PC are there. Do not
   reverse-engineer the server or the user's files.
5. **Always ask the user first** before tokens (`RunBamroc*`), model changes (`ApplyBamroc*`, `MoveElement`) and
   installs (`InstallRevitConnector`). Test what you build with free, read-only tools only.

---

## Connect an AI app

| App | How |
|---|---|
| Claude Code | `claude mcp add bamroc -- uvx --from git+https://github.com/Deepansu180102/BAMROC_MCP_Server.git bamroc-mcp` |
| Claude Desktop, Cursor, VS Code | Add a stdio MCP server, for example in `claude_desktop_config.json`: |

```json
{
  "mcpServers": {
    "bamroc": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/Deepansu180102/BAMROC_MCP_Server.git", "bamroc-mcp"]
    }
  }
}
```

Without `uv`: `pip install git+https://github.com/Deepansu180102/BAMROC_MCP_Server.git`, then use the full path of
that Python (find it with `python -c "import sys; print(sys.executable)"`):

```json
{ "mcpServers": { "bamroc": { "command": "C:\\Users\\<you>\\AppData\\Local\\Python\\pythoncore-3.14-64\\python.exe",
                              "args": ["-m", "bamroc_mcp"] } } }
```

Claude Code: `claude mcp add bamroc -- "<full path of python.exe>" -m bamroc_mcp`.

---

## What it can do

| Tool | What it does | Cost / effect |
|---|---|---|
| `CheckSetup` | What is ready, what to fix | free |
| `BamrocGuide` | Guides: `getting-started`, `workflow`, `build-an-agent`, `build-a-revit-button`, `call-from-code`, `tool-results` | free |
| `ClashDetection`, `ListClashes`, `ShowInRevit` | Find clashes, list them with filters, select and zoom to one in Revit | free |
| `RunBamrocAnalysis` (Move), `RunBamrocBending` (Bend) | BAMROC prediction for the clashes you choose; saved to Downloads | **BAMROC tokens** (~1 per clash) |
| `ApplyBamrocMove`, `ApplyBamrocBend` | Apply the prediction in one Revit transaction | **changes the model** (one Ctrl+Z) |
| `InstallRevitConnector`, `UninstallRevitConnector` | Add or remove the invisible Revit connector | **changes Revit setup** |
| `MoveElement`, `GetModelData`, `Logout`, ... | Manual move, raw export, sign-out | |

Prompts: `resolve_clashes`, `build_bamroc_agent`, `build_revit_button`.

**From any program, without an MCP client:** `python -m bamroc_mcp.cli <Tool> "<json arguments>"` prints JSON
(`python -m bamroc_mcp.cli --list`; same as `bamroc-call` when that is on PATH). Token-spending, model-changing and
installing tools need `--yes`, given only after the user agreed.

## The Revit connector

Revit only lets code running inside Revit read or change a model, so BAMROC needs a small add-in there. It has no user
interface. `InstallRevitConnector` downloads `connector/BamrocConnector-<version>.zip` from this repository, checks its
SHA-256, and installs it into `%APPDATA%\Autodesk\Revit\Addins\<year>\` (no admin rights). `UninstallRevitConnector`
removes it.

If your AI app is a packaged Windows app (for example Claude Desktop), Windows may hide files it writes from Revit; the
install then stops and gives you the exact command to run from a normal Command Prompt
(`python -m bamroc_mcp.cli InstallRevitConnector --yes`).

## License

Proprietary, Copyright (c) 2026 VAVETEK.AI PTE LTD. Free to use with a Vavetek account; see `LICENSE`.