Git-Backed Docs for Agents

What is it

Git-Backed Docs for Agents is the idea that documentation should live in a Git repository as the single source of truth, then be rendered in two directions at once: as human-readable docs (websites, PDFs, Markdown readers) and as machine-readable context for AI agents. Thousand and Moji are the two products exploring this, with Moji pushing a "PDF-like Markdown reading" experience and Thousand framing docs as shared context between people and agents.

The technical essence is simple: Markdown files in a repo, a build pipeline that compiles them into multiple outputs, and an MCP server or API that lets agents query the same content. The business significance is bigger. Every company now has two documentation problems — the one humans read and the one agents consume — and nobody wants to maintain them separately. Whoever owns the "write once, serve both" layer captures a recurring workflow. This is a productivity play with an open-source wedge and a clear path to paid hosting, sync, and agent-context features.

Why now

Three things converged in 2025-2026 to make this viable. First, MCP (Model Context Protocol) became the de facto standard for connecting agents to external context, so "docs as agent context" stopped being a thought experiment and became an integration target. Second, coding agents like Claude Code, Cursor, and Copilot now read repositories directly, which means docs already in Git are half-solved — they just lack structure and retrieval. Third, the "docs-as-code" toolchain (Docusaurus, MkDocs, Mintlify) matured to the point where Git-backed publishing is boring infrastructure, freeing founders to compete on the agent layer instead.

The timing matters because the pain is fresh. Teams adopting agents in 2026 are discovering that their wikis, Notion pages, and Confluence spaces are invisible to their tools. They need a Git-native source that both renders for humans and serves as retrievable context. Last year the agent ecosystem wasn't standardized enough; next year the incumbents (Mintlify, GitBook) will have shipped their own agent features. The window is roughly 12-18 months wide, and it's open right now.

Market Evidence

The signal here is thin but directional: one independent source (Product Hunt), two total mentions, a 100% growth rate, and an "emergent" stage classification. A trend score of 60/100 and an opportunity score of 51/100 tell the honest story — this is early, not proven. Two mentions is not a market; it's a hypothesis with a pulse.

But thin early signals are exactly where indie developers win, because the competition score is only 30/100. The demand score of 45/100 says buyers haven't formed a queue yet. That's a feature, not a bug, if you're fast. The risk is that this is a feature, not a company — a capability that Mintlify or GitBook absorbs into an existing $50-200/month plan. The 100% growth rate is meaningless at n=2, so treat it as noise until you see it repeated across Hacker News, GitHub stars, and Discord communities.

My position: this is real demand in an unformed market. The underlying pain — agents can't read your docs — is verifiable by talking to ten engineering teams. Validate the pain directly rather than trusting the trend score.

Who's Behind It

Thousand and Moji are the two named products, both surfacing on Product Hunt on 2026-09-12. Neither is a whale yet — they're early-stage builders staking out the "Git-backed docs for humans and agents" framing. Moji leans into Markdown reading as a PDF replacement; Thousand leans into shared document source for humans and agents.

The real whales are adjacent: Mintlify (docs-as-code with AI features, well-funded), GitBook (docs platform pivoting to AI), Docusaurus and MkDocs (open-source incumbents), and the agent platforms themselves — Anthropic with MCP, Cursor, and GitHub Copilot. The competitive dynamic is that the agent platforms define the protocol, the docs platforms own the customers, and the indie builders own the speed. If Anthropic ships a first-party "docs MCP server" template, it legitimizes the category and commoditizes the basic version. That's both a threat and a tailwind.

TAM & Market Size

The buyers are engineering teams and technical founders who already maintain docs in Git and are now adopting AI agents. That's a large and growing segment: GitHub has over 100 million developers, and a meaningful slice work on teams with docs-as-code setups. The realistic serviceable market is smaller — teams of 5-500 engineers who feel the agent-context pain acutely.

Price tolerance is moderate. Docs tooling typically sells at $20-100 per seat per month (Mintlify starts around $150/month for teams, GitBook charges per user). For an agent-context layer, $29-99/month per project or $10-15 per seat is defensible because the value is "your agents stop hallucinating about your codebase." Budget usually sits with engineering leadership, not marketing, which shortens sales cycles.

The demand score of 45/100 is the honest constraint: buyers haven't been trained to pay for this yet. The opportunity score of 51/100 reflects a market that's real but unproven. My read: the TAM is big enough for a $1-5M ARR indie business, not a venture-scale outcome on its own — unless you become the default MCP docs layer.

Competitive Landscape

The landscape splits into three tiers. Tier one: Mintlify and GitBook — polished, funded, with existing customers, but their agent features are bolted on rather than native. Tier two: Docusaurus, MkDocs, and VitePress — free, open-source, deeply trusted, but zero agent awareness. Tier three: indie experiments like Thousand and Moji — fast, native to the agent era, but no distribution.

The gap is the "MCP-native docs server" — a tool that takes any Git repo of Markdown and exposes it as structured, retrievable context for agents, with a human-readable render as a bonus. Nobody owns this cleanly yet. Mintlify will get there, but it'll be a feature in a $150/month plan, not a focused tool.

If Big Tech enters — say, GitHub ships "repo docs as MCP context" natively — you have maybe 12-18 months before the basic version is free. Your defense is depth: better retrieval, versioning, multi-repo support, and a hosted sync layer that GitHub won't bother building. Competition score of 30/100 is your friend right now. Use it.

Business Model

Go open-core. The CLI and MCP server are free and open source (MIT or Apache 2.0) to drive adoption and GitHub stars. Monetize the hosted layer: cloud sync, multi-repo indexing, team permissions, analytics on which docs agents actually query, and a managed MCP endpoint.

