Mermaid Chart MCP

@mermaid-chart create a sequence diagram showing the OAuth flow between our frontend, API gateway, and auth service

I've generated a sequence diagram illustrating the OAuth authorization code flow. The diagram shows your frontend initiating the request, the API gateway validating the client, the auth service issuing tokens, and the callback flow returning control. The chart includes decision points for token validation and error handling paths. You can view and edit the diagram at the provided Mermaid Chart link.

This example demonstrates diagram generation from natural language descriptions. The MCP translates your architectural intent into Mermaid syntax and renders it. Useful for documentation and design discussions, though you'll likely need to refine complex flows manually after the initial generation.

@mermaid-chart show me a flowchart for our user onboarding process, including the email verification branch and the skip-for-now path

Here's a flowchart mapping your onboarding flow. It starts with account creation, branches at email verification (with a 24-hour timeout condition), includes the optional skip path that limits feature access, and converges at the dashboard entry point. Decision nodes highlight where users can exit or loop back. The chart uses standard flowchart symbols for clarity.

Flowcharts work well for process documentation when you need to share logic with non-technical stakeholders. The MCP handles branching and decision logic, but complex conditional trees may require iterative refinement. No authentication needed since diagrams are generated ephemerally unless you save them to a Mermaid Chart account.

@mermaid-chart convert this ERD into a class diagram: we have Users, Projects, and Tasks tables with the relationships I described in the previous message

I've created a class diagram based on your entity relationships. The diagram shows User as a parent class with a one-to-many relationship to Project, and Project with a one-to-many relationship to Task. Each class displays the key attributes you mentioned (user IDs, project metadata, task status fields). The cardinality notation makes the foreign key relationships explicit.

This example shows the MCP's ability to reference prior conversation context when generating diagrams. Helpful for translating database schemas into visual documentation. The output assumes standard UML notation—if your team uses different conventions, you may need to specify those in your prompt for accurate representation.

When diagram-as-code beats slide decks for async design reviews

A 6-person engineering team spread across three time zones needs to document a microservices refactor without scheduling yet another Zoom. Mermaid Chart MCP is the right call here. Your team writes architecture diagrams in plain text—sequence flows, component maps, state machines—directly in Switchy threads, and the MCP renders them live. No Lucidchart logins, no export-to-PNG dance, no version drift between the diagram and the discussion. The trade-off: if your architects prefer freeform whiteboarding or need pixel-perfect layouts for executive decks, this won't replace Figma. But for teams that already live in markdown and want diagrams that update as fast as the conversation moves, this MCP closes the loop. Add it to your workspace if you're tired of stale PNGs in Notion.

Visualizing workflow bottlenecks without a dedicated tool

A product trio—PM, designer, engineer—runs a retro every two weeks and keeps hitting the same handoff delays. They need to see the process, not just talk about it. Mermaid Chart MCP works here because the team can sketch a flowchart of their current sprint cycle in a Switchy thread, spot the blockers (usually between design QA and dev kickoff), and iterate the diagram in real time as they brainstorm fixes. No separate diagramming subscription, no exporting to Miro. The limitation: if your retros involve 12 people and need collaborative cursor-dragging, a dedicated whiteboard tool has better real-time co-editing. But for small teams that want a quick visual artifact they can reference in the next sprint's planning doc, this MCP gets you there in under five minutes.

When support ops needs a single-source diagram that updates with the runbook

A 3-person support team handles 40 tickets a day and just added a new escalation tier for billing issues. They need the flowchart in the runbook to match reality, and they need it updated without opening a design tool. Mermaid Chart MCP is the move. The support lead writes the escalation logic as a Mermaid flowchart in the same Switchy thread where the team discusses edge cases, and the diagram updates as the policy evolves. The result lives in one place, not scattered across a Google Doc and a stale Lucidchart link. The boundary: if your escalation tree has 40 branches and needs conditional formatting or role-based views, you'll want a dedicated decision-tree tool. But for straightforward flows that change monthly and need to stay in sync with the conversation, this MCP keeps your docs honest.