Documentation that stays true — for people and agents

You connect a repository and a branch — or let your agent run the sync_github tool — and GitDoc imports every .md and .mdx file it finds, up to 1,000, optionally narrowed to one subdirectory. It runs when you connect the repo, whenever you press Re-sync, and — if you switch automatic sync on — whenever someone pushes to the branch you chose. Automatic sync is a GitHub webhook you add once; only the branch you configured publishes, so a push to a feature branch or a tag is ignored. Files whose contents have not changed are skipped.

Yes. You connect your own GitHub account over OAuth and GitDoc reads as you, so any repository you can see, you can import. There is no shared server token, and we never ask you to paste one in.

MCP (Model Context Protocol) is an open standard that lets AI agents call tools on external services. GitDoc ships its own MCP server over streamable HTTP with 11 tools, so Claude Code, Cursor or any MCP client can create documentation, sync a repo, read, write and delete pages, search, and publish — the same pages your users read. You mint a personal token in your dashboard and everything the agent does is scoped to your account.

Plainly, so you are not surprised after signing up: there are no AI features of any kind (no docs assistant, no stale-page detection, no reader analytics); no search box inside the docs viewer, though search does exist as an MCP tool for agents; no SSO or SAML; and no billing at all. Anything marked Planned on the pricing page is exactly that. If it appears on this site without a Planned label, it works today.

If your current tool can export Markdown, yes. Put the files in a GitHub repo and import it, or have an agent create pages one by one over MCP with create_page. There is no proprietary format on our side either — it is Markdown in, Markdown out.

A documentation is private until you widen its audience. Private means exactly that: anyone who is not the owner or an invited collaborator gets a 404, even with the link, and it is noindexed and never listed. Password-protected sits in between — anyone with the link and the shared password can read it without an account, and it stays unlisted and noindexed. Public documentation is readable by anyone and listed at /d. Content is encrypted in transit and at rest, and it is never used to train AI models — GitDoc contains no AI at all.

The webhook URL is public — anyone can POST to it — so the signature is the whole of its authentication. Each documentation gets its OWN secret, never a shared one: with a single URL, a shared secret would let anyone holding it forge a push for somebody else’s repository. We hash the exact bytes GitHub sent, so a payload altered after signing does not verify, and an unknown repository, a switched-off sync and a bad signature all return the same refusal so the endpoint cannot be used to discover which repositories are connected. Rotating the secret immediately stops the old webhook working.

Yes — set a password on the documentation and send the link with it. Anyone holding both can read it, no sign-up and no invitation. It stays unlisted and noindexed while protected, so the password is doing real work. Owners and invited collaborators are never asked for it, and changing the password immediately signs out everyone who had the old one. The password is stored only as a scrypt hash, so nobody at CleverAI can read it back to you either.

Yes. Add a hostname such as docs.yourcompany.com to a documentation, publish the two DNS records we show you — a TXT record that proves you own the domain, and a CNAME that points it at us — and press Verify. The certificate is issued automatically; it usually starts serving within a few minutes of DNS propagating. The domain then serves that one documentation and nothing else: our dashboard, our marketing pages and anyone else’s documentation are all 404 on it, and your URLs never show a /d/ path. One caveat worth knowing before you set it up: a custom domain can serve a public or password-protected documentation, but not a private one — sign-in cookies belong to gitdoc.cleverai.ai and are never sent to another domain, so every visitor there is signed out, including you.

Nothing right now. GitDoc is free during early access: there is no payment integration in the product and nothing is metered for billing. There are usage limits — published on the pricing page rather than left for you to discover. The tiers on the pricing page describe what we plan to charge for later, not something you can buy today. We will give notice well before anything changes — and your Markdown is in your own repo either way.