AI agents · MCP
Archboard runs a remote MCP server. Add it to your AI app, sign in with Google or GitHub, and choose what the agent can use. Its edits appear live next to your team, its cursor shows who it works for, and you can undo your agent’s change in one step.
https://getarchboard.app/mcpA scripted demo on the Archboard canvas, with sample names. The agent’s cursor shows who it works for, new shapes appear one by one, and a notice lets you undo your agent’s change in one step.
There’s no API key to paste: your AI app signs in to Archboard with OAuth, and you approve what it can use.
In your AI app’s connector or MCP settings, add Archboard as a remote MCP server with this URL. Some apps call it a custom connector.
https://getarchboard.app/mcpQuick setup for your app
These open your app with the Archboard server filled in. You confirm it there.
Opens in a new tabRun this in your terminal:
claude mcp add --transport http --scope user archboard https://getarchboard.app/mcpTo sign in, run:
claude mcp login archboardWhen your browser opens, sign in to Archboard and approve the app.
Don’t see your app? Copy the URL above into its connector or MCP settings. It needs OAuth sign-in without a client secret.
Some apps allow custom MCP servers on certain plans, or after an admin turns them on.
Archboard isn’t affiliated with these apps. Names and logos belong to their owners.
Your app opens Archboard. Sign in with Google or GitHub, pick the organizations and workspaces it can use, choose read, edit, or delete for each, and give it a name.
Ask your agent to draw or update a diagram, then open it in Archboard to watch the changes arrive live.
Try asking
Your AI app needs to support remote MCP servers with OAuth sign-in.
On the canvas
Your agent’s changes appear on the canvas as they happen, next to your team’s cursors. New shapes appear one by one as its cursor moves, and you can follow it around the canvas.
Its cursor shows the name you gave the connection and the person it works for, and the same name appears in change notices. Anyone watching through a public link sees the label too.
Right after your agent changes a diagram, a notice lets you undo your agent’s change in one step. You can also ask the agent to revert one of its own changes within 7 days. A field someone changed afterward is kept.
Agents add nodes from the same packs you use, so the result is a structured diagram you can keep editing.
With edit permission, your agent can add an image from a public https address, or a file from your computer in apps that can run commands. Archboard keeps only the processed image. Image metadata (location, camera, comments) is always removed.
In your control
When you approve an app, allow all your organizations and workspaces, including ones you join later, or only the ones you pick. Then choose read, edit, or delete for each. Delete only moves diagrams to the trash, where you can restore them.
Rename a connection, change what it can use, or remove it under Settings → Connected apps. Changes apply to its next call, with no reconnect.
An agent can’t do more than you can: your role and your plan limit it too. Apps that registered themselves are marked as unverified before you approve them.
Agent changes keep the app’s name in version history and in your organization’s audit log, which owners and admins can review on every plan.
MCP works on every plan, including Free, with the same plan limits as the editor. Agent tool calls also have a per-minute rate limit. On Free you edit live with your AI agents; editing live with teammates needs Pro or Enterprise seats.
AI apps that can add a remote MCP server with OAuth sign-in. Apps that require a client secret can’t connect. After you approve, Archboard sends you back to the app through an https address or a local (loopback) address on your computer. An app that returns through its own link scheme can finish connecting when Archboard allows that exact link; the developer guide lists them.
No. Apps connect with OAuth 2.1 through Archboard’s own authorization server: you sign in with Google or GitHub and approve the app. There are no API keys to create, paste, or rotate.
No. It can use only the organizations and workspaces you allowed, and in each only what the permission there and your role allow. A call outside them is refused.
Only where you gave it Delete permission, and only by moving a diagram to the trash, where you can restore it. An agent can’t delete a diagram permanently.
Open Settings → Connected apps and remove its access. It is disconnected right away, and the changes it already made stay in your diagrams, with the app’s name in version history.
For developers
A remote MCP server over Streamable HTTP, with OAuth 2.1 and PKCE from Archboard’s own authorization server, Client ID Metadata Documents or dynamic client registration, and protected resource metadata. Diagrams use a public, versioned JSON format with published JSON Schemas.
Sign in with Google or GitHub. Free for a single seat. Upgrade when the team joins.