Getting started
OKForest’s hosted service reads OKF trees from your GitHub repositories, shows them to people in the browser, and serves them to AI assistants over MCP. Getting there takes five steps.
1. Get an account
Section titled “1. Get an account”OKForest is in Early Access: free, with open sign-up and no card. Join the Early Access by signing up, then choose Create your account: an account for your organization, with you as its admin.
If your organization already uses OKForest, ask one of its admins to invite you instead: in Settings → Members.
2. Add a tree
Section titled “2. Add a tree”A tree is one OKF bundle in a GitHub repository, or a folder in one. In Settings → Trees, choose Add a tree and paste its GitHub address:
- A public repository needs nothing more, and is read-only.
- A private repository needs its GitHub organization or account connected first: in Settings → GitHub, choose Connect GitHub and install the OKForest GitHub App on the repositories you choose. It can only read them.
OKForest reads the tree and checks it before adding it; its findings are on its Checks page, and never stop a tree from being served. An account can have 25 trees for now.
No tree yet? npx okforest init starts one (the CLI).
3. Read it in the browser
Section titled “3. Read it in the browser”Your account’s Forest page lists its trees. Each tree has its contents, an index by type and tag, and every concept rendered with its status, trust tier, and links. Search covers every tree at once. See the browser.
4. Connect an AI assistant
Section titled “4. Connect an AI assistant”Add OKForest to your assistant as a custom MCP connector that signs in with OAuth (in Claude, a custom connector; in ChatGPT, a custom MCP server, in developer mode), with this address:
https://mcp.okforest.ai/mcpSign in when it asks. If you belong to several accounts, choose this one. Then ask it something your trees know. See the MCP server.
5. Check it on every pull request
Section titled “5. Check it on every pull request”Add OKForest Validate to the tree’s repository, so every pull request is checked against the same rules as the Checks page, with each finding on its line.