ArchiBridge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCHIBRIDGE_POLICY | No | Controls which Archicad commands are allowed. Possible values: `readonly` (only reads run), `ask` (the default: reads and modifications run, restricted commands are refused), `full` (restricted commands run too; use only if you accept the risk of lost work). Set this environment variable in your MCP config to change the safety policy. | ask |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archicad_instancesA | Lists the running Archicads: port, version, open project, and Tapir add-on version. Call this first. status is "ready", "no_project" (nothing is open yet) or "busy". When tapir is null, only API.* commands work until the add-on is installed. |
| archicad_search_commandsB | Finds Archicad commands by words in their name, group or description. Examples: "wall", "property value", "mep port", "layout". Leave query empty to see the groups. minimumArchicad shows commands that need a newer Archicad. |
| archicad_command_schemaA | Returns a command's input and output schemas, with the definitions they refer to. Read this before the first call of any command. Definitions listed in moreDefinitions were left out to keep the answer short: pass one of those names here to read it. |
| archicad_readA | Runs a command that does not change the project. command: a Tapir name such as "GetStories", or a built-in such as "API.GetAllElements". parameters: the command's input object. port: only needed when several Archicads are ready. Also allowed: commands that only move the view, such as ChangeWindow and FitInWindow. |
| archicad_modifyB | Runs a command that changes the project, such as CreateWalls or SetDetailsOfElements. Send many items in one call instead of many calls. Results list one entry per item, and an item can fail on its own, so read the result. Restricted commands such as QuitArchicad and CloseProject are refused unless the user turned on the full policy. |
| archicad_view_imageA | Returns a picture of Archicad's current window, so you can check your work. Works for the 3D window and for 2D windows. Switch window first with ChangeWindow if needed. entire_drawing: in a 2D window, capture the whole drawing, not just the zoom. |
| archicad_get_skillC | Returns a working method. Skills: archibridge, archicad-mep-review. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: discovery (instances, search_commands), introspection (command_schema), execution (read vs. modify), visual verification (view_image), and guidance (get_skill). The read/modify split is explicit, and search vs. schema is separated by discovery vs. detail lookup. No two tools appear to do the same thing.
All names share the archicad_ snake_case prefix, but action conventions are mixed: search_commands, view_image, and get_skill use verb_noun form, read and modify are bare verbs, and instances and command_schema are noun phrases. The pattern is still readable but not predictable as a uniform verb_noun convention.
Seven tools is well-scoped for an Archicad command bridge. Each tool covers a necessary part of the workflow: setup/discovery, schema lookup, read execution, modify execution, visual checking, and skill guidance. No tool feels redundant or missing from the count.
The surface covers the full bridge lifecycle: finding Archicad instances, discovering commands, reading schemas, executing non-mutating and mutating commands, visually verifying results, and retrieving procedural skills. There are no obvious dead ends for the stated purpose, and read/modify support batch operations.