Files
python-sdk/pkg/hanzo-tools-devserver/README.md
T
zeekay af78255a39 devserver: running dev servers as MCP nodes
An agent editing a web app needs the dev server's own view of it: which
routes exist, and whether the last edit broke the build. Next 16 serves
that over MCP at /_next/mcp, and Vite-based frameworks can with
vite-plugin-mcp, but nothing here found those endpoints.

index finds Next, Vite, Nuxt, Remix, React Router, Astro and SvelteKit
dev servers from each process's argv, cwd and listening ports, and lists
the tools of the MCP each serves. call runs one. errors returns current
build and runtime errors: Next's get_errors, after opening the app in the
browser tool, since Next reports only what a connected session reported;
otherwise Vite's error overlay, console errors and page errors, read
through the same browser tool.

discover() returns the servers as plain records, the shape a devserver
node will take. hanzo-mcp depends on the package so the tool ships.

Claude-Session: https://claude.ai/code/session_01Dc8DXc3fEQCRHUa6XWK4Ku
2026-09-29 12:37:53 -07:00

772 B

hanzo-tools-devserver

The devserver tool for hanzo-mcp: running dev servers as MCP nodes.

  • index — find dev servers on this machine (Next, Vite, Nuxt, Remix, React Router, Astro, SvelteKit) from each process's argv, cwd and listening ports, and list the tools of the MCP each one serves (Next 16+ at /_next/mcp; Vite-based frameworks at /__mcp/sse with vite-plugin-mcp or nuxt-mcp-dev).
  • call — run one of those tools.
  • errors — current build/runtime errors: the server's get_errors where it has one, otherwise Vite's error overlay, console errors and page errors, read through the browser tool.

hanzo_tools.devserver.discover() returns the servers as plain DevServer records.

pip install hanzo-tools-devserver