Skip to main content
Hookfish reads conventional values from the bindings passed to fetch, then from the ambient Node.js environment when available. Explicit configuration and runtime resolvers can override these conventions.

Broker variables

Generate independent high-entropy values for the encryption key and broker key:
Rotating OAUTH_ENCRYPTION_KEY makes existing encrypted values unreadable. Rotating HOOKFISH_API_KEY invalidates every scoped broker token.

Database variables

Provider variables

Built-in provider factories use conventional credential names when explicit values are not supplied:
The MCP template does not require fixed credentials. Dynamic MCP instances can register a client or store custom credentials.

Dashboard and inspector variables

The inspector uses HOOKFISH_API_KEY as its local broker key and defaults to test when it is unset. Store production values in the runtime’s secret manager. Do not commit .env, .dev.vars, database URLs, or provider credentials.