Aec Model Bridge

Please install the `aec-model-bridge` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Windows and Revit** — Windows 10 or 11 and a licensed Autodesk Revit installation are required. Supported Revit versions are 2024, 2025, 2026, and 2027. (https://www.autodesk.com/products/revit/)
- **Install Python 3.11 or later** — Python 3.11+ is required to run the MCP server. (https://www.python.org/)
- **Install required .NET SDK/build tools for your Revit version** — Revit 2024 requires .NET 8 SDK and the .NET Framework 4.8 developer pack. Revit 2025 and 2026 require .NET 8 SDK. Revit 2027 requires .NET 10 SDK.
- **Clone the repository and install the Python MCP server** — The README presents source installation as the canonical path. Create a virtual environment and install the MCP server package in editable mode. Run: `git clone https://github.com/Sam-AEC/aec-model-bridge.git
cd aec-model-bridge
py -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install -e packages/mcp-server-revit` (https://github.com/Sam-AEC/aec-model-bridge)
- **Build and install the Revit add-in** — Package and install the version-specific native Revit add-in that the MCP server connects to over localhost. Restart Revit after installation. Run: `$RevitVersion = Read-Host "Revit year (2024, 2025, 2026, or 2027)"
.\scripts\package.ps1 -RevitVersion $RevitVersion
.\scripts\install.ps1 -RevitVersion $RevitVersion`

Canonical MCP server config (stdio transport):
- command: `<path-to-aec-model-bridge>\.venv\Scripts\python.exe`
- args: ["-m","revit_mcp_server.mcp_server"]
- required environment variables:
  - `MCP_REVIT_MODE`: Run mode for the server. The README config uses bridge mode to connect to the Revit add-in. (example: `bridge`)
  - `MCP_REVIT_BRIDGE_URL`: Local HTTP URL of the AEC Model Bridge Revit add-in service. (example: `http://127.0.0.1:3000`)
  - `MCP_REVIT_WORKSPACE_DIR`: Workspace directory the server may access. (example: `<path-to-your-revit-workspace>`)
  - `MCP_REVIT_ALLOWED_DIRECTORIES`: Allowed directories for server file access. The README example sets this to the same workspace path. (example: `<path-to-your-revit-workspace>`)

Note: The MCP transport between client and server is stdio. The Python server then communicates with the local Revit add-in over HTTP at the bridge URL. MCP Bundles (.mcpb) are mentioned as a client convenience, but the underlying canonical configuration is the stdio command above, and the Revit add-in is still required.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.