tapir-archicad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| discovery_list_active_archicadsA | Scans for and lists running Archicad instances. Returns 'active' (ready to receive commands with their target 'port') and 'unavailable' (instances that are unresponsive or missing the Tapir Add-On). |
| archicad_list_commandsA | Search by keyword phrases or exact command names. Batch separate workflow steps and narrow by groups as needed. For every follow-up on the same user request, pass the latest query_id from the previous response, even when replacing all keywords or changing groups. Omit query_id to start a new task or restart an unavailable chain. The matches list returns up to 12 pooled ranked command names with descriptions. An exact name in scope returns that name and its status in exact_matches by keyword_index. Omit keywords to browse names. Available groups: analytical, app, attributes, classifications, components, custom_data, design_options, dev, elements, favorites, grouping, ifc, issues, keynotes, layout, library, mep, navigator, project, project_data, properties, revisions, solid_ops, teamwork, view. Use archicad_get_command_schema before executing a selected command. |
| archicad_get_command_schemaA | Retrieves the exact JSON schema (required arguments) for a specific Archicad command. Provide the exact 'command_name' obtained from 'archicad_list_commands'. CRITICAL: You MUST call this tool before executing 'archicad_call_tool' to ensure you provide the correct parameters. Do NOT guess or hallucinate parameters based on the command name. |
| archicad_call_toolA | Executes a specific Archicad API command by its 'name'. CRITICAL WORKFLOW: You MUST use 'archicad_get_command_schema' first to understand the exact JSON structure required for the 'arguments' parameter. The 'arguments' dictionary MUST contain a 'port' number (obtained from 'discovery_list_active_archicads'). If a tool's response includes a 'next_page_token', call this same tool again with the same parameters and add a 'page_token' key to the 'arguments' dictionary. Long executions return status='running' and a jobHandle; retrieve them with archicad_get_job. If a response is lost or cancelled, list jobs with archicad_get_job() before retrying a write. Cancelling this request does not cancel an admitted execution. |
| archicad_get_jobA | With no job_handle, immediately lists all retained executions newest first, including fast, completed, and failed jobs, with command, port, timestamps, and a short argumentsPreview. Use this to recover after a lost response before retrying a write; similar calls may be ambiguous. With a job_handle, waits up to the configured threshold and returns running, completed with result, or failed with error. Polling never redispatches commands. |
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 5 tools
Each tool occupies a distinct step in a clearly prescribed workflow: discover instances, search commands, fetch a schema, execute, and poll jobs. The descriptions explicitly state prerequisites and boundaries, leaving no realistic chance of misselection.
Four tools share the archicad_ prefix with a verb_noun pattern (list_commands, get_command_schema, get_job, call_tool), but discovery_list_active_archicads uses a different prefix and the generic 'call_tool' noun is vaguer than its peers.
Five meta-tools is exactly the right scope for a proxy that exposes hundreds of underlying Archicad commands via dynamic search and schema lookup. Each tool is load-bearing; nothing is redundant.
The surface covers discovery, search, introspection, execution, pagination, and job retrieval, which is solid lifecycle coverage. Minor gaps exist: no way to cancel or delete jobs despite mentions of cancellation, and no batching/parallel execution helper.