Helpdock

Any GitHub repo's docs, as a help center and an MCP server. Replace github.com with helpdock.flisk.sh:

https://github.com/vercel/next.js  →  https://helpdock.flisk.sh/vercel/next.js

• A help center for any public repo. Ask in your own words; answers are passages quoted from the docs (whole paragraphs and code blocks, not fragments), each linked to its file and heading on GitHub. Every page is browsable.

• An MCP server per repo. https://helpdock.flisk.sh/owner/repo/mcp gives Claude, ChatGPT, Cursor or Codex that repo's docs: search_docs and ask_help_center, read-only, no key.

• Your AI, not ours. Helpdock never calls a model. Under every answer, Ask your AI hands the question and the cited passages to the visitor's own ChatGPT or Claude.

• No signup, no database, no API key. The URL is the state. A repo is read on its first visit (one GitHub API call lists it, the Markdown is fetched in parallel; GitHub's archive is the fallback when the API limit is used up), listed again every six hours. Opening a repo costs almost no memory: the table of contents is a list of file paths and every page is fetched from GitHub when you open it. The SQLite full-text index is built for a repository only when someone asks it a question (a few seconds) and dropped after ten idle minutes. An optional GITHUB_TOKEN (read-only, public repositories) raises GitHub's limit from 60 to 5000 calls an hour.

• A folder of a repository, too. Paste a GitHub folder link and only that folder opens: helpdock.flisk.sh/hashicorp/web-unified-docs/tree/main/content/terraform/v1.17.x/docs is the Terraform docs, with the same MCP server at its /mcp.

• Markdown, MDX and reStructuredText. Django's docs (docs/*.txt) and any Sphinx .rst are converted to Markdown first: titles, code blocks, notes, signatures and cross-references. HashiCorp's MDX callouts and Docusaurus-style MDX work too.

• Or your own docs. Without HELPDOCK_REPOS, / is a help center for your own Markdown (seed-docs/, POST /docs), on SQLite or your own Postgres. Built and run with Flisk.

Run it

Needs Docker, Tilt and the Flisk CLI.

git clone https://github.com/flisk-sh/helpdock.git
cd helpdock
flisk project --yes
flisk up agents
flisk status          # the agent URL, e.g. http://api.helpdock.localhost:8082/api/agent

Open the agent URL with a trailing slash in a browser. The first start loads the starter pages (seven pages of the Flisk docs, from services/agents/agent/seed-docs/) into the help_docs table.

Use your own docs: replace the files in seed-docs/ and run bun run seed:pack in services/agents/agent before the first start (the image ships only compiled code, so the pages are packed into src/seed-docs.generated.ts). Or add pages at any time:

curl -s -X POST "$AGENT_URL/docs" -H 'content-type: application/json' \
  -d "$(jq -n --arg m "$(cat billing.md)" '{source:"billing.md", markdown:$m}')"

Related MCP server: docs-mcp

Online

Helpdock runs online for free at helpdock.flisk.sh on one Render free web service (from render.yaml and the root Dockerfile), with no database account and no AI key: without DATABASE_URL it uses Bun's built-in SQLite. Bring your own Postgres (Neon or any other) to keep added pages and history. DEPLOY.md has the steps, the DNS record, the limits and what free costs you (the service sleeps after 15 idle minutes).

API

Settings: HELPDOCK_DOCS_DIR, HELPDOCK_REPOS, HELPDOCK_PREWARM, HELPDOCK_REPO_BUILDS_PER_HOUR, GITHUB_TOKEN (optional: raises GitHub's 60 API calls an hour), and for online use HELPDOCK_ADMIN_TOKEN, HELPDOCK_PROXY, HELPDOCK_TURNS_PER_HOUR, HELPDOCK_PUBLIC_URL (see the header of services/agents/agent/src/index.ts).

Helpdock started from the Flisk agent-stack template. Its notes follow.

Starter landscape for AI agents on Flisk: a Bun agent resource, an MCP tool server, Postgres, and NATS.

Prerequisites

• Docker running

• Tilt installed

• Bun installed

• Flisk CLI

Quick start

Repository-pinned CLI (optional): Run bun install from the repository root to install the version pinned in package.json. Use bun run flisk:project to initialize project config, bun run flisk:dry-run to preview startup, or bun run flisk:up -- <stack> to start a stack. The global npm and standalone binary installation paths remain available.

git clone https://github.com/flisk-sh/flisk-agent-stack.git
cd flisk-agent-stack
flisk project --yes
flisk up

Or from the CLI:

flisk project agent-stack
cd flisk-agent-stack
flisk up

Landscape

Try the agent

Once flisk up agents is running, find the agent's URL with flisk networks and send turns with the x-session-id header. Each session keeps its transcript in Postgres, so it survives a restart of the agent:

AGENT_URL=<the agent URL from flisk networks>
curl -s -X POST -H 'x-session-id: demo' -H 'content-type: application/json' -d '{"input":"hello"}' "$AGENT_URL/turn"
curl -s -H 'x-session-id: demo' "$AGENT_URL/session"

/ready answers 503 while the checkpoint store is unreachable. The replacement for the placeholder turn lives in runTurn in services/agents/agent/src/index.ts.

Scaffold more with:

flisk resource my-agent --type agent --stack agents --durability files
flisk resource my-tools --type mcp --stack agents

See flisk and the website llms.txt for the full contract.

The film on the landing page and above is made by video/: bun video/shots.ts takes screenshots of the live site, bun video/render.ts films them in headless Chrome (needs Chrome and ffmpeg). Scenes are in video/film.json.