MCP.so
Sign In

CalderFlow MCP ServerVerifiedFeatured

@CalderFlow

Basic information

Transport

Streamable HTTP

Authentication

API Key

Last updated

Category

Media & Design

Author

CalderFlow

Submitted by

chloe liu

About CalderFlow MCP Server

Describe a process, decision or plan and CalderFlow draws an editable flowchart, decision tree, timeline, funnel or ER diagram, ready for your slides. The MCP server lets Claude, ChatGPT and other agents create and edit CalderFlow charts and returns a share link for each one.

#diagrams#flowchart#decision-tree#mermaid#er-diagram#presentation#visualization

Connection details

https://www.calderflow.com/mcp

Setup

claude mcp add calderflow --transport http https://www.calderflow.com/mcp

CalderFlow MCP Server tools

10

Create a presentation-ready flowchart or architecture diagram from Mermaid source. Use for branching processes, decision trees, and system architecture. Rules: start with 'flowchart TD' or 'flowchart LR'; solid arrows only (-->, optionally with |labels|); node shapes: A[Process] B{Decision} C([Start/End]). CalderFlow presents decisions as compact amber cards and terminals as green states, so use shapes semantically and do not add decorative classDef noise. CALIBRATE DETAIL: vague/ideation ask → 4-7 nodes, happy path + at most 2 essential decisions, NO subgraphs; detailed/spec-driven ask → subgraphs as phases, <=7 nodes per subgraph, <=18 nodes total (split the story into an overview plus detail chart beyond that). Consolidate checks that lead to the same outcome. If any subgraph is used, EVERY node—including starts, errors, and final outcomes—must be declared inside exactly one subgraph. Put internal edges inside their subgraph and cross-phase edges outside. Node labels 1-4 words; label every decision branch. Connect phases that hand off to each other. Returns the chart id + share URL. Give every node an icon with a %% nodeIcon <nodeId> <icon> line and mark the one step to remember with class <nodeId> keyStep (see the server instructions for icon names).

Create a sequential/chevron chart: a linear sequence of steps, phases, or stages (e.g. onboarding steps, project phases). NOT for branching logic — use create_flowchart for that. Include a 1-2 sentence description per step to make it presentation-ready. Aim for 4-6 steps: Presentation is one slide of at most 6. For a longer process, follow up with edit_chart set_presentation_steps choosing the 4-6 most important step IDs.

Create a funnel chart for filtering/narrowing processes where quantities reduce per stage (conversion funnels, pipelines). Include stage values when numbers are available; set conversionRates for proportional widths.

Create a lifecycle chart: phases across the top and milestones plotted on a curve. Each milestone has a level 1-10 setting its height — bell curves, S-curves, dips all emerge from levels. Use for product lifecycles, customer journeys, adoption/maturity curves. Every milestone needs a phaseId.

Create a timeline of events in chronological order (roadmaps, company history, sprint/release schedules). Every event needs a marker: supplied dates, relative time for a proposed plan, or Phase 1, Phase 2, etc. for an undated process. Never invent factual dates or measured durations. Include concise descriptions; group related events into eras.

Create an entity-relationship diagram (database schema / data model) with typed fields, PK/FK markers, and crow's-foot relationships. Entity names UPPER_SNAKE_CASE, 3-8 focused fields each.

