# Ascent Partners Vision Driven Design MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fvision-driven-design
Registry id: `mcp-registry/com.ascent-partners/vision-driven-design`
Status: live (checked 2026-10-27T06:22:20.349Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 2805
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "ascent-partners-vision-driven-design-mcp": {
      "type": "http",
      "url": "https://vdd.simonmak.com/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http ascent-partners-vision-driven-design-mcp https://vdd.simonmak.com/api/mcp
```

## Tools (15)

- `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 downw
- `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.] placehol
- `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 sc
- `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 
- `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.
- `vdd_implement`: VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instruction plus the impact-cha
- `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 
- `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→
- `vdd_plan`: VDD Phase 5: Generate the technical blueprint under vdd/specs/<feature>/ — plan.md (component breakdown, AC coverage map, technology choices, verification toolc
- `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),
- `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 targ
- `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-00
- `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/
- `vdd_validate`: VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impact metrics vs targets, 
- `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),

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.