IcePanel

Only if an admin has turned that on. IcePanel documents that all editors and admins can set up MCP with read access by default, but write access is disabled by default for existing organizations and must be enabled by toggling OAuth write access on the AI settings page. The scopes reflect this split: landscape.read and landscape.write.

A paid one. IcePanel states the MCP server is only available on paid plans, with no free-tier access documented. Beyond the plan, access also depends on your role: editors and admins can configure MCP with read access, and write access requires the separate organization-level toggle described in the AI settings page.

IcePanel publishes an explicit unsupported list: creating diagrams, draft tools, version tools and comment tools. So an agent can add model objects, connections and decision records, but cannot create a diagram, work with drafts or versions, or post comments. That published negative is unusually clear for a connector.

IcePanel's own examples include what your landscapes are, details about any model object, what an API service is connected to, which technologies are most used in your system, what a given team owns, and whether an architecture reflects your decision records. The last one pairs the model with ADRs, which is the connector's most distinctive read.

Yes, for both reading and writing. The tool set includes listing ADRs and getting ADR details, plus creating and updating them. IcePanel names decision records in both its supported read tools and its write and delete tools, so an agent can check whether a design matches recorded decisions and then record a new one.

IcePanel names Claude, Claude Code, Microsoft Copilot Studio, Codex, Cursor and VS Code, and tells you to look for Custom MCP connectors support in your tool. Any client that supports remote MCP over OAuth should connect, but those six are the ones IcePanel says it has actually tested.