pracht dev-mcp server

pracht

One app graph, projected to browsers and to agents. (pracht /praxt/ — Dutch & German for splendor. Also: how you've always mispronounced Preact.)

Other frameworks render your app for humans and leave agents to scrape it. Pracht resolves your routes, loaders, API routes, and capabilities into one explicit graph, then projects that graph two ways: components for people, and typed, trust-gated tools for agents — over HTTP, WebMCP, remote MCP, and llms.txt. It is a Preact framework, so the human half is small; it is an explicit framework, so the agent half is something you declare rather than something that gets scraped off you.

npm create pracht@latest my-app

Documentation · Why pracht · Getting started · Compare to other frameworks

Why pracht

• One explicit app graph — a typed defineApp() manifest wires routes, shells, middleware, and capabilities. What runs where is never a mystery, and because the graph is resolved rather than inferred, tooling can read it. Prefer file-based routing? Opt in to the pages router and skip the manifest entirely.
• The graph is projected to agents, not scraped from them — one defineCapability() contract becomes a server call, an HTTP endpoint, a WebMCP page tool, and a tool on your app's own remote MCP endpoint, listed for discovery in a generated llms.txt. Same validation, same middleware, same effect class on every transport.
• Trust ships with the surface — Web Bot Auth (RFC 9421) verified agent identity, per-capability policies, a prepare/commit confirmation gate for destructive effects, one structured audit event per dispatch, and pracht eval to prove agent flows in CI.
• Preact-first — 0 KB of client JavaScript on a static route, 8.0 KB gzip with islands, 17.4 KB fully hydrated with the router. Measured by pnpm bench in this repo and gated in CI, not asserted.
• Per-route render and hydration modes — SPA, SSR, SSG, and ISG, and full, islands, or no hydration, chosen per route. No global default fighting you.
• Vite-native — instant HMR, fast builds, multi-environment output out of the box.
• Performance budgets built in — pracht build --analyze reports per-route client JS (gzip + raw), and per-route budgets fail the build when a route ships too much.
• Env safety built in — typed serverEnv/publicEnv helpers with a PRACHTPUBLIC prefix rule, and builds fail when client bundles reference non-public env vars.
• Optional content collections — @pracht/content gives loaders and build plugins one server-only registry for routes, locales, source/compiled representations, caching, and emitted assets.
• Markdown images without runtime JavaScript — @pracht/markdown compiles ordinary relative Markdown images through @pracht/image into cached responsive WebP variants for SSR, SSG, and hydration-disabled routes.
• Deploy anywhere — one codebase, one build, five production-ready adapters (Node, Cloudflare Workers, Netlify, Vercel, and pure static export).

At a glance

Two routing styles, your choice:

Manifest routing — full control, explicit wiring:

Shortened. The full README is on GitHub.