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 all running Archicad instances that the server can connect to. Each instance is identified by a unique 'port' number. This 'port' is required to target any other command. |
| archicad_list_commandsA | Returns a comprehensive list of all available Archicad API commands and brief descriptions. STEP 1: Use this tool FIRST to search for the right command name for your task. Do NOT guess or hallucinate command names. STEP 2: Once you find the relevant command name, you MUST use the 'archicad_get_command_schema' tool to learn its exact required arguments. |
| 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 (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. |
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 4 tools
Each tool has a distinct purpose: one lists commands, one discovers instances, one retrieves schemas, and one executes commands. There is no overlap or ambiguity between them.
Tool names follow a consistent [prefix]_[verb]_[noun] pattern, but the prefixes vary ('archicad_' vs 'discovery_'), which is a minor inconsistency. Overall the naming is clear and predictable.
With 4 tools, the server is well-scoped. It provides just the right set for a meta-API bridge: discovery, schema lookup, and execution.
The toolset covers the complete workflow: list available commands, get schema for a command, discover instances, and execute commands with pagination support. No obvious gaps for its stated purpose.