rebuild-dossier
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode (default 8080). | 8080 |
| GROQ_API_KEY | No | GROQ API key for vision-assisted page classification (optional). | |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP mode authentication (required if using HTTP). | |
| MCP_ALLOWED_HOSTS | No | Comma-separated allowed hostnames for DNS rebinding protection (required if using HTTP). | |
| REBUILD_DOSSIER_ALLOWED_PATHS | No | Comma-separated absolute directories the server can access (required if using HTTP). | |
| REBUILD_DOSSIER_ENABLE_VISION_CLASSIFICATION | No | Set to '1' to enable vision classification (requires GROQ_API_KEY). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ingest_repoA | Parse package.json, tailwind/vite config, route files, and existing tests via static analysis. No LLM call. |
| crawl_siteB | Playwright headless crawl of reachable routes. Emits periodic progress notifications. |
| flag_known_bugA | Record a known bug. Always overrides auto-resolve for any case it matches, regardless of other evidence. |
| get_case_queueB | Return unresolved ambiguity cases from reconciliation. |
| resolve_caseA | Resolve one open case with a human decision. Always available, no elicitation capability required. |
| generate_specA | Write CLAUDE.md, .claude/, spec/, tests/, and kickoff-prompt.txt to -rebuild/. Only callable once the case queue is empty. Optional: if the target is a Next.js app with page routes, set GROQ_API_KEY and REBUILD_DOSSIER_ENABLE_VISION_CLASSIFICATION=1 before calling this tool to enable vision-assisted page-content classification (sends each captured page's screenshot and source code to Groq to judge static vs. dynamic content more accurately than plain regex matching) — ask the user for a Groq API key if they want more reliable generated page tests and this isn't already configured. Off by default; nothing changes if unset. Optional: pass authStorageStatePath to reach auth-gated pages during capture — see that field's own description for how to produce it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct role in the pipeline: static repo ingestion, dynamic site crawling, recording a known bug override, listing unresolved cases, resolving a case, and generating the final dossier. There is no functional overlap or ambiguity between tool boundaries.
All six tool names follow the same snake_case verb_noun convention, such as ingest_repo, crawl_site, get_case_queue, and generate_spec. The verb choices are specific and the object naming is consistent, making the set predictable and easy to navigate.
Six tools is a well-scoped size for this workflow, covering ingestion, crawling, bug flagging, case management, and final generation without redundancy. Each tool maps to a necessary step in the rebuild-dossier process and fits comfortably within the ideal range.
The main workflow is well covered: static analysis, dynamic crawling, human-in-the-loop case resolution, and final spec generation are all present. A minor gap is that there is no tool to list or remove previously flagged known bugs, but this does not prevent completing the core pipeline.