bimaiConnections
Connect your team to Autodesk's MCP servers with one command, and sign in without ever handling a key.
Available
bimai connect works today. Autodesk's servers are Technical Previews.Your team can only use the tools you connect. A connection is an MCP server: a small program that lets an AI read (and sometimes change) data in a tool such as Revit. bimai keeps all of them in one list and handles the setup for you.
What you can connect
bimai connect| Server | Runs | Sign-in | Can change data? |
|---|---|---|---|
| Autodesk Product Help | Autodesk's cloud | none | no. Every project gets it automatically |
| Revit | on your computer, inside Revit 2027.2 with Autodesk's MCP add-on (Windows) | none | no: bimai uses its read-only tools |
| Autodesk Fusion | on your computer, inside Fusion | none | yes |
| Autodesk Fusion Data | Autodesk's cloud | your Autodesk account | yes |
| InfoWorks Hydraulic Modeling | Autodesk's cloud, one address per region (US, UK, Australia) | your Autodesk account | yes |
| Autodesk Fusion Compute (beta) | Autodesk's cloud, Fusion without a desktop | your Autodesk account | yes |
| Civil 3D (bimai bridge) | on your computer, inside Civil 3D 2025–2027 (Windows) | none | no: read-only. See Civil 3D bridge |
| AutoCAD and Civil 3D (Autodesk) | inside Autodesk Assistant only | – | not connectable; use the bimai Civil 3D bridge |
AutoCAD and Civil 3D today
Autodesk has its own AI inside AutoCAD and Civil 3D: Autodesk Assistant (in Civil 3D 2027 a Tech Preview). Its drawing tools only work inside Assistant for now, and Autodesk has said a way for other AI tools to connect will follow. Until then there are two separate assistants:
| Autodesk Assistant | Your bimai team | |
|---|---|---|
| Where | inside AutoCAD or Civil 3D | in VS Code, with Claude Code |
| Reaches your drawing | yes, the open drawing | yes, read-only, through bimai's own Civil 3D bridge |
| Knows your project's agreements, decisions and team | no | yes |
They don't share information with each other yet. Organisations that don't want Assistant to talk to outside services can only block that at network level for now (Autodesk support article on Vault).
Connect a server
bimai connect revitThat's all. bimai adds the server to your project, finds where it's installed, and updates your team: the Model Checker gets Revit, members who don't need it don't. Start a new Claude Code session to use it; Claude Code asks you once to approve the project's servers.
For a regional server, add the region your projects are hosted in:
bimai connect hydraulic-modeling --region gbrSigning in
There are three cases, and bimai tells you which one applies:
| Case | Servers | What you do |
|---|---|---|
| No sign-in | Product Help, Revit, Fusion | Nothing |
| Autodesk account | Fusion Data, Hydraulic Modeling | Sign in once in your browser |
| Key | your own servers that need an API key | Paste the key once |
Signing in with your Autodesk account uses Autodesk's official sign-in, the same one as in
Autodesk's own documentation. Start Claude Code in the project, approve the servers when asked, type
/mcp, choose the server and select Authenticate. Your browser opens the normal Autodesk sign-in.
Afterwards, Claude Code keeps the sign-in in your computer's keychain and renews it itself. You can
also start it from the terminal:
bimai auth login fusion-dataWhat you can see and do through a server is exactly what your Autodesk account can already see and do: the same hubs, projects and permissions. Your Autodesk administrator manages that as usual.
Keys for your own servers are asked once, without showing what you type, and stored in your computer's keychain:
bimai connect --custom my-api --url https://example.com/mcp --auth keyClaude Code fetches the key from the keychain each time it connects. The key is never written to a file.
bimai auth status # which servers need what; never shows a key
bimai auth logout my-apiRead by default
Servers that can change data are only added when you agree. bimai then adds a rule so that every call to that server asks your approval first, also in Claude Code's auto mode.
bimai connect fusion-data --allow-writesClaude Code's "bypass permissions" mode skips all approval prompts, including these. Don't use that mode in a project with servers that can change data.
What is stored where
| What | Where | Who sees it |
|---|---|---|
| The list of servers | .mcp.json in the project | the whole team (it's shared) |
| Approval rules | .claude/settings.json in the project | the whole team |
| Autodesk sign-ins | your computer's keychain, managed by Claude Code | only you; never bimai, never the AI |
| Keys for your own servers | your computer's keychain | only you; never the AI |
.mcp.json never contains a secret: bimai validate reports one if someone pastes a token into it.
Your team and its connections
Each team member only gets the servers its job needs. The Coordinator's instructions list what the team is connected to, and which tools you mentioned during setup are not connected, so nobody claims data from a tool it can't reach.
bimai disconnect fusion-data # removes the server, its approval rule and your sign-in