com.vithanco/vgraph-mcp

Create a CLD diagram as PNG image. A Causal Loop Diagram (CLD) is a Systems Thinking tool that maps feedback loops between variables, showing how a change in one variable causes changes in others. It reveals reinforcing dynamics (exponential growth or decline) and balancing dynamics (stabilisation toward equilibrium). You provide VGL (Vithanco Graph Language) code using the CLD notation and the tool renders it to an PNG image. ## Core Concepts A CLD consists of **variables** (called Stocks) connected by **causal links** with polarity: - **same** (`s`): when A increases, B increases; when A decreases, B decreases. Drawn as a solid arrow. - **opposite** (`o`): when A increases, B decreases; when A decreases, B increases. Drawn as a dashed arrow. A **feedback loop** is a closed chain of causal links returning to the starting variable: - **Reinforcing loop (R)**: even number of `opposite` edges (including zero). Drives exponential growth or decline — a snowball effect. - **Balancing loop (B)**: odd number of `opposite` edges. Drives the system toward equilibrium — a thermostat effect. ## How to Build a CLD 1. Identify the key variables (stocks) in the system — things whose value can increase or decrease. 2. For each pair of causally related variables, determine the polarity: does an increase in A cause B to increase (same) or decrease (opposite)? 3. Trace closed loops and classify them as reinforcing or balancing using the counting rule. 4. Give the diagram a title that frames the system boundary. ## VGL Syntax ``` vgraph <id>: CLD "<title>" { <nodes and edges> } ``` ### Node Types - `Stock` — a variable whose value changes over time (blue circle). Examples: Population, Revenue, Stress, Trust. ``` node <id>: Stock "<label>" ``` ### Edges CRITICAL: You MUST specify the edge type (`: same` or `: opposite`) on every edge. Both edge types connect Stock to Stock, so the type CANNOT be inferred — omitting it will cause an error. ``` edge <from_id> -> <to_…

Create a ConceptMap diagram as PNG image. A Concept Map defines the vocabulary of a domain through falsifiable propositions. It helps people align on exact wordings and shared understanding by stating facts as simple, readable sentences. You provide VGL (Vithanco Graph Language) code using the ConceptMap notation and the tool renders it to an PNG image. ## How to Build a Concept Map 1. Start with a Guiding Question (used as the graph title) — it determines what belongs on the map. 2. List all relevant concepts. 3. Connect every concept through relations. ALWAYS form readable propositions. 4. NEVER leave a concept unconnected. Every concept MUST connect to at least one relation. 5. Reuse relations when multiple concepts share the same relationship. ## VGL Syntax ``` vgraph <id>: ConceptMap "<Guiding Question>" { <nodes and edges> } ``` ### Node Types - `Concept` — a concept or term - `EmphasizedConcept` — a concept to highlight as especially important - `Relation` — a linking verb or phrase that connects concepts ``` node <id>: Concept "<label>" node <id>: EmphasizedConcept "<label>" node <id>: Relation "<label>" ``` ### Edges ``` edge <from_id> -> <to_id> ``` ALWAYS form the pattern: Concept -> Relation -> Concept. This creates a readable proposition. ## Reusing Relations When multiple concepts share the same relationship, reuse a single Relation node. No duplicate edges when reusing — create edges only where needed: **Multiple sources, one target:** ``` vgraph animals: ConceptMap "What are common pets?" { node dog: Concept "Dog" node cat: Concept "Cat" node isa: Relation "is a" node mammal: Concept "Mammal" edge dog -> isa edge cat -> isa edge isa -> mammal // Only ONE edge from relation to target } ``` Both "Dog is a Mammal" and "Cat is a Mammal" share one Relation node — only 4 nodes total. **One source, multiple targets:** ``` vgraph typography: ConceptMap "What defines a font?" { node font: Concept "Font"…

Create a IBIS diagram as PNG image. IBIS (Issue-Based Information System) maps out any decision, discussion, or thought process using just four node types: Questions, Answers (Ideas), Pros, and Cons. Attaching Questions to any node lets you drill into any aspect at any depth. You provide VGL (Vithanco Graph Language) code using the IBIS notation and the tool renders it to an PNG image. ## How to Build an IBIS Diagram 1. Start with a root Question (used as the graph title). 2. Add Answers (Ideas) that respond to the question. 3. Add Pro and Con arguments for each answer. 4. Attach further Questions to any node to drill deeper. 5. Keep going until the topic is explored to the depth you need. ## VGL Syntax ``` vgraph <id>: IBIS "<title>" { <nodes and edges> } ``` ### Node Types - `Question` — a question or issue to explore (purple, question mark icon) - `Answer` — an idea or proposed answer (amber, lightbulb icon) - `Pro` — an argument in favour of an answer (green, thumbs up icon) - `Con` — an argument against an answer (red, thumbs down icon) ``` node <id>: Question "<label>" node <id>: Answer "<label>" node <id>: Pro "<label>" node <id>: Con "<label>" ``` ### Edges Edge types are inferred from node types — just write `edge <from> -> <to>`. Valid connections: - Question -> Answer (answering the question) - Answer -> Pro (supporting argument) - Answer -> Con (opposing argument) - Question -> Question (sub-question of a question) - Answer -> Question (answer raises new question) - Pro -> Question (pro raises new question) - Con -> Question (con raises new question) ``` edge <from_id> -> <to_id> ``` ## The Drill-Down Mechanism The power of IBIS is that you can attach a Question to **any** node type: - Question a Question: "Shouldn't we rather discuss X?" - Question an Answer: "What would we need to implement this?" - Question a Pro: "Is this advantage really significant?" - Question a Con: "Can we mitigate this disadvantage?" Each sub-question starts…

Create a Timeline diagram as PNG image. A Timeline visualises events over time, optionally across multiple parallel tracks (groups). The default layout is left-to-right but can be changed to any direction. The base notation provides generic TimePoint and Event types — use `vnotation extends Timeline` to define domain-specific event types (e.g. Battle, Treaty, Release, Incident) with custom colours and categories. You provide VGL (Vithanco Graph Language) code using the Timeline notation and the tool renders it to an PNG image. ## Core Concept: alignGroup The key mechanism is the `alignGroup` attribute. Nodes sharing the same `alignGroup` value are placed at the same position in the layout — pinned to the same column (left-to-right) or the same row (top-to-bottom). This is what creates time alignment. ``` node t1800: TimePoint "1800" [alignGroup: "1800"] node e1: Event "Something happened" [alignGroup: "1800"] ``` These two nodes will appear at the same horizontal position because they share alignGroup "1800". ## How to Build a Timeline 1. Choose a title that describes the scope of the timeline. 2. Decide whether you need TimePoints (axis markers) or whether alignGroup alone suffices. 3. Add Events for things that happened, each with an `alignGroup` matching its time. 4. Use `sequence` edges between TimePoints to form the visible time axis. 5. Use `influence` edges between Events to show causal or contextual links. 6. Optionally use groups to create named parallel tracks (countries, teams, systems). ## VGL Syntax ``` vgraph <id>: Timeline "<title>" { <nodes, edges, and groups> } ``` ### Node Types - `TimePoint` — an axis marker (date, phase, milestone label). Small gray box. Optional. - `Event` — something that happened. Steel-blue rounded box. ``` node <id>: TimePoint "<label>" [alignGroup: "<time_value>"] node <id>: Event "<label>" [alignGroup: "<time_value>"] ``` ALWAYS include `alignGroup` on every node to ensure correct time alignment. ### Edg…

Return the self-describing Markdown document for a built-in VGraph notation. The document includes the notation's purpose, when to use it, node types, edge types, history, and references.