One Reference, One Request: Building an Evidence-Isolated Design Analysis MCP

Description and use

Secret MCP processes each design reference independently, producing a dedicated DESIGN_INDEX file that preserves attribution and detailed design evidence.

Problem

Screenshot‑to‑code workflows mix multiple design references in a single prompt, making it hard to trace which reference supports each design decision.

Outcome

The pipeline successfully generated separate design documents for each reference, preserving attribution and preventing cross‑reference contamination. Evidence images were tiled, resized, and color‑measured to keep payloads manageable.

Workflow

• Search for eligible design references
• Prepare desktop and mobile evidence for the first reference
• Send a sampling/createMessage request with includeContext:none
• Save the resulting DESIGN_INDEX markdown file
• Repeat the process for the next reference

Evidence

The live smoke test used two sampled references. Each request contained its own reference ID, zero occurrences of the other sampled ID, its own visual evidence, and includeContext: none. Two requests produced two Markdown files.

Source

A preserved three-reference run recorded the following descriptive measurements: ... 19/19 heading result measures structural completeness, not factual correctness.

Source