Chhart MCP Server

Connect Chhart MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for creating flowcharts and Sankey diagrams on chhart.app. The chhart mcp mcp server is what makes that connection.

What the server does

An MCP (Model Context Protocol) server that enables AI assistants like ChatGPT, Claude, and others to programmatically create flowcharts and Sankey diagrams on chhart.app.

• 🎨 Create Flowcharts - Generate flowcharts using Chhart's intuitive text-based DSL
• 📊 Create Sankey Diagrams - Build Sankey diagrams from flow data
• 📚 Syntax Help - Get comprehensive documentation and examples
• 🔗 Shareable URLs - All diagrams come with shareable chhart.app links
• 🚀 Easy Integration - Works with any MCP-compatible AI assistant
• 🌐 Dual Mode - Run locally (stdio) or remotely (StreamableHTTP)

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• create_flowchart — The create_flowchart tool exposed by this server
• create_sankey — The create_sankey tool exposed by this server
• get_syntax_help — The get_syntax_help tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

• Node.js 20 or higher - npm or yarn - An MCP-compatible client (Claude Desktop, Cursor, etc.)

Where it fits

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chhart MCP's toolset — create_flowchart, create_sankey, get_syntax_help — is a fair guide to whether it matches your workflow. It is maintained by alwank; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Chhart MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.