Excalidraw MCP MCP integration for AI agents.
Connect AI agents to Excalidraw MCP through 2 structured actions, including read me and create view. Review authentication, inputs, workflows, and safety gui…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Excalidraw MCP integration exposes
The Excalidraw MCP Agent App exposes 2 provider-backed actions for design and developer tools work. Its current contract lets an authorized agent fetch the excalidraw element format guide and drawing tips from the mcp server and render a hand-drawn excalidraw diagram from a json array string of elements. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Excalidraw MCP account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Excalidraw MCP capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
read_meREADFetch the Excalidraw element format guide and drawing tips from the MCP server.
create_viewWRITERender a hand-drawn Excalidraw diagram from a JSON array string of elements.
INPUTS: elements
INPUT CONTRACTS
Know what the action needs before it runs.
create_view
elementsREQUIRED- A compact JSON array string of Excalidraw elements. Call read_me first for the element format and ordering rules.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Read Me
Fetch the Excalidraw element format guide and drawing tips from the MCP server. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
read_meControl Create View
Render a hand-drawn Excalidraw diagram from a JSON array string of elements. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_viewVerify with Create View
Render a hand-drawn Excalidraw diagram from a JSON array string of elements. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_viewSAFETY BOUNDARY
Operate Excalidraw MCP with explicit limits
- Authorize Excalidraw MCP with Custom credentials and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Excalidraw MCP rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Excalidraw MCP task completed successfully.
CONNECTION MODEL
Custom credentials
Excalidraw MCP uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Excalidraw MCP.