Edit an existing chart. Call get_chart first to see its current spec, then pass tool_calls (surgical edits) and/or mermaid (full source replacement, flowchart/ERD only). A create_* tool call replaces the chart's data wholesale and can switch its type. Valid tool names — flowchart: style_chart, update_node, delete_node, add_node, connect_nodes, delete_edge, organize_sections, add_section, update_section, delete_section, move_node_to_section, set_node_icon ({nodeId, icon} or icon "none" to remove), set_key_step ({nodeId} or "none"); process/funnel/timeline/lifecycle: set_item_icon ({itemId, icon} or icon "none") and set_key_item ({itemId} or "none"), plus icon on add_* calls; any type: set_slide_text ({headline, takeaway}) for the Designed presentation slide and set_walkthrough ({steps:[{id, caption}]}) for the Walkthrough (a flowchart with 2+ sections walks one step per section, using subgraph IDs; otherwise use node or item IDs); chevron: create_chevron_chart, add_step, update_step, delete_step, reorder_steps, set_presentation_steps, style_chevron_chart; funnel: create_funnel_chart, add_funnel_stage, update_funnel_stage, delete_funnel_stage, reorder_funnel_stages, style_funnel_chart; lifecycle: create_lifecycle_chart, add_lifecycle_milestone, update_lifecycle_milestone, delete_lifecycle_milestone, update_lifecycle_phase, style_lifecycle_chart; timeline: create_timeline_chart, add_timeline_event, update_timeline_event, delete_timeline_event, reorder_timeline_events, style_timeline_chart; erd: create_erd_chart, add_erd_entity, update_erd_entity, delete_erd_entity, add_erd_attribute, update_erd_attribute, delete_erd_attribute, add_erd_relationship, update_erd_relationship, delete_erd_relationship, set_erd_direction, style_erd_chart (set_erd_direction takes {direction: "vertical"|"horizontal"}). For chevron Presentation-only selection/order edits, use set_presentation_steps with {stepIds:[up to 6 existing IDs in featured order]} (or null to reset to all); never reorder_steps, delete_step, or rename Full steps to change a Presentation summary. Use organize_sections with {sections:[{sectionId,title,nodeIds}], ungroupedNodeIds?} for a complete multi-section regroup; omitted nodes are placed with their closest connected section. Input shapes otherwise match the get_chart spec data (e.g. add_node takes {nodeId, label, shape?, connectFrom?, connectTo?}; style_chart takes {target: '<nodeId>'|'all', bgColor?, textColor?, borderColor?}).

Fetch a chart's current spec (JSON) and editable source text, plus its share URL.

List your CalderFlow charts (id, title, type, share URL), newest first.

Permanently delete a chart you own.

Overview

What is CalderFlow?

CalderFlow turns plain language into presentation-ready diagrams. Describe a process, a decision or a plan and it picks the right chart (flowchart, decision tree, process, funnel, timeline, lifecycle or ER diagram) and lays it out. Every chart stays editable: drag boxes, recolor, comment, or ask the AI for changes. Each chart has a Full view for the team and a clean Presentation view with a 16:9 copy-to-slide for PowerPoint, Google Slides and Keynote.

Charts are a structured spec rather than generated SVG, so your agent, the canvas and the CalderFlow AI all edit the same source.

Tools

  • create_flowchart: flowcharts and decision trees
  • create_chevron_chart: process steps
  • create_funnel_chart, create_timeline_chart, create_lifecycle_chart, create_erd_chart
  • edit_chart: targeted edits to an existing chart
  • get_chart, list_charts, delete_chart

Every response includes a share link that shows the live chart and opens it in the CalderFlow editor.

Connect

  1. Sign up free at https://www.calderflow.com/app
  2. Open the chart menu at the top left and choose Copy MCP URL
  3. Add that URL as a custom connector in claude.ai or Claude Desktop, or paste it into any MCP client config (streamable HTTP)

The key in the URL is shown once. Creating a new link replaces the old one.

Demo: https://youtu.be/CFjBFw_2fBk

Frequently asked questions

1

What is the CalderFlow remote MCP server?

The CalderFlow remote MCP server is a hosted Model Context Protocol endpoint at https://www.calderflow.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the CalderFlow MCP server?

Add the endpoint https://www.calderflow.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the CalderFlow MCP server require authentication?

Yes. CalderFlow requires an API key — check the official documentation for how to obtain one, then include it in your client's configuration.

4

Which transport does the CalderFlow MCP server use?

CalderFlow exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments