powershell.exe -NoProfile -ExecutionPolicy Bypass -Command 'iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1'
Cursor's agent can use terminal commands on your Windows machine. With bim-cli installed on PATH, it can check drawing sets, look up flood zones and zoning, build site reports, shrink PDFs, and help with Revit work without opening Revit.
Install bim-cli on the Windows machine running Cursor, then ask the agent to run bim describe --index to see the installed commands. The terminal route is the easiest way to start. If you want the commands to appear as MCP tools, configure the same bim mcp server in Cursor. MCP is optional; both approaches use the local bim-cli installation.
Paste this prompt into Cursor before giving it a task:
Install bim-cli on this Windows machine and use it for my AEC tasks. Run this installer command exactly: powershell.exe -NoProfile -ExecutionPolicy Bypass -Command 'iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1' Refresh PATH in this PowerShell session: $env:Path += ";$env:LOCALAPPDATA\bim-cli" Check readiness with `bim doctor --json`, then run `bim describe --index` to see the installed commands. Summarize what is ready and wait for my task.
Cursor runs shell commands directly in your terminal. Install bim-cli on the Windows machine where Cursor runs and make sure bim is available on PATH. Ask the agent to run bim describe --index to orient itself, then give it a task such as checking a drawing set, looking up a flood zone, or shrinking a PDF.
Cursor's terminal sandbox can restrict file access and network activity. Site lookups need network access to contact their data sources, so choose a Run Mode that permits the access your task needs. Local PDF work does not need a network connection. Review Cursor's terminal documentation for how terminal commands and sandbox behavior work.
Project instructions help the agent choose commands safely. Put a short bim-cli note in the repository's AGENTS.md or add a project rule under .cursor/rules/ as a .mdc file. In either place, tell the agent to run bim describe --index before selecting a verb.
Cursor can load a local stdio MCP server from mcp.json. Add the following entry to .cursor/mcp.json for one project or ~/.cursor/mcp.json for your user configuration:
{
"mcpServers": {
"bim": {
"type": "stdio",
"command": "bim",
"args": ["mcp"]
}
}
}
Save the file, then manage the server from Cursor's Customize page. Cursor's documentation says, "Disabled servers won't load or appear in chat." This can help when you want to reduce tool clutter. The configuration above is the documented stdio shape with the bim mcp command.
The same server was verified with Codex and a raw MCP client; Cursor itself was not available for a run. A full bim-cli installation returned 361 tools in a verified MCP check. That is a large set of commands to browse, so start with terminal commands when a direct bim invocation fits your task. You can enable MCP when you want tool discovery inside Cursor.
See Cursor's MCP configuration guide for config locations and server options, the terminal guide for Run Modes and sandboxing, and Cursor Rules for AGENTS.md and .cursor/rules project instructions.
Add this short note to the project's AGENTS.md, or save it as a .cursor/rules/bim-cli.mdc project rule:
## bim-cli
- bim-cli is installed on this Windows machine and available as `bim` in PowerShell.
- Run `bim describe --index` before choosing a bim command.
- Check the installed command schema and ask me if the task or file is ambiguous.
- Site lookups need network access. Local PDF checks do not need Revit.
Cursor supports project rules in .cursor/rules and recognizes AGENTS.md as a plain-markdown alternative. Follow the linked Cursor Rules guide if you want to scope a rule to particular files.
bim-cli is a Windows program, and these examples assume it is installed on the Windows machine running Cursor. Cursor setup follows Cursor's documentation and was not run by us. The bim mcp server itself was checked with Codex and a raw MCP client. Cursor's terminal sandbox can block network activity, and flood or zoning lookups need network access.
The MCP example uses Cursor's documented stdio configuration format. If the server does not appear, check that the JSON is valid, that bim is on Cursor's PATH, and that the server is enabled in Customize. bim describe --index remains available from the terminal to show which commands are installed.
No. Cursor's agent can call bim from the terminal. Set up MCP if you want those commands exposed as tools in chat.
Drawing-set checks, flood and zoning lookups, site reports, and PDF compression do not need Autodesk Revit. Revit-specific work needs Revit, though some Revit tasks can run without opening its interface.
Site data comes from network services. Check the Cursor Run Mode and sandbox permissions for network access, then retry when access is available.
Check the JSON file location and syntax, confirm bim is available on PATH, then open Customize and make sure the server is enabled. Disabled servers will not show up in chat.
Ask the agent to run bim describe --index for a compact list or bim describe --json for the full command schema. The installed drivers determine the available verbs.
powershell.exe -NoProfile -ExecutionPolicy Bypass -Command 'iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1'
Then ask your assistant to run bim describe --json. See what the installer does.