Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Concept Maps, IBIS, Causal Loop Diagrams and Timelines as images. Runs locally via WebAssembly.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.vithanco.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"vgraph": {
"command": "npx",
"args": [
"-y",
"@vithanco/vgraph-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http vgraph https://mcp.vithanco.com/mcpclaude mcp add vgraph -- npx -y @vithanco/vgraph-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vgraph": {
"url": "https://mcp.vithanco.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vgraph": {
"command": "npx",
"args": [
"-y",
"@vithanco/vgraph-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"vgraph": {
"type": "http",
"url": "https://mcp.vithanco.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"vgraph": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vithanco/vgraph-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.vithanco.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain vithanco.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.0.9) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, yontu
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Vithanco stands for Visual Thinking and Communication. It helps you think in a structured way by drawing typed network graphs. In a typed graph every node and every edge has a meaning of its own: in an IBIS map a Question, an Answer, a Pro and a Con are different things, and the notation says how they may be connected. The drawing becomes a way of reasoning, and a way of explaining that reasoning to someone else.
VGraph is the open-source engine behind it. It lays a typed graph out and draws it as SVG. The Vithanco Graph Language (VGL) is only the *how*: a small text format in which these diagrams are written down, stored and shared. The same Swift code runs natively and, compiled to WebAssembly, in the browser, in Obsidian, in VS Code and behind an MCP server, so a diagram looks the same everywhere.
vgraph decision: IBIS "Should we ship the plugin?" {
node q1: Question "Should we ship?"; node a1: Answer "Yes, soon"; node p1: Pro "Users have asked for it"; node c1: Con "Docs are still thin"; edge q1 -> a1; edge a1 -> p1; edge a1 -> c1; }
A notation is the vocabulary of a diagram: it fixes the node and edge types and how they look. Every document names one. These ship with VGraph: IBIS, BBS, Impact Mapping, Concept Map, Current Reality Tree, Evaporating Cloud, Future Reality Tree, Prerequisite Tree, Transition Tree, Attack-Defense Tree, Goal Tree, Causal Loop Diagram, Decision Tree, Timeline, C4 and Arithmetic. A document can also declare notations of its own. The VGL guide has the whole language.
| Web editor | vithanco.com/editor: write VGL, see the diagram, edit it on the canvas |
| Obsidian | obsidian-vithanco: a vgl code block becomes a diagram |
| VS Code | vscode-vithanco |
| MCP server | npx @vithanco/vgraph-mcp runs it locally; https://mcp.vithanco.com/mcp is hosted. Details |
| Command line | vgraph-cli, built from this repository |
| Swift package | the VGraph, VGLanguage and VGraphSVG libraries |
Two tiers, so a parser fix does not send you through a toolchain install:
swift build and swift test need nothing but a Swift 6.4 toolchain.just build, just test, the wasm smoke tests and the editor's browser tests also need Node, jq, binaryen, wabt, just and the Embedded Swift SDK that matches .swift-version.Install the toolchain with swiftly, then the SDK. One bundle holds both the plain and the -embedded SDK, and its version must equal .swift-version. The checksum is per release; take it from swift.org's WebAssembly guide.
V=$(cat .swift-version)
swiftly install "$V" && swiftly use "$V" swift sdk install "https://download.swift.org/swift-$V-release/wasm-sdk/swift-$V-RELEASE/swift-$V-RELEASE_wasm.artifactbundle.tar.gz" \ --checksum
just doctor lists what is missing; a missing SDK is reported but does not fail it.
just build # compile everything: wasm, command line, MCP server
just test # build, then the full suite: Swift, wasm smoke tests, editor browser tests just # everything else
For most changes swift test is the quick loop. The Obsidian and VS Code plugins are separate repositories; just plugins-setup clones them next to this one, and the build and test recipes use them when they are there.
VGraph is built as hexagons: a pure domain at the centre, ports that name each conversation with the outside, and adapters at the edge. The parser, the SVG renderer and the Graphviz layout are separate targets that know only the core. Why it is shaped this way and where a change goes are written down, as are the decisions behind the design (ADRs) and the visual rules (design guide).
Pull requests are welcome, and so are issues. Start with CONTRIBUTING.md.
Apache-2.0, see LICENSE. Third-party works, among them Graphviz and the DM Sans typeface, are listed in NOTICE. The Vithanco name and logo are not covered by the licence: the artwork is all rights reserved, and a fork should use a name and a logo of its own. See graphics/README.md for what is allowed.