Eraser MCP
Eraser MCP lets agents generate, create, read, search, update, export, and organize technical diagrams and documents in an Eraser workspace.
Verdict
Common use cases
- Generate architecture diagrams from design docs
- Convert meeting notes into flowcharts
- Pull diagram context into technical reviews
- Update documentation visuals during sprints
- Sketch system designs from chat descriptions
Integration
- Vendor
- Eraser MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
eraser_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Eraser MCP in the list and click Connect. 3. You'll be redirected to Eraser's OAuth consent screen — sign in with your Eraser account. 4. Review the requested scopes (typically read and write access to diagrams and documents) and click Authorize. 5. Switchy redirects you back and confirms the connection is active. 6. Open any Project and type '@Eraser' in the chat — your AI can now interact with your Eraser workspace. 7. Test it by asking '@Eraser list my recent diagrams' or '@Eraser create a simple flowchart for user login'. 8. If the response includes diagram data or confirmation of creation, the integration is working. 9. To revoke access later, visit your Eraser account settings and remove Switchy from connected apps.
What teammates see: by default, memories from Eraser MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Diagram System Architecture
@Eraser create an architecture diagram showing our API gateway, three microservices (auth, billing, notifications), a PostgreSQL database, and a Redis cache. Show request flow from client to gateway to services.
List Recent Diagrams
@Eraser show me the five most recent diagrams in my workspace. Include their titles and last modified dates.
Convert Notes to Flowchart
@Eraser take these steps and create a flowchart: user submits form, validation runs, if valid send to payment processor, if payment succeeds send confirmation email, if fails show error message.
Update Existing Diagram
@Eraser find the diagram titled 'User Onboarding Flow' and add a new step after email verification: phone number confirmation with SMS code.
Explain Diagram Context
@Eraser retrieve the diagram named 'Payment Processing Architecture' and summarize the components and their relationships for our onboarding doc.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@eraser show me all the architecture diagrams in our workspace that were updated in the last two weeks
Found 4 diagrams matching your criteria: 1. **Payment Service Architecture** (updated 3 days ago) — shows API gateway, database connections, and external payment provider integrations 2. **User Auth Flow** (updated 5 days ago) — sequence diagram covering OAuth flow and session management 3. **Microservices Overview** (updated 9 days ago) — system context diagram with 12 services and their dependencies 4. **Database Schema v2** (updated 12 days ago) — entity-relationship diagram for the new user profile tables Each diagram includes version history and contributor annotations. This is an illustrative example; actual results depend on your workspace's diagram library.
Demonstrates read access to Eraser's diagram repository. Requires OAuth scope that permits reading workspace content. Useful for auditing documentation freshness or finding reference materials during design reviews. Response format will vary based on Eraser's API structure.
@eraser create a new sequence diagram called 'Checkout Flow v3' showing the interaction between our frontend, API gateway, inventory service, and payment processor
Created **Checkout Flow v3** in your workspace. The diagram includes: - Four participants: Frontend (React), API Gateway, Inventory Service, Payment Processor - Seven interaction steps covering cart validation, stock check, payment authorization, and order confirmation - Return paths for error scenarios (out of stock, payment declined) Direct link: [View diagram in Eraser] Note: This is a starter structure based on your description. You'll likely want to refine timing, add conditional branches, or annotate with specific API endpoints in the Eraser editor.
Shows the MCP's ability to generate new diagrams from natural language descriptions. The AI interprets your requirements and structures them into Eraser's diagram format. Requires write permissions. The initial output is a foundation — expect to iterate in Eraser's UI for production-quality diagrams.
@eraser review all diagrams tagged 'authentication' and summarize which ones are outdated based on our current OAuth2 implementation
Reviewed 6 diagrams tagged 'authentication': **Outdated (3):** - **Login Flow 2022** — still shows deprecated session tokens instead of JWT - **SSO Integration** — references old identity provider endpoints that changed in Q3 - **Password Reset** — missing the new 2FA verification step added last month **Current (3):** - **OAuth2 Authorization Flow** — matches production implementation - **Token Refresh Logic** — accurate as of last security audit - **MFA Setup Process** — reflects current user onboarding Recommendation: Archive or update the three outdated diagrams to prevent confusion during onboarding. This analysis is illustrative; accuracy depends on diagram metadata and your system's actual state.
Combines the MCP's diagram access with the AI's reasoning to perform documentation audits. Particularly valuable when technical debt accumulates in visual documentation. Requires the AI to cross-reference diagram content against described implementation details you provide in the conversation context.
Use-case deep-dives
When Eraser MCP fits async architecture documentation
A 6-person engineering team shipping microservices needs to keep architecture decision records current without blocking on meetings. Eraser MCP works here if your team already uses Eraser for diagramming and you want AI to pull context from those diagrams during planning threads. The OAuth2 flow means each engineer authenticates once, then Switchy can reference their shared diagrams when drafting ADRs or sprint docs. The threshold: if your team doesn't already live in Eraser, the setup cost outweighs the benefit—you're better off with a filesystem or GitHub MCP pointing at markdown ADRs. If Eraser is your single source of truth for system diagrams, this MCP closes the loop between visual design and written decisions.
Eraser MCP for onboarding knowledge retrieval
A 3-person startup onboarding its first customer success hire needs to surface internal process diagrams without manual handoff. Eraser MCP lets Switchy pull flowcharts and system maps into onboarding prompts, so the new hire asks questions and gets answers grounded in the actual diagrams the founders drew. This works when your onboarding knowledge is visual—network topologies, user flows, data pipelines—and already lives in Eraser. The trade-off: if your onboarding docs are mostly text or live in Notion, you're adding a dependency for marginal gain. The buying call is simple: if your team draws to think and those drawings answer 30% of onboarding questions, connect Eraser. Otherwise, skip it.
When this MCP wins for early-stage spec feedback
A 5-person product team reviews technical specs before engineering starts, and half the feedback is about system boundaries shown in diagrams. Eraser MCP helps if your specs reference Eraser diagrams and you want AI to check consistency—does the proposed API match the service map, does the data flow align with the ERD. The OAuth2 setup means each reviewer authenticates once, then Switchy can cross-reference diagrams during spec threads without context-switching. The boundary: if your specs are prose-heavy or your diagrams live in Miro or Figma, this MCP doesn't apply. If Eraser is where your team draws system truth and specs reference those drawings by URL, this MCP turns diagram context into reviewable feedback.
Frequently asked
What does the Eraser MCP do in Switchy?
The Eraser MCP connects Switchy to your Eraser workspace, letting AI assistants read and reference your technical diagrams, architecture docs, and design files. Your team can ask questions about system designs, generate documentation from diagrams, or pull context from Eraser boards directly into conversations without switching apps.
Does Eraser MCP require OAuth or can I use an API key?
Eraser MCP uses OAuth2, so you'll authenticate through Eraser's standard login flow when you connect it in Switchy. This means you don't need to generate or manage API keys manually. The OAuth flow will request permissions to access your workspace diagrams and boards on your behalf.
Can the Eraser MCP create or edit diagrams?
Not yet. The current integration focuses on reading and referencing existing Eraser content. Your AI assistants can pull information from diagrams and boards, but they can't modify files or create new diagrams. If you need to update a diagram, you'll still do that directly in Eraser.
How is this different from just opening Eraser in another tab?
The MCP brings Eraser content directly into your AI conversations as context. Instead of manually copying diagram details or switching between tabs to reference architecture docs, your assistant can pull that information automatically when answering questions. It's faster for technical discussions that reference multiple diagrams.
Who on my team should connect the Eraser MCP?
Anyone with access to your Eraser workspace can connect it. The integration will only surface diagrams and boards that the connecting user has permission to view in Eraser. If your team shares a workspace, one person connecting it gives assistants access to all shared content visible to that account.