Documentation
Arch Studio, inside your agent.
Task routing, discovery order, and execution boundaries for architecture and AEC agents.
When to use this
Reach for Arch Studio when a user needs architecture-specific research or delivery: NYC property due diligence, site and zoning findings, workplace space programs, FF&E candidate comparisons and schedules, material specifications, EPD analysis, or durable meeting and project records. Select the narrowest relevant workflow. For unrelated general questions, continue using the host’s native capabilities.
How to call Arch Studio
Connect and authorize the MCP. Initialize using the protocol version supported by your client and the server; complete the MCP initialization lifecycle. Use tools/list to discover the current release. Call as_search_catalog with a short task query to find workflow instruction tools and supporting resources. Use the exact sourceDigest returned when reading resources with as_read_resource or continuing a release-bound workflow. Do not guess tool names or resource digests.
A workflow tool can return instructions rather than a completed deliverable. The host carries out the instructions with its available tools, obtains approvals when required, and writes durable results into the user-authorized workspace. Missing source access, an unavailable operation, or insufficient project context must be reported rather than silently fabricated.
Boundaries
Code and standards references require applicable jurisdiction, edition, project conditions, and source evidence. Do not describe retrieval alone as a compliance determination. Arch Studio does not replace professional review. Do not assume that two hosts share project memory because both connect to the same MCP.