Skip to main content
Hookfish separates the broker API, storage adapters, provider contracts, provider implementations, React integration, and CLI into published packages.

Database import paths

The Durable Objects exports are experimental. Use the PostgreSQL adapter with Hyperdrive for production Workers deployments.

API import paths

Use createHookfish for the concise authenticated setup:
For trusted application code, construct Hookfish from @hookfish/sdk. Put the tenant identifier in each resource path when your application is multi-tenant:
Use hookfish.mcp() when you want an authenticated, connected MCP client instead of the raw connection credential. The SDK includes both Octokit and the MCP client dependency. Install @modelcontextprotocol/client directly only when you construct and pass a custom MCP client instance. The same initializers are also available as hookfish.provider.github() and hookfish.provider.mcp(). Use @hookfish/api for the broker runtime and lower-level composition. Import the migration helper from @hookfish/database.

Individual provider packages

@hookfish/providers re-exports all built-in factories. Install an individual package such as @hookfish/provider-github or @hookfish/provider-mcp when you want to keep the dependency surface narrow.
Import @hookfish/backend only when composing a raw Hookfish-compatible API handler yourself. HookfishServer.init(...).fetch already applies that layer.