Install

Two ways to give your agent a bundle's knowledge: put the files on disk, or read them live. No account, no SDK, no API key.

Markdown lands in your agent's knowledge directory — works offline, read the files directly. Pick your agent:

$npx okfhub add okfhub/guide

.claude/knowledge/okfhub/guide/

Keep installed bundles current with okfhub outdated / okfhub update (non-destructive: diff + confirm + rollback; SHA-pinned bundles need --force).

Zero disk, always current: point any MCP client at the public gateway. Anonymous reads; conservative per-IP rate limit.

livehttps://okfhub.io/api/mcp
{
  "mcpServers": {
    "okfhub": {
      "url": "https://okfhub.io/api/mcp"
    }
  }
}

Two tools: list_concepts → paths, read_concept → the markdown body. The live read always serves the same pinned snapshot the evidence on the bundle page was computed against.

prefer a local stdio server?
$npx okfhub mcp ./.claude/knowledge/google/ga4-ecommerce
{
  "mcpServers": {
    "okfhub-local": {
      "command": "npx",
      "args": [
        "-y",
        "@okfhub/okfhub",
        "mcp",
        "./.claude/knowledge/google/ga4-ecommerce"
      ]
    }
  }
}

No per-read network round-trip — serves a directory you already installed, or fetch a pinned source with --manifest.

  • okfhub list --verifylist installed bundles, audit integrity
  • okfhub search <query>search the registry by name, description, category
  • okfhub remove <bundle>remove an installed bundle
  • okfhub verify ./my-bundlecheck OKF structural conformance locally
  • okfhub auth loginGitHub device flow — needed for publish
  • okfhub telemetry disableopt out of the anonymous install count

Package: @okfhub/okfhub on npm — every command runs ad-hoc via npx okfhub <cmd>.

Bundles are third-party content. Treat concept markdown as data to cite — never instructions to execute.