🌲 Evergreen

Documentation that writes and maintains itself.

Evergreen is an AI knowledge layer on Cloudflare Workers. It drafts docs from your real sources — code, PRs, tickets, and Claude memory — you approve them in seconds, and it keeps them from rotting: when the source changes, the doc is flagged stale and a refresh is drafted for you. The same knowledge is readable and writable by AI agents over MCP.

This repo is a template. Click “Use this template”, then follow Quickstart below. The entity dictionary and a few config values are placeholders — make them yours.

📖 New here? Read USAGE.md — full configuration checklist (exactly what to fill in), deploy steps, how to use every feature, and how to connect your Claude.

The loop

flowchart LR
  subgraph SRC["Real sources"]
    direction TB
    C["Code / PRs"]
    T["Tickets"]
    M["Claude memory"]
  end
  SRC --> LLM["Claude<br/>(Bedrock)"]
  LLM --> DR["Drafts"]
  DR -->|"human approves<br/>in seconds"| KB[("Knowledge base<br/>D1: facts + entity graph")]
  KB --> UI["Web UI<br/>/evergreen"]
  KB --> MCP["MCP server<br/>agents read &amp; write"]
  KB -. "code &amp; facts change" .-> DFT["Drift +<br/>auto-maintain"]
  DFT -. "flag stale · draft refresh" .-> DR

Generate → approve → detect drift → refresh → repeat. The loop closes itself.

Related MCP server: okfy

What's inside

Architecture

• Cloudflare Workers + Hono

• D1 (SQLite) with FTS5 full-text search — the knowledge base is a graph of facts ↔ entities

• Amazon Bedrock (Claude) for generation, synthesis, Q&A, and drift judgment

• MCP (streamable HTTP) for agent access

• Auth via Cloudflare Access (SSO) with a WEB_PASSWORD basic-auth fallback

The core knowledge base lives at /; the Evergreen doc surface is additive under /evergreen/*, in its own hack_* tables — generated docs only promote into the real knowledge base on human approval.

Quickstart

bun install                                   # or npm install

# 1. Create the database + token store
wrangler d1 create evergreen                  # paste database_id into wrangler.jsonc
wrangler kv namespace create TOKENS           # paste id into wrangler.jsonc
bun run db:init:remote                         # apply migrations/

# 2. Secrets
wrangler secret put WEB_PASSWORD              # browser UI password
wrangler secret put MCP_SHARED_SECRET         # fallback MCP bearer
wrangler secret put BEDROCK_API_KEY           # Bedrock bearer token (for the LLM)
wrangler secret put LINEAR_API_KEY            # optional — ticket harvester
wrangler secret put GITHUB_TOKEN              # optional — private repos + higher rate limits

# 3. Set account_id / route / CF_ACCESS_TEAM_DOMAIN in wrangler.jsonc, then:
bun run deploy

Local dev

cp .dev.vars.example .dev.vars                # set WEB_PASSWORD, BEDROCK_API_KEY, …
bun run db:init:local
bun run dev                                    # http://localhost:8787  (UI password from .dev.vars)

Make it yours

• src/extraction.ts — replace the example entity dictionary (clients, products, people, systems) with your own vocabulary. This is how the graph auto-links.

• wrangler.jsonc — set HARVEST_LINEAR_TEAM, your custom domain, and CF_ACCESS_TEAM_DOMAIN.

• scripts/seed.ts — import your local Claude memory: bun run scripts/seed.ts <memory-dir> --author "Your Name" → review the sensitive-content report → bun run db:seed:remote.

Connect a Claude (MCP)

Add to ~/.claude.json (or a project .mcp.json):

{
  "mcpServers": {
    "evergreen": {
      "type": "http",
      "url": "https://<your-worker>/evergreen/mcp",
      "headers": { "Authorization": "Bearer <token-or-MCP_SHARED_SECRET>" }
    }
  }
}

Per-person tokens (for authorship) go in the TOKENS KV:

wrangler kv key put --binding TOKENS <token> '{"name":"Alex"}'

MCP tools: ask_docs · generate_doc · check_drift · coverage_gaps · entity_brief.

License

MIT — see LICENSE.