@wraithwalker/mcp-server

Restore a human-facing captured projection file from its canonical hidden snapshot

Copy selected projection-backed captured files into a local projection workspace for same-machine agent editing

Push tracked edits from a local projection workspace back into the human-facing fixture root

Remove a local projection workspace after the agent is done with it

Start a guided click-trace that the extension will record into the current WraithWalker root

Stop a guided click-trace and keep it as a completed scenario trace on disk

List all captured origins and their fixture summary

List captured static assets for an origin with optional filters, pagination, and body availability

List all captured API endpoints for an origin

Search live fixture content across assets, endpoint bodies, and text-like files, with path fallback when body text is unavailable or misses

Read a bounded page from a text fixture file by its path relative to the fixture root

Read a bounded text snippet from a fixture file relative to the fixture root

Read response metadata and a bounded body page for an API fixture returned by list-api-routes

Read the RESOURCE_MANIFEST.json for an origin

Overwrite a human-facing captured projection file with UTF-8 text

Patch a human-facing captured projection file by line range, with conflict detection

List guided scenario traces stored in the current WraithWalker root

Read a stored guided scenario trace by ID

Analyze one known JavaScript fixture and return compact semantic summaries without dumping the AST. Use suggest-js-seeds first when you need to discover actionable seeds across chunks.

Search JavaScript facts when you already have a query. For unknown bundles, use suggest-js-seeds first, then pass a returned nodeId or value into trace-js-pipeline.

First JS discovery step: suggest high-signal endpoint, selector, call, and string seeds, including captured API metadata links for endpoint seeds when available. Next, pass a returned nodeId or value to trace-js-pipeline.

Trace a likely JavaScript execution pipeline from a selector, endpoint, symbol, or nodeId using compact evidence and API metadata pointers. Next, use read-js-symbol for JS evidence and read-api-response for linked API metadata.

Read the smallest useful snippet after suggest-js-seeds, search-js, or trace-js-pipeline returns a nodeId. Prefer nodeId follow-up over broad file reads.

List the explicit site config entries stored in the current WraithWalker root

Ensure an origin is explicitly configured in the current root using the agent-friendly default capture patterns

Remove an explicit site config entry from the current WraithWalker root

Replace, append, or reset dump allowlist patterns for an explicitly configured origin

Ensure an origin is configured in the current root and report whether the connected extension is ready to capture it

Report whether the browser extension is connected to this local server and ready to capture

Read recent browser console and log entries observed by the connected extension

Report guided trace readiness plus an agent-friendly summary of the active trace, if one exists

List all saved fixture scenarios

Save the current fixture workspace as a named scenario snapshot and attach trace provenance

Compare two scenario snapshots and report differences in API endpoints