Endiagram MCP vs Fantasy Draft
A side-by-side look at the Endiagram MCP and Fantasy Draft MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Endiagram MCP for developer tools work as a local process; choose Fantasy Draft for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Endiagram MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
EN_API_URL, ENDIAGRAM_TELEMETRY. - You want tools like
structure, invariant, live.
Choose Fantasy Draft when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
draft_board, best_available, player_outlook.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | EN_API_URLENDIAGRAM_TELEMETRY | None listed |
Tools & capabilities
Endiagram MCP tools 7
structureWhat 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.invariantWhat'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.liveCan 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.reachableCan 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.equivalentAre 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Endiagram MCP
{
"mcpServers": {
"endiagram-mcp": {
"command": "npx",
"args": [
"-y",
"@endiagram/mcp"
],
"env": {
"EN_API_URL": "YOUR_EN_API_URL_HERE",
"ENDIAGRAM_TELEMETRY": "YOUR_ENDIAGRAM_TELEMETRY_HERE"
}
}
}
}
Fantasy Draft
{
"mcpServers": {
"fantasy-draft": {
"url": "https://predictionmarketspicks.com/api/mcp-draft/mcp"
}
}
}
Frequently asked questions
Endiagram MCP is categorized under Developer Tools and uses a local stdio subprocess. Fantasy Draft belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Endiagram MCP for developer tools work and Fantasy Draft for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Endiagram MCP is listed as free. Auth: no auth required. Fantasy Draft has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add endiagram-mcp and fantasy-draft as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Endiagram MCP has a quality signal of 61/100 (Good) with 3 views, 0 installs and 8 GitHub stars. Fantasy Draft has 59/100 (Good) with 0 views, 0 installs and 0 GitHub stars.