allplan-mcp-bridge
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@allplan-mcp-bridge Create a 5 m wall at (0,0,0) to (5000,0,0), height 3000 mm, thickness 300 mm."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
allplan-mcp-bridge
A production-grade MCP server that exposes Allplan's BIM API (geometry, attributes, IFC import/export, and layer management) to MCP clients such as Claude Code and Claude Desktop. Runs as a normal Python process that communicates with a PythonPart agent embedded inside Allplan over local TCP, so Claude can create, query, and modify BIM elements while every operation stays inside Allplan's native undo history.
Quick start
Prerequisites
Component | Version |
Allplan | 2026 (tested), likely works on 2025 / 2024-1 |
OS | Windows 10 / 11 |
Python (external) | 3.12+ |
|
|
Claude Code or Claude Desktop | Latest |
1 — Clone and install the MCP server
git clone https://github.com/andrej-reeg/allplan-mcp-bridge.git
cd allplan-mcp-bridge
uv sync2 — Install the Allplan PythonPart
python scripts\install_pythonpart.pyAuto-detects the Allplan 2026 PythonParts directory. Pass --scripts-dir and
--library-dir explicitly if auto-detection fails.
3 — Activate the bridge in Allplan
Launch Allplan 2026 and open any project.
In the Library, find Allplan MCP Bridge → AllplanMcpBridge and activate it.
A palette should appear. The bridge is now listening on TCP port 49152.
4 — Start the MCP server
uv run python -m allplan_mcp_serverYou should see {"event": "ipc.connected", ...} in the log. If not, check that the
Allplan palette is visible and the bridge is active.
5 — Configure Claude Code (or Claude Desktop)
Add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"allplan": {
"command": "uv",
"args": ["run", "python", "-m", "allplan_mcp_server"],
"cwd": "C:\\path\\to\\allplan-mcp-bridge"
}
}
}Then ask Claude:
"Create a 5 m wall at (0,0,0) to (5000,0,0), height 3000 mm, thickness 300 mm."
The wall should appear in Allplan, inside one undo bracket.
Related MCP server: Blender MCP
Architecture
Claude Code / Desktop
│ stdio JSON-RPC (MCP protocol)
▼
allplan_mcp_server (this repo — normal Python 3.12 process)
│ TCP 127.0.0.1:49152 length-prefixed JSON + HMAC token auth
▼
allplan_agent (PythonPart — runs INSIDE Allplan's embedded Python)
│ thread-safe queue
▼
Allplan main thread → NemAll_Python_* API → BIM documentSee docs/architecture.md for the full picture and
docs/threading-model.md for the one law that must
never be broken.
Configuration reference
All settings use the ALLPLAN_MCP_ prefix. Set as environment variables or in a
.env file in the repository root.
Variable | Default | Description |
|
|
|
|
| TCP host (loopback only) |
|
| TCP port |
| auto-detected | Root path for IFC file allowlist |
|
| Timeout for standard operations |
|
| Timeout for IFC import/export |
|
|
|
|
| IPC frame size cap (16 MiB) |
|
| Per-tool argument size cap (1 MiB) |
Available tools
See docs/tool-catalog.md for the full catalog with input
schemas and examples. Short summary:
Category | Tools |
Geometry |
|
Document |
|
Attributes |
|
Layers |
|
IFC |
|
Health |
|
Supported Allplan versions
Version | Status |
Allplan 2026 | Tested, supported |
Allplan 2025 | Should work — not formally tested |
Allplan 2024-1 | Should work — not formally tested |
Earlier | Not supported |
Limitations (v1)
Single instance. One Allplan + one MCP server. Multi-instance support is out of scope for v1; see
docs/architecture.mdfor the design note.Windows only. Allplan is Windows-only. The MCP server can run in WSL2 and connect to Allplan over TCP.
Geometry only.
create_slab,create_column,create_beamcreate generic 3-D solids (not architectural elements with material assignments). Architecture elements are planned for v2.No live preview. Elements are inserted when the bridge processes the command, not on mouse hover.
IFC size. Exports > 1 GiB are hard-rejected. Exports > 100 MiB log a warning.
Main-thread serialisation. All Allplan API calls run on the main thread. Heavy operations (large IFC export) will briefly freeze Allplan's UI.
Troubleshooting
ipc.connect_failed in MCP server logs
Confirm the Allplan palette is visible and shows "running".
Check that the TCP port (default 49152) is not blocked.
Check
~/.allplan-mcp/bridge.logfor errors from the agent.
Wall/element created but in wrong position
Check
~/.allplan-mcp/debug.logfor_wall: attempt Nlines — these show which geometry placement strategy succeeded.
PathNotAllowedError on IFC export
The path is outside
ALLPLAN_MCP_ALLPLAN_WORKSPACE_ROOT.Either move the file or set the env var to a parent directory.
Timeout errors on get_active_document_info
This call requires the Allplan main thread and returns
{main_thread_required: true}when called from the background pump. Trigger a mouse event in Allplan (move the cursor into the drawing) to process the next tick.
Development
uv sync --dev
uv run pytest tests/unit tests/integration
uv run ruff check src tests
uv run mypy srcSee CONTRIBUTING.md for how to add a new tool.
Available Tools
25 toolsassign_layerC
Assign an element to a layer by name. Participates in undo.
Inputs: uuid (required), kind (required), layer (required). Returns: object
copy_to_grid_positionA
Copy one or more elements to a new grid position.
Computes the offset from (from_x_line → to_x_line) and/or (from_y_line → to_y_line), then re-creates each element at the offset position. Elements must have been created in this session (UUIDs are looked up in the in-memory spec cache).
Example: copy a column from between X28–X29 to between X30–X31: from_x_line="28", to_x_line="30" → dx = X30 - X28
Returns a list of new ElementRef objects for the created copies.
Inputs: element_uuids (required), grid_name (required), from_x_line, to_x_line, +2 more. Returns: object
create_beamC
Create a beam element between two points. Units: mm.
Inputs: start (required), end (required), width_mm (required), height_mm (required), +1 more. Returns: object
create_columnC
Create a rectangular column element. Units: mm.
Inputs: base (required), height_mm (required), width_mm (required), depth_mm (required), +1 more. Returns: object
create_layerC
Create a new layer. Returns the created layer dict.
Inputs: name (required), parent, visible, locked. Returns: object
create_slabA
Create a slab element from a polygon outline. Minimum 3 points. Units: mm.
Inputs: outline (required), thickness_mm (required), layer. Returns: object
create_wallC
Create a wall element in the active Allplan document. Units: mm. Participates in undo.
Inputs: start (required), end (required), height_mm (required), thickness_mm (required), +2 more. Returns: object
define_gridA
Store or overwrite a named grid definition.
x_lines: lines with X coordinates (vertical, parallel to the Y axis). y_lines: lines with Y coordinates (horizontal, parallel to the X axis). Each line has a name (e.g. "28", "A") and a coordinate_mm value. Units: mm. Call get_grid_lines to verify after defining.
Inputs: name (required), x_lines (required), y_lines (required), z_base_mm, +1 more. Returns: object
delete_elementC
Delete an element by UUID. Participates in undo.
Inputs: uuid (required), kind (required). Returns: object
delete_gridC
Remove a grid definition by name.
Inputs: grid_name (required). Returns: object
export_ifcC
Export model or selected elements to an IFC file. Path must be absolute, inside workspace.
Inputs: path (required), schema_version, element_uuids. Returns: object
get_active_document_infoA
Return name, path, and units of the active Allplan document.
Inputs: no named parameters. Returns: object
get_attributesC
Return all scalar attributes of an element.
Inputs: uuid (required), kind (required). Returns: object
get_elementA
Retrieve an element by UUID. Raises if not found.
Inputs: uuid (required), kind (required). Returns: object
get_grid_linesA
Return all grid line names and coordinates for a named grid.
Use this to resolve grid line names to mm coordinates before calling create_wall, create_column, or other placement tools. Example: X line "28" → coordinate_mm=28000 means x=28000 mm.
Inputs: grid_name (required). Returns: object
healthA
Return server and agent health status.
Reports: agent connection state, last heartbeat age (ms), queue depth, reconnect count since server start, and per-tool call/error counts with p50/p95/p99 latencies over the last 1000 samples. Read-only — no side effects on the Allplan document.
Inputs: no named parameters. Returns: object
import_ifcB
Import an IFC file into the active document. Path must be absolute, inside workspace.
Inputs: path (required). Returns: object
list_gridsA
Return a summary of all defined grids.
To get full line data for a specific grid, call get_grid_lines.
Inputs: no named parameters. Returns: object
list_layersA
Return all layers defined in the active Allplan document.
Inputs: no named parameters. Returns: object
move_elementC
Translate an element by (dx, dy, dz) mm. Participates in undo.
Inputs: uuid (required), kind (required), dx (required), dy (required), +1 more. Returns: object
redoA
Redo the last undone operation in the active Allplan document.
Inputs: no named parameters. Returns: object
save_documentA
Save the active Allplan document to disk.
Inputs: no named parameters. Returns: object
set_attributesC
Set one or more attributes on an element. Participates in undo.
Inputs: uuid (required), kind (required), attributes (required). Returns: object
set_layer_visibilityB
Show or hide a layer by name.
Inputs: name (required), visible (required). Returns: object
undoA
Undo the last operation in the active Allplan document.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Each tool targets a distinct operation: element creation/modification, layer handling, grid management, I/O, document info, and undo/redo. No overlapping purposes; descriptions clearly differentiate them.
Most tools follow verb_noun snake_case (e.g., create_beam, list_layers), but a few deviate like 'health' (noun only) and 'copy_to_grid_position' (uses prepositions). Overall pattern is recognizable and consistent.
With 25 tools, the server is on the high side for a single-domain tool set. It covers many BIM operations, but the number is borderline and feels slightly heavy for a focused bridge.
The tool set covers essential CRUD and lifecycle operations for elements, layers, grids, and IFC import/export. Missing operations like updating element geometry or deleting layers are minor gaps that can be worked around.
Related MCP Connectors
Create projects, nodes, and tasks in UluP Spaces by conversation with Claude.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
Related MCP Servers
- AlicenseBqualityNot gradedmaintenanceEnables seamless communication between Claude AI and Autodesk Revit, allowing users to access and interact with Revit model information through natural language.618-
- FlicenseNot gradedqualityDmaintenanceEnables Claude AI to control Blender 3D through natural language commands for object creation, modification, deletion, and Python script execution.-
- AlicenseAqualityDmaintenanceConnects Claude AI to SketchUp, allowing you to create and modify 3D models via natural language commands.217MIT
- AlicenseCqualityBmaintenanceEnables Claude to drive Rhino 8 and Grasshopper for geometry creation, manipulation, and analysis via natural language.2469MIT