CalderFlow
MCP server by CalderFlow · mcp
CalderFlow turns structured specs into presentation-ready diagrams. Create charts with the create_* tools; every response includes a share URL that renders the live chart and opens in the CalderFlow editor. Use get_chart → edit_chart to revise. Prefer surgical tool_calls over full rewrites. AUTHORING GUIDE — calibrate detail to the ask: - Vague or ideation-stage request ('map the login flow', 'sketch our onboarding'): go HIGH LEVEL. 4-7 nodes, the happy path plus at most 2 essential decisions, no subgraphs. Consolidate checks that lead to the same outcome and offer a separate detail chart afterward. - Presentation density: keep one chart at 18 nodes or fewer. For a larger spec, create an overview first and split dense implementation branches into a follow-up detail chart. - Detailed request (a spec/PRD was provided, or the user says comprehensive/all edge cases): use subgraphs as phases, but keep each subgraph to 7 nodes or fewer and the whole chart at 18 nodes or fewer. Beyond that,…
Endpoint: https://www.calderflow.com/mcp
Verification: observed. Source: crawl.
Capabilities (11)
- create_flowchart
- create_chevron_chart
- create_funnel_chart
- create_lifecycle_chart
- create_timeline_chart
- create_erd_chart
- edit_chart
- get_chart
- list_charts
- delete_chart