Vision Driven Design (VDD) is an MCP server with 15 tools an agent can call, among them vdd_amend, vdd_clarify, vdd_clone. It answers at https://vdd.simonmak.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 3 of 4 times since 24 September 2026; the last check, on 8 November 2026, succeeded.
Bi-directional traceability for AI-assisted development: 8-phase spec-driven chain, 7 gates.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
vdd_amend | VDD Cross-phase: Plan a requirement-change cascade through the whole chain — identifies the highest affected level and returns the ordered steps to update downward V→S→T→SP→PL→TK and re-run affected gates (G1–G7). Read-only; returns the cas Inputs: description, projectRoot |
vdd_clarify | VDD Phase 4b: Clarify an existing spec — scans vdd/specs/<feature>/spec.md and returns the items to resolve: every [NEEDS CLARIFICATION] marker, [e.g.] placeholder, and happy-path acceptance criterion (AC) still needing an edge-case counter Inputs: feature, artifactFiles, projectRoot |
vdd_clone | Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + Payload + Postgres scaffold manifest (vdd/clone-manifest.json). Pass the domain as description. Write Inputs: description, statement, maxPages, timeoutMs, concurrency, crawl |
vdd_detect_environment | VDD Environment Detection: Report which tools/MCPs each VDD phase requires vs treats as optional — across the 8-phase pipeline (init through validate) plus the cross-phase helpers (amend, clone, inspect, get-next-task) — and which of the ho Inputs: availableTools, capabilities, projectRoot |
vdd_get_next_task | VDD Phase 7a: Read vdd/specs/<feature>/tasks.md and return the next uncompleted task (or a completion marker when none remain). Read-only; never edits tasks.md. Pass feature (the exact spec directory name). Use before each implementation se Inputs: feature, artifactFiles, projectRoot |
vdd_implement | VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instruction plus the impact-chain commit-message format. Read-only; the tool writes nothing — the host agent pe Inputs: taskId, artifactFiles, projectRoot |
vdd_init | VDD Phase 0: Generate constitution.md at the project root — the immutable tech stack, conventions, security constraints, naming rules, and banned patterns that every later phase obeys. Overwrites any existing constitution.md. Run this first Inputs: projectRoot |
vdd_inspect | VDD Cross-phase: Read-only inspection of the current project in one call — scope selects the view. scope="project" (default) returns the bidirectional V→S→T→SP→PL→TK traceability matrix across all vdd/ artifacts; scope="feature" returns per Inputs: scope, feature, artifactFiles, projectRoot |
vdd_plan | VDD Phase 5: Generate the technical blueprint under vdd/specs/<feature>/ — plan.md (component breakdown, AC coverage map, technology choices, verification toolchain), data-model.md (entities, indexes, migrations), and contracts/ (request/re Inputs: feature, projectRoot |
vdd_specify | VDD Phase 4: Generate vdd/specs/<id>/spec.md for one tactical action item — user stories, Always/Ask/Never boundaries, Given/When/Then acceptance criteria (AC), MoSCoW priorities, non-functional requirements, and impact verification. Overwr Inputs: feature, actionItemId, description, projectRoot |
vdd_strategize | VDD Phase 2: Produce research-backed strategy into vdd/strategy.md — strategic pillars, competitive analysis, and a risk register, resolved from the vision target-domain primers. Overwrites vdd/strategy.md. Requires vdd/vision.md; run after Inputs: availableTools, capabilities, researchFindings, projectRoot |
vdd_tactics | VDD Phase 3: Audit the existing codebase into vdd/tactics.md — repo audit, technical-debt assessment, gap analysis, MoSCoW-prioritized action items (A-001, A-002, …), dependency map, and infrastructure requirements. Overwrites vdd/tactics.m Inputs: projectRoot, artifactFiles, codebaseAudit |
vdd_tasks | VDD Phase 6: Break the plan into atomic test-first tasks in vdd/specs/<feature>/tasks.md — each references acceptance criteria (AC) and contracts, is sized S/M/L, and is marked [P] when parallelizable. Overwrites tasks.md. Requires plan.md; Inputs: feature, projectRoot |
vdd_validate | VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impact metrics vs targets, and 28 S&T assumption checks across 7 gates. Writes vdd/impact-report.generated. Inputs: feature, artifactFiles, projectRoot |
vdd_vision | VDD Phase 1: Expand a freeform vision statement into vdd/vision.md — Impact Model (Goal, Actors, Impacts), Stakeholder Map, Success Metrics (leading + lagging), Constraints & Boundaries, and Target Domains. Overwrites any existing vdd/visio Inputs: statement, projectRoot |
Every block below points at https://vdd.simonmak.com/api/mcp. Pick your client and copy.
claude mcp add --transport http vision-driven-design-vdd https://vdd.simonmak.com/api/mcp
{
"mcpServers": {
"vision-driven-design-vdd": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vdd.simonmak.com/api/mcp"]
}
}
}{
"mcpServers": {
"vision-driven-design-vdd": {
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"servers": {
"vision-driven-design-vdd": {
"type": "http",
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"context_servers": {
"vision-driven-design-vdd": {
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"mcpServers": {
"vision-driven-design-vdd": {
"serverUrl": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"mcpServers": {
"vision-driven-design-vdd": {
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}name: Vision Driven Design (VDD)
version: 0.0.1
schema: v1
mcpServers:
- name: Vision Driven Design (VDD)
type: streamable-http
url: https://vdd.simonmak.com/api/mcp{
"mcpServers": {
"vision-driven-design-vdd": {
"httpUrl": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"mcpServers": {
"vision-driven-design-vdd": {
"type": "http",
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}{
"mcpServers": {
"vision-driven-design-vdd": {
"url": "https://vdd.simonmak.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvdd.simonmak.com%2Fapi%2Fmcp&type=streamable_http&id=vision-driven-design-vdd&name=Vision%20Driven%20Design%20%28VDD%29
It answered our last check on 8 November 2026 in 200 ms. Over 4 checks since 24 September 2026 it answered 3. Status here comes from Neuronto's own probes, not from the publisher.
15, as returned by the server's own tools/list on 15 November 2026: vdd_amend, vdd_clarify, vdd_clone, vdd_detect_environment, vdd_get_next_task, vdd_implement, vdd_init, vdd_inspect, and 7 more.
It answered our last check on 8 November 2026 in 200 ms. Over 4 checks since 24 September 2026 it answered 3.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vdd.simonmak.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.simonplmak-cloud. Endpoint host: vdd.simonmak.com. ARD identifier: urn:air:io.github.simonplmak-cloud:mcp:vision-driven-design.
First indexed 24 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.