Skip to main content
The hookfish package provides the project initializer, packaged dashboard, MCP inspector, and local migration command. Run it through your package manager without a global installation, or install it globally for a persistent command.

​
Install and update the CLI

Install Hookfish globally when you want the hookfish command available in every project:
Update a global installation to the latest stable release:
Every Hookfish command checks the latest published version. An outdated CLI prints a warning with the installed and latest versions before continuing. Registry failures do not prevent the requested command from running.

​
Scaffold a project

The default backend is node. The target directory must be empty, and its name must be a lowercase npm-compatible name.

​
Serve the dashboard

hookfish dev is an alias. The command serves the packaged dashboard behind a loopback operator BFF. It forwards only explicit safe operations and keeps HOOKFISH_API_KEY in the CLI process. Generated projects already combine this command with their runtime-native development server under pnpm dev.

​
Run the MCP inspector

hookfish inspector is an alias. Set INSPECTOR_PORT to override port 3000. See MCP inspector for storage and authentication behavior.

​
Run local migrations

This command applies bundled migrations to the selected local PGlite directory. Generated projects already apply PGlite migrations lazily on first use, so an explicit local migration is normally unnecessary. For production PostgreSQL, call migrateDatabase from a trusted deployment job as described in Databases and migrations. Experimental Durable Object databases apply their SQLite schema when each object starts.