repowiseServer & watch — serve, watch, mcp
Run the repowise API and dashboard, auto-update on file save, or expose the MCP server directly to an editor.
repowise serve
Start the API server and the local web dashboard. The Next.js UI
is downloaded and cached on first run (~50 MB). Use --no-ui for
API-only mode.
repowise serve [OPTIONS]Prop
Type
repowise serve
repowise serve --port 8000 --ui-port 3001
repowise serve --no-ui # headless / CIThe dashboard exposes the chat, graph view, hotspots, ownership, dead code, generated wiki, decision records, and cost tracking.
repowise watch
Filesystem watcher that triggers update on file changes. Debounced —
several rapid edits collapse into a single update cycle.
repowise watch [PATH] [OPTIONS]Prop
Type
repowise watch
repowise watch --debounce 1500
repowise watch --workspaceFor passive auto-sync, prefer the post-commit hook.
watch is best when you're actively coding and want the wiki current
between commits.
repowise mcp
Start the MCP server for editor integration. Exposes the
seven public tools. Supports both stdio
(Claude Code, Cursor, Cline) and sse (web clients).
repowise mcp [PATH] [OPTIONS]Prop
Type
repowise mcp # stdio
repowise mcp /path/to/repo
repowise mcp --transport sse --port 8080repowise init writes a working .mcp.json for you, so you usually
don't run this command directly — your editor spawns it.
Indexing — init, update, reindex
The three commands that build and maintain repowise's intelligence layers. init parses everything from scratch, update is incremental on each commit, reindex rebuilds the vector store without re-running the LLM.
Query — search, status
Ask questions and check sync state from the terminal without involving an editor.