iArchi1. Connect your account
- Open iArchi sign-in and sign in with Google. Cloud models belong to the authorized account or organization workspace.
- In a client that supports custom remote MCP connections, add the endpoint below. Choose OAuth authorization when prompted; you do not need an iArchi API key.
- Follow the browser sign-in and consent flow. Check which iArchi account you are authorizing, review the access shown, then allow the connection if you want to proceed.
- Return to your AI client and ask it to list your models or create a new model.
https://mcp.iarchi.cloud/mcpConnection menus and availability vary by client, account and release. If your client does not offer a custom remote MCP connection, use the iArchi web app to work with your models directly.
2. Start with a model
Start with a saved model or ask for a new one. This example requests new model content; choose a separate model when experimenting.
Create a new iArchi model called Order fulfillment. Add a Fulfill order business process and an Order API application service that serves it. Create an Order overview view showing both elements and their serving relationship. Open that view.After the operation, inspect the returned results and the actual canvas. You can then request a check without changing the model:
Read Order overview in Order fulfillment. Explain the saved relationship and check the view for overlapping shapes. Keep the model unchanged.Keep using the same saved model in later conversations. Elements and relationships are model content; views arrange selected elements on a canvas. Removing a shape from a view is different from deleting its underlying element.
3. Permissions and data
An OAuth connection acts as the signed-in iArchi account. It can access only workspaces that account is permitted to use. Modeling tools include operations that create, update and delete content; review your client’s confirmation prompts before approving changes.
Architecture content returned by tools is received by the connected AI client. Choose what you include in a model accordingly, and review both iArchi’s privacy policy and the client provider’s data policies.
iArchi operates on saved architecture models. It cannot read a local source-code directory, run commands on your laptop, deploy infrastructure or query an external production database. Supply appropriate architecture information if you want to model a system.
To stop a connection, disconnect iArchi in the client’s connection settings. Account deletion is a separate support process.
4. Client compatibility
Remote tool access, embedded UI and file downloads are separate client capabilities. A working MCP connection does not guarantee that every client can show the canvas or deliver files in the same way.
| Client or capability | Current scope |
|---|---|
| ChatGPT Web | The dedicated development connection has been exercised with real model reads, edits and an embedded architecture canvas. Availability still depends on the ChatGPT account and connection surface. |
| Desktop and mobile clients | Behavior varies by client and version. Tool access, canvas display and downloads must be verified separately; identical behavior across platforms is not promised. |
| Other remote MCP clients | The client needs remote MCP transport and OAuth support for tool access. An embedded canvas also needs a compatible MCP Apps or Extensions UI surface. A client name alone does not establish full compatibility. |
The web app provides another way to open your saved model when the host cannot display an embedded canvas.
5. Export your architecture
Archi XML export includes the entire selected model: all elements, relationships, properties and views. Each diagram is translated to nonnegative coordinates for Archi compatibility. Ask the agent to return the exported XML directly if the host cannot deliver a downloadable file.
The canvas supports PNG and SVG exports. Where the host supports native downloads, it can deliver the file directly. Otherwise iArchi can prepare a private, temporary download link. The link grants access to that export until it expires, so share it only with intended recipients.
MCP image exports include links to the original PNG or SVG bytes and their SHA-256 hashes. Snapshots normally expire after 24 hours; downloading does not extend that period. Export the saved view again when a link expires. PNG is intended for image previews; SVG remains available as a vector file download.
Image generation and file delivery can fail independently. If an image cannot be generated, open the same saved view in the web app and retry the export. If only delivery is unsupported, use the offered temporary link or export from the web app.
6. Modeling tool reference
This list is rendered directly from the modeling tool registry used by the service. Account, workspace discovery and UI entry tools are separate from this modeling list. The client discovers each tool’s input and output schema over MCP.
A completed batch may contain individual failures. Check each item’s result before reporting that every operation succeeded.
Show the 26 modeling tools
| Tool | Purpose | Effect |
|---|---|---|
queryArchitecture | Run one raw read-only SQLite query within the authenticated account. Core tables: ArchitectureModel, ArchitectureElement, ArchitectureRelationship, ArchitectureView, ArchitectureViewNode, ArchitectureViewConnection; elements and relationships use kind. Use sources to join authorized workspaces. Paths and account identifiers are not accepted. | Read only |
diagnoseArchitectureViewGeometry | Inspect persisted view geometry for deterministic overlap, containment, crossing, and bounds issues. | Read only |
createArchitectureElements | Create Architecture elements in input order. Use a concrete ArchiMate element type ID from the type enum; display names are not accepted as IDs. | Changes model |
updateArchitectureElements | Update Architecture elements in input order. | Changes model |
deleteArchitectureElements | Delete Architecture elements in input order. | Changes model |
createArchitectureRelationships | Create Architecture relationships in input order. Reuses an existing relationship when source, target, canonical type, trimmed name, and properties match; otherwise creates a new relationship. Use a concrete ArchiMate relationship type ID from the type enum; display names are not accepted as IDs. | Changes model |
updateArchitectureRelationships | Update Architecture relationships in input order. | Changes model |
deleteArchitectureRelationships | Delete Architecture relationships in input order. | Changes model |
createArchitectureView | Create one Architecture view. | Changes model |
updateArchitectureView | Update one Architecture view. | Changes model |
deleteArchitectureView | Delete one Architecture view. | Changes model |
setArchitectureViewNodeParents | Set or clear parent nodes in input order. | Changes model |
upsertArchitectureViewNodes | Create or update view nodes in input order. | Changes model |
moveArchitectureViewNodes | Move view nodes to absolute canvas positions in input order. | Changes model |
resizeArchitectureViewNodes | Resize view nodes while preserving absolute positions. | Changes model |
deleteArchitectureViewNodes | Delete view nodes in input order. | Changes model |
upsertArchitectureViewConnections | Create or update view connections in input order. | Changes model |
routeArchitectureViewConnections | Persist caller-supplied routes for selected view connections. | Changes model |
deleteArchitectureViewConnections | Delete view connections in input order. | Changes model |
alignArchitectureViewNodes | Align selected view nodes. | Changes model |
distributeArchitectureViewNodes | Distribute selected view nodes. | Changes model |
applyArchitectureLayout | Apply a persisted layout algorithm to a view. | Changes model |
autoRouteArchitectureView | Automatically route view connections. | Changes model |
exportArchitectureViewImages | Render and persist native PNG/SVG snapshots. Return exact-file HTTPS links with expiry and byte hashes, and embed each image in the MCP response for clients that support inline images. PNG is suitable for visual inspection; SVG is also available as the original vector file. Snapshots normally expire after 24 hours. | Creates export |
importArchiXml | Import an ArchiMate Exchange XML model into the selected model. Defaults to merging by stable XML identifiers: update matching concepts and views, add new objects, retain unrelated content. Supports element and relationship properties. All changes are atomic and respect view capacity and revision conflicts. | Changes model |
exportArchiXml | Export the entire selected model as ArchiMate Exchange XML, including all elements, relationships, properties and views. Each diagram is translated to nonnegative absolute coordinates for Archi compatibility; stored canvas coordinates are unchanged. | Read only |
7. Troubleshooting
- The connection asks me to sign in again
- Check the account shown during consent. Reconnect through the client if authorization has expired or been removed. Do not paste tokens or passwords into a conversation.
- My expected model is missing
- Check the signed-in iArchi account and selected personal or organization workspace. Ask the agent to list accessible models before creating another one.
- The tool works but the canvas does not open
- The host may lack the required UI surface or restrict its availability. Open the saved model in the web app and check the client’s version and connection support.
- The view changed but I am still looking at the old view
- Select the new view from the canvas view list. If the host has not refreshed the embedded panel, reopen the model; the saved model remains the source of truth.
For help, contact iArchi support with the client name and version, the action attempted and the error text. Remove credentials and private model content from screenshots.