io.github.dushyant30suthar/endiagram-mcp

Official7 tools

by dushyant30suthar · JavaScript

EN Diagram — structural verification for concurrent systems. Pure math, no AI.

EN Diagram MCP Server (io.github.dushyant30suthar/endiagram-mcp)

EN Diagram MCP server provides deterministic structural verification for concurrent systems. It performs math-based analysis using graph theory and reports results tied to named mathematical theorems, with “No AI inside the computation.” The package exposes 7 tools.

🛠️ Key Features

Structural verification for concurrent systems
Deterministic analysis powered by graph theory
Results backed by named mathematical theorem(s)
Toolset: 7 tools
Package: @endiagram/mcp / npx @endiagram/mcp

🚀 Use Cases

Verify structural properties of concurrent systems
Perform theorem-backed analysis workflows in an MCP client

⚡ Developer Benefits

The computation is described as pure math (“No AI inside the computation”)
Named mathematical backing for each result
Runs via npx or can be installed globally

⚠️ Limitations

Described as “pure math” structural analysis; no AI computation is included

Declared in the repository manifest (tools.json). Not verified against a live endpoint.

structure

What is this system? Returns shape (Pipeline, Fork-Join, DAG, Star, Cycle, Tree, Complete, etc.), stages with roles, bridge nodes, cycles, parallelism, critical path, dominator tree, min-cuts, subsystems, interface nodes, actors (who does what, workload entropy), locations (where work happens, boundary crossings). Levers: node=X returns per-node centrality (betweenness, closeness, eigenvector) for a specific node. detect_findings=true flags named structural risks — unguarded-sink (sinks reachable via only pipeline actions, no JOIN/HUB gating), single-cut-path (source-sink pairs with only one vertex-disjoint path), multi-cut-path (paths with redundant defense, min-cut > 1). See server instructions for EN language syntax.

Parameters

No parameters.

invariant

What's always true — automatic findings and on-demand checks. Automatic outputs: conservationLaws (weighted entity sums constant across executions), sustainableCycles (T-invariants — action sequences returning to start state), depletableSets (entity groups whose simultaneous depletion is irreversible), behavioral.deficiency (0 means structure fully determines dynamics), behavioral.isReversible, behavioral.hasUniqueEquilibrium. On-demand via `rules`: encode domain-specific claims and verify them against the graph — this is how to check things the topology alone can't see (precedence, coverage, centrality bounds, resilience). See the rules parameter for supported sentence shapes.

Parameters

No parameters.

live

Can it deadlock? Can entities overflow? isStructurallyLive means every siphon contains a trap — no structural deadlock possible. uncoveredSiphons are entity groups that can drain permanently, with the actors and locations affected. isStructurallyBounded means no entity can accumulate without limit. unboundedCycles are action sequences that could cause overflow. See the server instructions for EN language syntax.

Parameters

No parameters.

reachable

Can X reach Y? Follows directed data flow first; falls back to undirected. `from` and `to` accept entity names or action names (resolved against the program). Path shows each step with actor and location. locationCrossings counts boundary transitions. defense_nodes checks if guards cover all paths; coverage.fullCoverage=false means unguarded routes exist. See the server instructions for EN language syntax.

Parameters

No parameters.

equivalent

Are two systems the same, or what changes if I change this one? Compare mode (source_a + source_b): structural differences, edit distance, spectral equivalence. isCospectral=true means identical graph structure up to relabeling — topologically the same despite different names, actors, or locations. Evolve mode (source + patch): dry-run a change, shows diff plus new/lost bridge nodes. Patch has three directive types — plain EN statement adds an action; a line starting with `-` (and not containing `do:`) removes the named action; a statement whose action name matches an existing one replaces the original. See the server instructions for EN language syntax.

Parameters

No parameters.

compose

How do parts combine, or how does a part stand alone? Merge mode (source_a + source_b + links): declare which entities in A are the same as entities in B; the combined graph is wired via string-equality of shared names. Extract mode (source + subsystem): pull a named subsystem out as standalone EN with boundary inputs/outputs, actors, and locations. Valid subsystem names come from structure's `subsystems` field — call structure on the source first to discover them. See the server instructions for EN language syntax.

Parameters

No parameters.

render

SVG or PNG diagram. Only call when user explicitly asks to visualize. The rendered image is delivered to the user, not injected into the model's context. See the server instructions for EN language syntax.

Parameters

No parameters.

README.md5 KBView on GitHub

@endiagram/mcp

MCP server for EN Diagram — deterministic structural analysis powered by graph theory. Every result is backed by a named mathematical theorem. No AI inside the computation.

Installation

Run directly:

bash

npx @endiagram/mcp

Or install globally:

bash

npm install -g @endiagram/mcp

Connect

Claude Code

bash

claude mcp add endiagram npx @endiagram/mcp

Claude Desktop

Add to your claude_desktop_config.json:

json

