bim-cli

com.bimcliPublished by bimcli.comv0.35.1Updated Nov 5, 2026

Let agents drive Revit, AutoCAD, SketchUp, Blender and PDF sets on your own Windows desktop.

Overview

AI-generated overview

Windows-only local MCP server that lets an agent drive Revit, AutoCAD, SketchUp and Blender, check drawing-set PDFs, and look up US site and flood data.

What you can do
  • Check, extract text from, stamp, split and merge PDF drawing sets
  • Drive Revit 2024-2027 jobs by starting or attaching to an installed Revit
  • Convert IFC, FBX and glTF files in the background via Blender
  • Look up flood zone and site data for a US address
  • Expose every installed bim-cli verb as a tool, generated from bim describe
When to use it
Useful when an agent should work on BIM and CAD files on a Windows desktop: auditing drawing-set PDFs, running Revit tasks without clicking through the UI, converting 3D formats, or pulling US flood and site data.
Requirements
A Windows machine with bim-cli installed and on PATH, launched as the local bim mcp stdio server; Revit jobs need Revit installed. No account, API key or environment variable is declared. Flood lookups need network access to a public FEMA/NFHL endpoint.
Before you install
Tools run real local commands that can modify files, for example adding stamps or watermarks to PDF pages and splitting or merging PDFs. Optional anonymous telemetry is on by default; opt out with DO_NOT_TRACK=1 or BIM_TELEMETRY=0. Flood lookups send the address to a public FEMA/NFHL endpoint.

Installation

In SourceWeft

  1. Open bim-cli in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

bim-cli Claude Code Plugin

Claude Code plugin for bim-cli. Lets AI agents drive Revit 2024-2027, check drawing-set PDFs, and pull US site and flood data -- local, free, no account. Revit jobs need Revit installed on the machine: bim starts or attaches to it and drives it, so no one has to click through Revit. PDF, site and IFC jobs need no desktop app.

Windows-only. bim-cli is a Windows-only CLI. This plugin requires a Windows machine with bim-cli installed.

What this plugin does

Exposes all installed bim-cli verbs as MCP tools in Claude Code. Each tool maps to a bim <format> <verb> command running locally on your machine. Example tools:

  • pdf_set.check -- find missing sheets, unresolved callouts and titleblock mismatches in a drawing set
  • pdf_text -- extract text from a PDF without opening it
  • pdf_stamp.add -- apply a Bates stamp or watermark to PDF pages
  • pdf_page.split, pdf_page.merge -- split or combine PDF files
  • site_flood.lookup, site_assess -- flood zone and site data for a US address
  • blender_convert -- convert IFC/FBX/glTF in the background

The tool list is generated dynamically from bim describe --json -- adding a new bim-cli driver or verb makes it available automatically.

About this plugin repo

This repository contains only manifest files (JSON and Markdown), plus one stdlib Python maintenance script (scripts/check_skills.py) that the plugin never runs. It contains:

  • No executable code in the plugin itself
  • No telemetry of its own
  • No secrets or credentials
  • No network calls

All execution is local: the plugin simply tells Claude Code how to launch the already-installed bim binary as a local stdio MCP server (bim mcp). Nothing runs in the cloud.

Setup

  1. Install bim-cli (Windows, run in PowerShell):

    powershell
    iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1

    Verify: bim describe --json should list installed drivers.

  2. Add this plugin to Claude Code via the Claude Code plugin directory, or manually add the following to your .mcp.json in your project root (or via Claude Code settings):

    json
    {  "mcpServers": {    "bim": {      "type": "stdio",      "command": "bim",      "args": ["mcp"]    }  }}
  3. Restart Claude Code. Verify with bim doctor that installed drivers are healthy.

Agent skill (Hermes, Claude Code, and other Agent Skills hosts)

skills/bim-cli/ is an Agent Skills skill that teaches an agent how to drive bim from the terminal: discovery with bim describe, output and error conventions, and working notes for the PDF and Revit drivers. Claude Code loads it automatically with this plugin.

Hermes Agent:

bash
hermes skills tap add HelloHowAreYouHaveANiceDay/bim-cli-pluginhermes skills install HelloHowAreYouHaveANiceDay/bim-cli-plugin/skills/bim-cli

The skill is Windows-only (platforms: [windows]) and expects bim-cli on PATH. It never runs the installer itself; it hands the PowerShell one-liner to the user.

It is also served from bimcli.com as an Agent Skills well-known endpoint: https://bimcli.com/.well-known/skills/index.json (proxied live from skills/ on main).

bash
hermes skills install well-known:https://bimcli.com/.well-known/skills/bim-cli

Changing a skill

  1. Edit skills/<name>/, bump version: in its frontmatter.
  2. python scripts/check_skills.py regenerates skills/index.json (the well-known index).
  3. python scripts/check_skills.py --check --scan <hermes-agent checkout> must pass: Hermes only installs community skills that its scanner rates SAFE. Never put curl ... | bash (or any pipe-to-shell) in a skill; that is a hard block.
  4. Merge to main. The tap and bimcli.com pick it up immediately; Hermes users get it with hermes skills update.

Privacy Policy

bim-cli runs entirely on your local machine. The MCP server (bim mcp) does not make network calls beyond what the individual bim-cli verbs themselves make (e.g. a flood lookup calls a public FEMA/NFHL endpoint; a PDF operation makes no network calls at all).

What leaves your machine:

  • Optional anonymous telemetry: verb shape, bim version, OS, success/error kind, latency. No file paths, addresses, document content, or user identity are ever sent. Set DO_NOT_TRACK=1 or BIM_TELEMETRY=0 to opt out entirely.
  • Verb-specific network calls declared in bim describe --json under each verb's requires field (e.g. network:host for flood lookups).

What never leaves your machine:

  • Document content (PDF pages, IFC geometry, Revit models).
  • File paths or filenames.
  • User identity or any personal data.
  • MCP argument values.

Full privacy policy: https://bimcli.com/privacy

License

The files in this repository (the plugin manifest and MCP server declaration) are released under the MIT License. See LICENSE.

The MIT License covers only the manifest files in this repo. The bim-cli binary itself is proprietary software; its license is separate and can be found at https://bimcli.com.

More

Source: README.md at commit 5533620

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

4
  1. v0.35.1LatestNov 5, 2026
  2. v0.32.0Oct 29, 2026
  3. v0.27.0Oct 17, 2026
  4. v0.26.0Oct 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts