Design & Creative Tools · Eraser MCP + Claude
Eraser MCP with Claude: Faster Technical Diagrams and Shared Documentation
The short answer
Claude works with Eraser through the Model Context Protocol (MCP). Once connected, Claude can search workspace content, generate technical diagrams, update structured documents and export diagrams when a user asks in natural language. Access follows the permissions your organisation sets, so people stay in control of what changes.
What is Eraser MCP?
Eraser is a workspace for creating and managing technical diagrams and structured documents. Teams use it to organise diagrams, keep track of versions and export visuals for presentations, reviews and documentation. It is built for collaboration, so engineers, product managers, architects and operations staff can work on the same material together. Many teams rely on it to keep system designs and process maps current.
How Claude connects to Eraser MCP through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. In plain terms, it works like a universal adapter between Claude and a tool such as Eraser. The organisation decides what Claude can see and do, and access is granted through the sign-in method the tool supports, which for Eraser is Dynamic Client Registration OAuth.
Once connected, Claude can typically search workspace content to find existing diagrams and documents, generate new diagrams from a written description, update parts of a document and export diagrams in the formats your team needs. A user might ask Claude to draft a system diagram from a short brief and then place it in the right folder.
Permissions and approvals keep people in charge. Access can be limited to specific workspaces and actions, so Claude reads only what it needs. Consequential changes, such as overwriting a published document, can be set to require a person's approval before they take effect.
What you can automate
Turning briefs into architecture diagrams
A product manager describes a new feature in a few sentences. Claude uses Eraser to generate a first-draft architecture diagram that engineers can refine. This shortens the time between a idea and a shared visual that the whole team can review.
Finding existing documentation quickly
Teams often lose time hunting for the latest diagram of a process. Claude can search workspace content by topic, name or owner and return the most relevant diagrams and documents, helping new joiners and busy staff find what is current.
Keeping process documents up to date
When a workflow changes, an operations lead can ask Claude to update the related section of a structured document and flag the diagram that needs revising. Changes can be routed for review before they are published.
Preparing visuals for reviews and audits
Before a governance meeting or audit, a compliance officer can ask Claude to gather the latest system diagrams and export them in the required formats. This saves manual effort and reduces the risk of sharing an outdated version.
Onboarding and training material
A training lead can ask Claude to generate simple diagrams explaining a tool or process, then update them as the process evolves. This keeps onboarding material consistent across teams and regions.
An end-to-end workflow: Change request to updated system diagram
TriggerA change request is approved in the IT service management system.
Claude reads the approved change request and identifies the systems affected.
Claude searches the Eraser workspace for the current diagrams covering those systems.
Claude drafts an updated diagram reflecting the change and places it in a review state.
The solution architect reviews and approves the draft in Eraser.
Claude exports the approved diagram and attaches it to the change record in the ticketing system.
OutcomeDiagrams stay aligned with live systems, reviews happen before publication, and audit trails show who approved each change.
How we set it up
Free automation audit
We review how your teams use diagrams and documents today and identify the workflows worth automating with Claude and Eraser.
Secure connection
We connect Claude to Eraser through its MCP server using Dynamic Client Registration OAuth, so sign-in follows your organisation's existing controls.
Workflow design
We design the end-to-end workflow across Eraser and your other systems, such as Microsoft 365, ticketing or CRM, with approval steps for consequential actions.
Testing with real cases
We test the workflow against past diagrams and documents to confirm accuracy, tone and access rules before anything goes live.
Launch and training
We launch with monitoring and audit logs in place, then train your team so they know how to request work from Claude and how to review its output.
Who benefits
- Engineering and architecture leads
- Faster first drafts of system diagrams and easier retrieval of current designs.
- Product managers
- Quicker translation of feature briefs into shared visuals for review.
- Operations and process owners
- Documents and diagrams that are updated when processes change, with review built in.
- Compliance and IT governance teams
- Consistent, exportable records of system designs for audits and reviews.
Security and control
- Least-privilege access, limiting Claude to the workspaces and actions each team needs.
- Human approval before consequential changes, such as publishing or overwriting documents.
- Audit logs that record what Claude read, created or changed.
- Testing against real past cases before launch, and ongoing monitoring afterwards.
- Clear guidance for staff on reviewing AI-generated diagrams before relying on them.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can apply their existing data protection and security standards to how Claude accesses Eraser. In India, the Digital Personal Data Protection Act, 2023 governs personal data, and we configure access accordingly. For organisations in the UAE and Saudi Arabia, local data protection laws shape where data is processed and who can access it. We can host the Claude application in India, the United States, the United Kingdom or the European Union to meet these requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Eraser MCP server do?
The Eraser MCP server acts as a secure bridge between AI tools like Claude and your Eraser workspace. Through it, approved AI agents can typically search content, generate diagrams, update documents and export visuals using natural language, within the access rules you set.
Is connecting Eraser to Claude secure?
Security depends on how the connection is configured. We use Dynamic Client Registration OAuth sign-in, least-privilege access and audit logs. Approval steps can be added for changes that matter. We also test the setup before launch so you can confirm it meets your internal policies.
What can Claude do with Eraser once it is connected?
Typically, Claude can search your workspace, generate diagrams from written descriptions, update parts of documents and export diagrams. The exact actions available depend on the permissions you grant and the workflow we design together.
How long does setup take?
Timing depends on how many workflows you want to automate and how many systems they involve. A focused setup for one team is often quicker than a company-wide rollout. We confirm a realistic timeline during the free automation audit.
Which plan or permissions do I need?
You need an Eraser workspace where your organisation can grant access through the supported sign-in method. The exact plan requirements are set by Eraser, so we check your current account and permissions during the audit.