Documentation that stays true — for people and agents

GitDoc is docs infrastructure. It syncs with your GitHub repo on every commit, keeps every page accurate as your product changes, and serves the same source of truth to your users and to their AI agents.

Free tier forever · No credit card · Export your Markdown anytime

Set up GitDoc with your agent

Paste this into your agent — it connects to the GitDoc MCP server, syncs your repo, and hands back a live docs URL.

Set up GitDoc for this project:

1. Connect to the GitDoc MCP server. In Claude Code, run:
   claude mcp add --transport http gitdoc https://gitdoc.cleverai.ai/api/mcp
   (Other MCP clients: add a streamable-HTTP server pointing at https://gitdoc.cleverai.ai/api/mcp)
2. Create a documentation space for this project with the create_space tool.
3. Sync this GitHub repository into the space with the sync_github tool.
4. Publish the space with publish_space and give me the live docs URL.
  • Claude Code
  • Cursor
  • ChatGPT

Everything your docs need to stay accurate

Writing docs was never the hard part. Keeping them true after every release is — so that is what GitDoc automates.

Git Sync

Branch, review, and merge your docs like code. Every commit to your repo lands in your published docs — no copy-paste, no drift.

GitDoc Agent

When your product changes, the GitDoc agent flags the pages that stopped being true, so stale content never quietly ships.

Ask your docs

A built-in AI assistant answers questions straight from your pages — with citations, not guesses — for every visitor.

AI Insights

See what users and agents search for, where they get stuck, and which pages leave questions unanswered.

Live docs in three steps

  1. Connect your repo or your agent

    Point GitDoc at a GitHub repository, or let your coding agent do it over MCP with a single prompt.

  2. GitDoc generates and syncs your docs

    Your Markdown becomes a structured, searchable docs space — re-synced automatically on every commit.

  3. Publish at your URL

    One click makes the space public at your docs URL, with AI answers built in for every reader.

MCP server built in

Your agent is a first-class docs author

GitDoc ships a native MCP server. It works with Claude Code, Cursor, ChatGPT, and any MCP client over streamable HTTP — your agent can create spaces, sync repos, edit pages, and publish without leaving the editor.

terminal
$ claude mcp add --transport http gitdoc \
    https://gitdoc.cleverai.ai/api/mcp
✓ Added HTTP MCP server "gitdoc"
$claude "sync this repo to GitDoc and publish it"
MCP tools exposed by the GitDoc server
ToolWhat it does
list_spacesList your documentation spaces
create_spaceCreate a new docs space
sync_githubSync a GitHub repo into a space
list_pagesList the pages in a space
get_pageRead a page as Markdown
create_pageAdd a new page
update_pageEdit an existing page
searchFull-text search across your docs
publish_spacePublish a space at its public URL

Built to be trusted with your docs

No per-seat pricing

Invite your whole team and every contributor. Plans are priced by spaces, never by heads.

GDPR-ready & encrypted

Content is encrypted in transit and at rest, and we build for GDPR from day one.

Zero lock-in

Your docs are Markdown in your repo. Export everything, anytime, in one click.

Never trains models

Your content powers answers for your readers. It is never used to train AI models.

Questions, answered honestly

How does GitHub sync work?

You connect a repository (or let your agent run the sync_github tool) and GitDoc mirrors its Markdown into a docs space. Every push to the synced branch updates the space, so published docs track the repo — the repo stays the source of truth.

What is MCP, and why does it matter for docs?

MCP (Model Context Protocol) is an open standard that lets AI agents call tools on external services. GitDoc exposes its own MCP server over streamable HTTP, so agents like Claude Code, Cursor, or ChatGPT can create spaces, sync repos, edit pages, and search your docs directly — the same docs your users read.

Can I migrate from another docs tool?

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

Is my content private?

Spaces are private until you explicitly publish them. Content is encrypted in transit and at rest, and it is never used to train AI models. The built-in assistant only answers from your own pages.

Can I use my own domain?

Not yet — custom domains are on the roadmap for paid tiers. Today your docs are published under gitdoc.cleverai.ai. Join the waitlist and we will let you know the moment custom domains land.

What happens if I cancel?

Nothing is held hostage. Your Markdown lives in your repo and stays exportable at any time; paid features simply stop, and spaces beyond the free tier limits become read-only until you export or downgrade them.

Your docs are one commit away

Sync a repo, publish a space, and hand your agents the same truth your users read.

Start for free

Get early access

GitDoc is rolling out gradually. Join the waitlist and we will email you when your spot opens — free tier first, paid tiers as they ship.

  • Free tier: 1 space, GitHub sync, MCP server
  • No credit card, no per-seat pricing
  • Export your Markdown anytime

No spam. We only email you about GitDoc access.