LAMCP-Archicad
LAmbda MCP for Archicad: teach your LLM to do Archicad tricks.
LAMCP-Archicad lets Claude Code (or any MCP client) work in a live Archicad project: read elements and properties, draw walls, slabs, roofs, doors and windows, change parameters, take screenshots, and run short Python scripts that chain many commands in one go.
Everything goes through the Tapir Add-On and Archicad's own JSON API, so there is no bridge to install and nothing to compile.
Sibling of LAMCP for Grasshopper.
Try it on a copy first. The tools can create, change and delete model elements. Archicad's Undo (Ctrl+Z) reverts model changes, but not file operations such as saving or Teamwork send.
What you need
| Requirement | Notes |
|---|---|
| Archicad 25–30 | Windows or macOS. capture_view needs Archicad 30. |
| Tapir Add-On | The latest release. See step 1 below. |
| uv | Runs the server and fetches Python for you. See step 2 below. |
| Claude Code or another MCP client | Claude Code in the terminal, VS Code or the desktop app, Claude Desktop, etc. |
You don't need to install Python yourself, because uv takes care of it.
Installation
1. Install the Tapir Add-On in Archicad
Download from the latest Tapir release. Use either method:
- Installer (Windows, easiest). Close Archicad, then run
TapirInstaller_Win.exefrom the release page. It asks for administrator rights because it copies files into the Archicad folder. - Manual. Download the
.apx(Windows) or.bundle(macOS) file that matches your Archicad version, for exampleTapirAddOn_AC29_Win.apx, and save it somewhere permanent (not Downloads). In Archicad, go to Options → Add-On Manager → Edit List of Available Add-Ons → Add, pick the file, then click OK.
Check: after you restart Archicad, a Tapir menu appears in the menu bar. Tapir → Tapir Palette shows the installed version.
2. Install uv
Windows (PowerShell):
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
macOS:
curl -LsSf https://astral.sh/uv/install.sh | sh
Afterwards, open a new terminal so uv and uvx are on your PATH. See the
uv docs for
other options.
3. Register the server with Claude Code
claude mcp add lamcp-archicad --scope user -- uvx lamcp-archicad
--scope user makes the tools available in every project. Restart Claude
Code, or in VS Code run Developer: Reload Window, then start a new chat.
Run claude mcp list to check that lamcp-archicad is listed.
Install the latest development version from GitHub instead
claude mcp add lamcp-archicad --scope user -- uvx --from git+https://github.com/gramaziokohler/lamcp-archicad lamcp-archicad
Other MCP clients (Claude Desktop, Cursor, …)
The server talks MCP over stdio. Add it to your client's MCP configuration,
for example in Claude Desktop's claude_desktop_config.json:
{
"mcpServers": {
"lamcp-archicad": {
"command": "uvx",
"args": ["lamcp-archicad"]
}
}
}
4. Open a project and try it
- Start Archicad and open a project. Archicad only serves its JSON API while a project is open.
- Ask Claude something like:
- "Use lamcp-archicad to check the connection to Archicad."
- "List the stories and count the walls on each."
- "Draw a 6 × 4 m room on the ground floor with a slab, a hip roof, a door and a window in each wall."
If the first request reports Archicad's version and the Tapir version, you're set up.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| No Archicad found, or connection refused | Archicad isn't running or has no project open. Open a project. With several Archicads open, ask Claude to list_instances and select_instance. |
Invalid program status (ongoing user input) (code 4001) |
Archicad is in the middle of an input: a half-drawn element, an open dialog, or an edit mode (curtain wall, stair…). Press Esc, close dialogs, and try again. |
| Commands hang, then time out | A modal dialog is open in Archicad. Close it. |
Archicad does not have the registered Add-On command … (code 4010) |
Tapir isn't loaded, or the command is newer than your Tapir. Check the Tapir menu, then update Tapir. |
Invalid command parameters … additionalProperties … path '#/…/<field>' (code 4002) |
Your Tapir is older than the command reference describe_command reads, so it doesn't accept that field yet. Update Tapir, or leave the field out. |
capture_view: Available from Archicad 30 |
Screenshots need Archicad 30 and an open 3D window. |
uvx or claude is not recognized |
Open a new terminal after installing, or add their install folder to your PATH. |
How it works
LLM ──MCP stdio──▶ lamcp-archicad (Python 3.10+)
│
│ HTTP POST {"command": "API.ExecuteAddOnCommand", ...}
▼
Archicad JSON API on 127.0.0.1:19723 (+1 per extra instance)
├─ official commands (API.*)
└─ Tapir Add-On (several hundred commands)
Unlike LAMCP, this needs no bridge, because Archicad already serves a JSON
API and runs every command on its own main thread. The "lambda" part,
run_python_script, runs your code in the MCP server's process and
sends commands to Archicad. A broken script can't crash Archicad; only the
commands it sends reach Archicad.
Tools
| Tool | Purpose |
|---|---|
bridge_health |
Checks that Archicad and Tapir are reachable, and reports their versions. |
list_instances |
Finds every running Archicad (ports 19723–19744). |
select_instance |
Sends further commands to the Archicad on a given port. |
list_commands |
Lists the commands the installed Tapir offers, filterable by text or group. |
describe_command |
Shows one command's description and input schema (optionally its output schema and an example). |
run_command |
Runs one Tapir command, or an official one as API.<Name>. |
run_python_script |
Runs Python with tapir() / archicad() helpers; globals persist between calls. |
capture_view |
Takes a screenshot of the 3D window as an inline image (Archicad 30+). |
run_python_script
These helpers are available in the script's globals:
| Name | Does |
|---|---|
tapir(name, params=None) |
Runs a Tapir command and returns its response dict. |
archicad(name, params=None) |
Runs an official command (API. is added when missing). |
run(name, params=None) |
Sends API.* to archicad and anything else to tapir. |
batched(items, size=1000) |
Splits long element lists into chunks. |
ArchicadError |
Raised by the helpers when a command fails. |
Assign to _ to return a value. Globals persist between calls:
# call 1
walls = tapir("GetElementsByType", {"elementType": "Wall"})["elements"]
# call 2
_ = len(walls) # `walls` is still bound
Every call returns {"stdout", "stderr", "result", "error"}. result is
_ itself when it's JSON-serialisable, otherwise its repr. error is a
traceback, or null when the script succeeded.
Command reference vs. installed Add-On
describe_command reads the latest published Tapir reference (cached for a
day), while list_commands asks your installed Add-On. If a command is
described but not listed, or a field is rejected as an
additionalProperties error, your Tapir is older than the reference.
Update Tapir.
Configuration
| Variable | Default | Purpose |
|---|---|---|
LAMCP_ARCHICAD_URL |
http://127.0.0.1:19723 |
The Archicad JSON API to talk to. |
LAMCP_ARCHICAD_COMMANDS_URL |
https://archicad-api.com/commands.json |
The Tapir command reference. |
LAMCP_ARCHICAD_CACHE |
~/.cache/lamcp-archicad |
Where the reference is cached. |
To set one with Claude Code, use -e:
claude mcp add lamcp-archicad --scope user -e LAMCP_ARCHICAD_URL=http://127.0.0.1:19724 -- uvx lamcp-archicad
Security
run_python_script runs arbitrary Python with your user's rights, like any
code Claude Code runs. The Archicad JSON API listens on 127.0.0.1 only and
has no authentication; that is Archicad's design, not ours.
Development
git clone https://github.com/gramaziokohler/lamcp-archicad
cd lamcp-archicad
uv venv && uv pip install -e ".[dev]"
ruff check . && ruff format --check .
pytest -q
The tests run against a fake Archicad (tests/), so you don't need
Archicad to run them.
To point Claude Code at your working copy instead of the published package:
claude mcp add lamcp-archicad --scope user -- uv run --directory /path/to/lamcp-archicad lamcp-archicad
Releases are tag-driven: push a v* tag and CI publishes to PyPI.
License
MIT
Metadata
Release files for lamcp-archicad 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lamcp_archicad-0.1.0.tar.gz | 139.9 kB | With provenance | Details for lamcp_archicad-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lamcp_archicad-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lamcp_archicad-0.1.0-py3-none-any.whl |
Total release size: 153.1 kB
Release files / lamcp_archicad-0.1.0.tar.gz
| Download URL | lamcp_archicad-0.1.0.tar.gz |
|---|---|
| Size | 139.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5b4f9ddc0017cfa473dca03e8f736a3bd46c5680351f3b1a75da594609ad955
|
|
BLAKE2b-256 checksum How to use checksums |
ff09af1f3490fe65c0c95d7cb001bbc54d515af305dbba19b5a456fca7208f02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logRelease files / lamcp_archicad-0.1.0-py3-none-any.whl
| Download URL | lamcp_archicad-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac961d4f5b94f95e069d7f8020f53c89a95f245afca9bd8615df5a2da361a5c0
|
|
BLAKE2b-256 checksum How to use checksums |
3e5c800cfc4d75e7271b1e3e53b4cd561c932df6d418cc29e23e9ff761f642e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logSecurity for lamcp-archicad 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for lamcp_archicad-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.