Pricing: Free for individuals and single public repos. Team plan at $49/month per workspace (up to 10 repos, 5 seats). Pro at $149/month (unlimited repos, SSO, query analytics, priority indexing). Enterprise custom at $500+/month. This mirrors Mintlify's ladder but undercuts it at the entry point, which matters when you're unknown.

12-month forecast: conservative $3K MRR (60 team plans), base $12K MRR (roughly 150 team + 30 pro), optimistic $35K MRR (landing 3-5 mid-size companies plus strong self-serve). CAC via developer content and open-source distribution should land at $80-200 for self-serve, with payback under 3 months on the $49 plan. The open-source wedge is what keeps CAC low — this is why you don't gate the core.

MVP Blueprint

Ship in 2-7 days, not 21. The 21-day estimate is for the full vision; the MVP is narrower.

Core features only: (1) a CLI that takes a Git repo path and indexes all Markdown into a local SQLite or vector store, (2) an MCP server that exposes search_docs and get_doc tools, (3) a minimal web renderer that shows the same docs as a clean reading page. Cut multi-repo, auth, analytics, and hosting entirely for v1.

Tech stack: TypeScript for the CLI and MCP server (the MCP SDK is TS-first), SQLite with FTS5 for keyword search plus optional embeddings via a local model or OpenAI. The renderer can be a static Next.js page or even a single HTML file. Ship as an npm package: npx gitdocs-mcp ./path. That's the whole product.

Fastest path to launch: publish to npm, post on Hacker News and r/LocalLLaMA, and submit an MCP server listing to Anthropic's registry. The open-source repo is your marketing. Add a hosted version only after 100+ GitHub stars prove pull. The MCP Server and CLI Tool product types are correct; skip the VS Code Extension until week three.

Commercial Opportunities

Hosted MCP docs endpoint. Target: teams using Cursor or Claude Code who want a shared, always-on docs context without running local servers. Charge $49-149/month. This beats local-only because teams need consistency across machines and members.

Docs analytics for agent queries. Target: documentation owners who want to know what agents (and humans) actually search for and where they fail. Charge $99/month. This is a data product incumbents ignore because they're focused on rendering, not retrieval intelligence.

Migration and setup service. Target: mid-size companies moving from Confluence/Notion to Git-backed agent-ready docs. Charge $2,000-5,000 one-time. High-margin, funds development, and teaches you exactly what the product should do. Beats pure SaaS early because it generates cash before you have scale.

Product Ideas

🥇 GitDocs MCP — "Point it at any Git repo, get an MCP server your agents can query." Target: developers using Claude Code, Cursor, or any MCP client. Why now: MCP is standardizing and every agent user needs context; a one-command install wins.

🥈 DocSync Cloud — "Your team's docs, served to humans and agents from one Git source." Target: engineering teams of 10-200. Why now: teams are adopting agents faster than they can fix their docs infrastructure, and nobody wants two sources of truth.

🥉 Moji-style Markdown Reader — "A PDF-quality reading experience for Markdown, with an agent-readable backend." Target: technical writers and docs maintainers who hate how Markdown renders. Why now: the reading experience is the wedge that gets non-engineers to adopt Git-backed docs.

SEO Opportunity

Search volume for "MCP server docs" and "Git-backed documentation" is low but rising fast, and SEO difficulty is only 25/100 — wide open. Target long-tail keywords: "MCP server for documentation," "Git docs for AI agents," "Markdown MCP server," "docs as agent context," and "Claude Code documentation MCP." Content strategy: publish a working tutorial ("Build an MCP docs server in 20 minutes") and a comparison post ("Mintlify vs Git-backed docs for agents"). Tutorials rank and convert developers better than landing pages at this stage.

Risk Assessment

The thesis breaks if "docs for agents" turns out to be a feature, not a product — and Mintlify or GitHub ships it free within a year. That's the top market risk, and it's real given the competition score of 30/100 cuts both ways.

Risk two: developers won't pay for docs tooling they can hack together in a weekend. The open-source version may cannibalize the paid tier. Mitigate by gating team sync and analytics, not core functionality.

Risk three: execution — MCP is still evolving, and betting on a moving protocol is risky. If Anthropic changes the spec, your integration breaks.

Validate cheaply: build the CLI in two days, post it, and count GitHub stars and inbound "can I pay for hosting?" messages within two weeks. If you get 200+ stars and 10+ hosting requests, build the cloud. If you get crickets, walk away. Don't spend 21 days before testing demand.

Action Plan

Today: write a one-page spec and scaffold the CLI with the MCP TypeScript SDK. Tomorrow: get search_docs working against a local Markdown repo. Day three: publish to npm and post on Hacker News, r/LocalLLaMA, and the MCP Discord.

Week 1 goal: 50 GitHub stars and 5 real users giving feedback. Low-cost validation: DM ten engineering leads asking "how do your agents access your docs today?" — if they describe a painful workaround, you have a market.

Month 1 goal: 200 stars, a hosted waitlist, and your first paying customer at $49/month. If signal confirms, build DocSync Cloud and add query analytics.

Month 3 goal: $2-5K MRR, 30+ paying teams, and a repeatable content engine (tutorials, comparisons). If you're below $1K MRR with no inbound, reassess — the market may be too early or the pain too mild.

Related Terms

MCP (Model Context Protocol) — the standard that makes Git-backed docs queryable by agents; this trend is essentially MCP applied to documentation. Docs-as-Code — the mature practice of storing docs in Git; this trend extends it to machine consumers. Agent Context Engineering — the broader discipline of feeding agents the right information; Git-backed docs is one concrete implementation. Together they form a stack: Docs-as-Code stores it, MCP serves it, context engineering makes it useful.