{
  "mcpServers": {
    "endiagram": {
      "command": "npx",
      "args": ["@endiagram/mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project root:

json

{
  "mcpServers": {
    "endiagram": {
      "command": "npx",
      "args": ["@endiagram/mcp"]
    }
  }
}

HTTP (zero install)

Any MCP client that supports HTTP transport:

code

https://api.endiagram.com/mcp

Smithery

bash

smithery mcp add dushyant30suthar/endiagram

Environment Variables

Variable	Default	Description
`EN_API_URL`	`https://api.endiagram.com`	API endpoint for the EN Diagram service

Tools

Six questions about any system, plus a render tool. Every tool takes source (EN code or .en/.txt file path). Tool names are shorthand, not specs — read each description before calling; compose and equivalent are mode-based, not general analyzers.

Tool	What it answers	Levers
`structure`	What is this system? Shape, stages, bridges, cycles, critical path, dominator tree, min-cuts, subsystems, actors, locations.	`detect_findings=true` flags risks (unguarded-sink, single-cut-path, multi-cut-path); `node=X` returns per-node centrality (betweenness, closeness, eigenvector).
`invariant`	What's always true? Conservation laws, T-invariants (sustainable cycles), depletable sets, deficiency, reversibility.	`rules` (one per line) checks custom claims. Four supported shapes: `no bridge that is also hub` · `every path from X to Y passes through at least one of [A,B,C]` (precedence) · `no node with centrality above N` · `removing any single node disconnects at most N others`.
`live`	Can it deadlock? Can entities overflow? Siphons, traps, unbounded cycles, structural liveness and boundedness.	—
`reachable`	Can X reach Y? Path, distance, boundary crossings. `from`/`to` accept entity or action names.	`defense_nodes=a,b,c` checks whether guards cover every path.
`equivalent`	Are two systems the same, or what changes if I change this one?	Compare mode (`source_a`+`source_b`): edit distance + spectral cospectrality. Evolve mode (`source`+`patch`): plain EN adds; `- name` removes; same-name replaces.
`compose`	How do parts combine (merge) or how does a part stand alone (extract)?	Merge: `source_a`+`source_b`+`links` (`a.entity=b.entity` per line). Extract: `source`+`subsystem` (names come from `structure.subsystems`).
`render`	SVG or PNG diagram. Only call when the user asks to visualize.	Themes: `Editorial`, `Primer`, `Carbon` (each ± `isDark`) or seed-derived from `color=#RRGGBB`. `structure_layers` bitmask (1=subsystems, 2=pipelines, 4=cycles, 8=forks, 16=joins, 32=hubs, 64=deadlock, 128=overflow).

EN Syntax

One statement per line:

code

actor do: action needs: input1, input2 yields: output1, output2

Shared names between yields and needs create connections automatically:

code

customer do: place order needs: menu yields: order
kitchen do: prepare food needs: order yields: meal
waiter do: deliver needs: meal yields: served customer

Modeling

Same name = same thing. Put all required inputs in one needs: list (AND). Give two actions the same yield-name to offer alternatives (OR). Sequence = one action consuming another's yield. Re-yield stateful resources to keep them persistent; one-shot data stays consumed. Model at the real atomic granularity — split only when the pieces could be accessed independently.

Learn more at endiagram.com.

Telemetry

@endiagram/mcp generates a random install ID on first run, stored at ~/.endiagram/install-id (mode 0600). It is sent with every request as the X-Endiagram-Install-Id HTTP header so we can correlate requests from the same install for debugging issues that the per-IP signal alone cannot track (mobile networks, VPNs, CGNAT all collapse or churn IPs).

No source code, no file paths, no environment variables, and no PII are sent. The install ID is a random opaque UUIDv4 generated locally.

A first-run notice prints to stderr (never stdout — stdout is the MCP JSON-RPC channel) with the disclosure and the opt-out instructions. The notice fires once per install and never again.

Opting out

Any of these three methods disables the install ID:

Set ENDIAGRAM_TELEMETRY=off as an environment variable (also accepts 0, false, no).
Create a file at ~/.endiagram/telemetry containing the word off.
Delete ~/.endiagram/install-id. (A new one is generated on next run unless option 1 or 2 is also set.)

When any of these is active, the X-Endiagram-Install-Id header is not sent at all — the server falls back to its per-IP HMAC cid for correlation, which works fine for short-term per-session tracing.

Full privacy policy: endiagram.com/privacy

License

MIT

Install

Tools (7)

structureinvariantlivereachableequivalentcomposerender

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "endiagram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@endiagram/mcp@0.3.16"
      ]
    }
  }
}

EN Diagram MCP Server (io.github.dushyant30suthar/endiagram-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

structure

invariant

live

reachable

equivalent

compose

render

@endiagram/mcp

Installation

Connect

Claude Code

Claude Desktop

Cursor

HTTP (zero install)

Smithery

Environment Variables

Tools

EN Syntax

Modeling

Telemetry

Opting out

License

Install

Related servers