llms.txt
# Moxie Docs
> Free to start on one repo, no card required. PR checks that flag doc gaps, living docs re-checked on every merge, MCP context for AI agents, hosted public knowledgebases, and Friday Cleanup PRs from GitHub.
Moxie Docs is a hosted service that connects to your GitHub repositories, keeps a searchable knowledge base of your codebase in sync on every merge, and serves that context to AI coding agents over MCP. Built by jackalope.digital.
## Product
- [Overview](https://moxiedocs.com/): Automated codebase documentation for GitHub - searchable docs, MCP context, and Friday Cleanup PRs.
- [How it works](https://moxiedocs.com/workflow): Indexing, doc generation, drift detection, and Friday Cleanup PRs.
- [Use cases](https://moxiedocs.com/use-cases): Onboarding, architecture docs, and AI agent context.
- [MCP server](https://moxiedocs.com/mcp): How AI agents query your codebase context over the Model Context Protocol.
- [Automated code documentation](https://moxiedocs.com/code-documentation): Generate searchable codebase documentation from GitHub automatically. Architecture, conventions, cross-file flows, drift detection, MCP context, and Friday Cleanup PRs.
- [Documentation drift detection](https://moxiedocs.com/documentation-drift): Detect documentation drift and fix stale docs on every merge. Surface gaps and open a reviewable Friday Cleanup PR so the wiki does not rot quietly.
- [PR documentation checks](https://moxiedocs.com/pr-documentation-checks): Verify docs on every GitHub pull request. Advisory check runs flag doc gaps, convention breaches, and PR descriptions that miss your template - required in branch protection when you want a gate.
- [Architecture documentation](https://moxiedocs.com/architecture-documentation): Generate architecture documentation from your GitHub repository: module boundaries, cross-file flows with Mermaid diagrams, and a directory guide, cited to source and re-checked on every merge.
- [Free tools hub](https://moxiedocs.com/free-tools): Browser-based SQL ER diagrams, README, Mermaid, ADR, AGENTS.md, and llms.txt utilities - no account required.
- [Open source](https://moxiedocs.com/open-source): How Moxie Docs supports and works with open-source repositories.
## Agent integrations
Connect Moxie Docs MCP context to the agents your team already uses:
- [Cursor](https://moxiedocs.com/integrations/cursor): Connect Cursor to your repository's live docs, conventions, and doc gaps over MCP. One setup command after you connect GitHub - no manual context packing.
- [Claude Code](https://moxiedocs.com/integrations/claude-code): Give Claude Code repository conventions, generated docs, and doc gaps over MCP - and keep AGENTS.md and CLAUDE.md aligned with the code that ships.
- [Codex](https://moxiedocs.com/integrations/codex): Connect OpenAI Codex to live codebase docs and conventions over MCP. Compact context from Moxie Docs for fewer exploratory reads and better edits.
- [Windsurf](https://moxiedocs.com/integrations/windsurf): Connect Windsurf to Moxie Docs over MCP for live codebase documentation, conventions, and doc gaps. One setup command after you connect GitHub.
- [Cline & Roo Code](https://moxiedocs.com/integrations/cline): Connect Cline and Roo Code to your repository's live codebase docs, conventions, and doc gaps over MCP. Zero manual context packing.
- [GitHub Copilot](https://moxiedocs.com/integrations/github-copilot): Give GitHub Copilot Agent Mode live repository conventions and doc gaps over MCP - and keep .github/copilot-instructions.md current.
## Solutions
How Moxie Docs maps to each engineering role and organizational setup:
- [Solutions overview](https://moxiedocs.com/for): Moxie Docs framed by role and team setup.
- [For engineering leaders](https://moxiedocs.com/for/engineering-leaders): Cut onboarding time, kill documentation drift, and see what shipped each week.
- [For staff & platform engineers](https://moxiedocs.com/for/staff-engineers): Turn tribal knowledge into source-cited docs that teammates and AI agents follow.
- [For CTOs & founders](https://moxiedocs.com/for/ctos): Keep documentation current as AI accelerates the codebase, without a per-seat wiki bill.
- [For teams using AI agents](https://moxiedocs.com/for/ai-engineers): Serve Cursor, Claude Code, and Codex real repository context over MCP.
- [For startups & early-stage](https://moxiedocs.com/for/startups): Move fast without losing codebase context or burning founder hours on onboarding.
- [For scale-ups & growing orgs](https://moxiedocs.com/for/scaleups): Eliminate documentation drift and knowledge silos as your dev team doubles.
- [For multi-repo & microservices](https://moxiedocs.com/for/multi-repo-teams): Synchronize architecture maps and MCP context across all your repositories.
- [For agencies & consultancies](https://moxiedocs.com/for/agencies): Ramp up on client codebases fast and hand off self-updating documentation.
- [For enterprise & security-first](https://moxiedocs.com/for/enterprise): PR-gated documentation governance with predictable repo-based pricing.
## What developers say
Quotes from the Product Hunt launch and other reviewers:
- [Zaid Mallik](https://moxiedocs.com/#testimonials): "Context quality seems to be becoming a bigger bottleneck than model quality for a lot of agent workflows." (@zaidmallik · Product Hunt)
- [GlyphHarbor](https://moxiedocs.com/#testimonials): "Docs that travel into the coding assistant is the part that feels right here. A README sitting in GitHub is helpful, but the moment I'm in a Claude/Codex loop the question is whether the current rule is actually in the model's face." (@glyphharbor · Product Hunt)
- [MakerStack](https://moxiedocs.com/#testimonials): "Moxie Docs tackles the real problem of stale documentation by auto-generating docs and flagging drift on merge, which is smart." (Product review · MakerStack)
- [Paul Crinigan](https://moxiedocs.com/#testimonials): "The PR check is the part I would lead with. Docs rot because nothing in the workflow ever tells you they rotted, so a check that fails loudly on the diff is worth more than any amount of generation quality." (@paul_crinigan · Product Hunt)
- [Grace Lee](https://moxiedocs.com/#testimonials): "This feels useful because docs are starting to serve two audiences at once: humans reading the public knowledgebase, and AI agents using repo context while work is happening." (@grace_lee26 · Product Hunt)
- [Adrian Ciaschetti](https://moxiedocs.com/#testimonials): "The Friday Cleanup idea is nicely restrained. Batching doc drift into one reviewable PR, with nothing auto-merging, feels like a much easier habit for a team to trust." (@adriancia · Product Hunt)
## Pricing
Three plans, each with a 14-day free trial. Every plan can be billed monthly or annually; annual billing is two months free (about 17% off):
- [Free - $0/mo or $0/yr](https://moxiedocs.com/pricing): See it work on a real repo before you decide anything. No card required. Up to 1 repositories, 1 seat.
- [Starter - $29/mo or $290/yr](https://moxiedocs.com/pricing): For solo builders documenting a handful of private repos. Up to 5 repositories, 1 seat.
- [Pro - $79/mo or $790/yr](https://moxiedocs.com/pricing): Hands-off documentation for a growing team: weekly Recaps, automated Cleanup PRs, and room for many repos. Up to 15 repositories, 10 seats.
- [Team - $199/mo or $1,990/yr](https://moxiedocs.com/pricing): For organizations with a fleet of services: unlimited seats, priority indexing, and the highest capacity. Up to 50 repositories, unlimited seats.
## Product specifications
Deployment: Hosted SaaS. Connects to GitHub through a scoped, least-privilege GitHub App with read-only repository access; Moxie Docs never commits to your code and never merges anything - documentation arrives only as reviewable pull requests.
MCP endpoint: A Model Context Protocol server at https://moxiedocs.com/api/mcp serves conventions, docs, doc gaps, and verified commands to AI coding agents such as Cursor, Claude Code, Codex, and other MCP-aware clients, so agents make one scoped lookup instead of re-crawling the repository each prompt.
Pricing tiers: Free $0/mo, Starter $29/mo, Pro $79/mo, Team $199/mo. Every plan includes a 14-day free trial and is priced per repository, not per seat; annual billing is about two months free.
Core capabilities: Automated codebase documentation, documentation drift detection on every merge, weekly Friday Cleanup PRs, interactive codebase search, MCP context for AI coding agents, and hosted public knowledgebases.
## Developer resources
- [OpenAPI specification](https://moxiedocs.com/openapi.json): Machine-readable description of the REST API (list docs, check documentation drift), with typed request/response schemas and bearer-token auth.
- [MCP server](https://moxiedocs.com/api/mcp): JSON-RPC 2.0 endpoint over Streamable HTTP (protocol version 2025-06-18). Server card at https://moxiedocs.com/.well-known/mcp/server-card.json.
- [API catalog](https://moxiedocs.com/.well-known/api-catalog): RFC 9264 linkset pointing at both the MCP and REST service descriptions.
- [CLI](https://moxiedocs.com/mcp): `npx moxie-docs setup` - open-source CLI published on npm at https://www.npmjs.com/package/moxie-docs (source https://github.com/Jackalope-Dev/Moxie-Docs-MCP). Signs in, configures your editor, and installs the skill in one command.
- [Self-serve API tokens](https://moxiedocs.com/mcp): Create a repository-scoped token from the dashboard (Settings > MCP tokens) as soon as a repository finishes its first index - self-serve on every plan including the free tier, no sales call required.
## Comparisons
- [Comparisons overview](https://moxiedocs.com/comparisons): All comparison pages at a glance.
- [Moxie Docs vs Mintlify](https://moxiedocs.com/vs/mintlify): Codebase context vs. docs-site agent: Moxie Docs maps your architecture and serves it to coding agents over MCP; Mintlify's AI agent drafts updates to your docs site.
- [Moxie Docs vs Jamdesk](https://moxiedocs.com/vs/jamdesk): Generation vs. publishing: Moxie Docs writes and maintains docs from your code; Jamdesk hosts the MDX you author yourself, with flat pricing and reader-facing AI chat.
- [Moxie Docs vs Context7](https://moxiedocs.com/vs/context7): Your codebase vs. public library docs: Moxie generates and maintains documentation for your own repository and serves it over MCP; Context7 injects up-to-date third-party library docs into your prompts.
- [Moxie Docs vs Swimm](https://moxiedocs.com/vs/swimm): Self-serve vs. sales-led: zero-maintenance codebase wikis from continuous repo analysis, no discovery call required to see pricing or get started.
- [Moxie Docs vs Docusaurus](https://moxiedocs.com/vs/docusaurus): Generation vs. publishing: Moxie writes and maintains docs from your source and serves them to agents over MCP; Docusaurus is an open-source static site generator for docs you write and host yourself.
- [Moxie Docs vs GitBook](https://moxiedocs.com/vs/gitbook): Code-native vs. cross-functional wiki: code-coupled, AI-generated docs without GitBook's per-seat wiki licensing.
- [Moxie Docs vs Google Code Wiki](https://moxiedocs.com/vs/codewiki): Private repos vs. public preview: Moxie Docs documents your private codebase and opens pull requests; Google Code Wiki is a free, read-only wiki for public repos.
- [Moxie Docs vs Confluence](https://moxiedocs.com/vs/confluence): Automated code synchronization vs. legacy text graveyard: docs stay coupled to the code instead of drifting out of date.
- [Moxie Docs vs Repowise](https://moxiedocs.com/vs/repowise): Hosted GitHub App vs. self-hosted daemon: Moxie Docs opens docs-only pull requests with nothing to install, instead of running your own indexing daemon.
- [Moxie Docs vs Merge.dev](https://moxiedocs.com/vs/merge): Native codebase MCP vs. unified integrations API: zero-code MCP servers that serve repository context to agents.
- [Moxie Docs vs Cursor Rules](https://moxiedocs.com/vs/cursorrules): Generated vs. hand-written: Moxie Docs serves repo conventions via MCP that update themselves from your code, instead of rule files someone has to write and maintain by hand.
- [Moxie Docs vs DocuWriter.ai](https://moxiedocs.com/vs/docuwriter): Docs-only pull requests vs. a docs Space: both generate repository-wide docs and an MCP server, but Moxie Docs routes updates through GitHub pull requests and adds a public knowledgebase site.
Head-to-head comparisons between documentation tools:
- [Mintlify vs GitBook](https://moxiedocs.com/compare/mintlify-vs-gitbook): Developer MDX workflow vs. a block editor for mixed teams.
- [GitBook vs Confluence](https://moxiedocs.com/compare/gitbook-vs-confluence): Purpose-built docs platform vs. the general enterprise wiki.
- [Mintlify vs Confluence](https://moxiedocs.com/compare/mintlify-vs-confluence): Code-coupled MDX docs vs. a decoupled enterprise wiki.
- [Mintlify vs Docusaurus](https://moxiedocs.com/compare/mintlify-vs-docusaurus): Managed MDX platform vs. free open-source static site generator.
- [GitBook vs Docusaurus](https://moxiedocs.com/compare/gitbook-vs-docusaurus): Block editor for mixed teams vs. self-hosted Markdown sites.
- [Mintlify vs Swimm](https://moxiedocs.com/compare/mintlify-vs-swimm): Polished public docs hosting vs. code-anchored onboarding walkthroughs.
- [Mintlify vs Jamdesk](https://moxiedocs.com/compare/mintlify-vs-jamdesk): Premium docs platform with an AI Agent vs. flat-priced MDX hosting.
## Learn
Guides on MCP, documentation, and AI development practices:
- [Learn hub](https://moxiedocs.com/learn): Browse all guides.
- [What is an MCP server?](https://moxiedocs.com/learn/what-is-an-mcp-server): The plain-English explainer on Model Context Protocol servers.
- [Best MCP servers for coding](https://moxiedocs.com/learn/best-mcp-servers-for-coding): Twenty MCP servers worth connecting to your coding agent.
- [Living documentation](https://moxiedocs.com/learn/living-documentation): Why docs drift, and what it takes to keep them true.
- [AGENTS.md vs CLAUDE.md vs llms.txt](https://moxiedocs.com/learn/agents-md-vs-claude-md-vs-llms-txt): Three files for AI context - and what each is actually for.
- [What is documentation drift?](https://moxiedocs.com/learn/what-is-documentation-drift): Why docs go stale, how to spot it, and how teams fix it.
- [AI coding agent context](https://moxiedocs.com/learn/ai-coding-agent-context): How Cursor, Claude Code, and Codex learn your private codebase.
- [CLAUDE.md guide](https://moxiedocs.com/learn/claude-md-guide): How to manage and optimize CLAUDE.md for Claude Code.
- [AGENTS.md guide](https://moxiedocs.com/learn/agents-md-guide): What AGENTS.md is, what goes in it, and how to keep it current.
- [What is context engineering?](https://moxiedocs.com/learn/what-is-context-engineering): The discipline that replaced prompt engineering - and why it matters.
- [How to write a .cursorrules file](https://moxiedocs.com/learn/how-to-write-a-cursorrules-file): The ultimate guide to structuring custom instructions for Cursor.
## Resources
- [Blog](https://moxiedocs.com/blog): Articles on documentation, codebases, and AI developer tooling. Full RSS feed at /blog/feed.xml.
Recent articles:
- [How to Write a Runbook: A Field Guide for On-Call Engineers Who Will Read It at 3 a.m.](https://moxiedocs.com/blog/how-to-write-a-runbook): Most runbooks fail the moment they are needed: the command was renamed, the dashboard moved, the owner left. Learn how to write a runbook that a tired engineer can follow, a template you can copy, and how to keep it from rotting.
- [How to Write a CONTRIBUTING.md: A Guide Humans and Coding Agents Actually Follow](https://moxiedocs.com/blog/how-to-write-a-contributing-md): Most CONTRIBUTING.md files are either a code of conduct with a link to the issue tracker or a wall of process nobody reads. A practical guide to writing one that gets a first pull request merged: what goes in it, what to leave out, how it fits next to AGENTS.md, and how to keep it true.
- [How to Write a Pull Request Description: A Template Reviewers and Agents Can Both Use](https://moxiedocs.com/blog/how-to-write-a-pull-request-description): Most pull request descriptions restate the title or the prompt. A practical guide to writing PR descriptions that speed up review and survive in git history: what to include, a copy-paste GitHub template, examples, and how to keep agent-written descriptions honest.
- [Documenting APIs for AI Agents: OpenAPI, llms.txt, and MCP, and When Each One Matters](https://moxiedocs.com/blog/documenting-apis-for-ai-agents): AI agents now read your API docs before developers do. What OpenAPI, llms.txt, Markdown pages, and an MCP server each give an agent, which one to build first, how to write descriptions an agent can act on, and how to keep all of them in sync with the code.
- [Full context file](https://moxiedocs.com/llms-full.txt): Inlined guides, tool summaries, and FAQ for AI ingestion.
- [FAQ](https://moxiedocs.com/faq): Answers on doc generation, GitHub access and security, MCP context, supported languages, and pricing.
- [Security](https://moxiedocs.com/security): How Moxie Docs handles repository data and access.
- [Contact](https://moxiedocs.com/contact): Reach the team.
## FAQ
### What is Moxie Docs?
A hosted service that connects to GitHub, generates searchable codebase docs from source, keeps them current on merge, and serves that context to AI agents over MCP. Doc updates arrive as pull requests your team reviews.
### What happens after I connect a repo?
Moxie runs a first full index, generates docs and conventions, then re-indexes on every merge. PR checks for description alignment, documentation gaps, and conventions start with the next pull requests.
### Do PR checks block merge, or only warn?
By default they warn. Moxie posts GitHub check runs (Moxie Docs / Description, Moxie Docs / Documentation, Moxie Docs / Conventions) with advisory conclusions on findings - they do not fail the check and will not block merge on their own. To make them a hard gate, require those check names in your repository's branch protection rules.
### Will Moxie change my code automatically?
No. Doc updates are reviewable docs-only PRs. Description alignment only edits the PR description text. Merge control stays with your team.
### How does MCP cut agent cost?
Agents pull conventions, docs, gaps, and verified commands instead of re-crawling the repo every prompt - fewer tokens and fewer wrong guesses. When code is undocumented, MCP surfaces the gap instead of inventing APIs.
### Can I publish a public help center for my users?
Yes — the Public Knowledgebase (Beta) turns your repo into a hosted help site on your-team.moxiedocs.app, written for end users, developers, or both. Every page is human-approved before it goes live; internal agent notes stay out of the public site until you publish. Available on every plan during the beta.
### Is indexing one-shot or continuous?
Continuous. The first index builds the baseline. Every merge re-checks affected docs, flags drift and gaps, and keeps MCP context current. On Pro and Team, Friday Cleanup batches remaining fixes into one docs-only PR you review and merge - nothing auto-merges.
### How much does it cost?
Free forever for one repository, no card required. Beyond that, Starter is $29/mo, Pro is $79/mo, and Team is $199/mo, each with a 14-day free trial. Annual billing saves about two months. Low-churn single-repo teams often prefer annual Starter or the one-time $5 trial pass on /pricing.
### Does Moxie Docs work with private GitHub repositories?
Yes. Built for private repos. The GitHub App is scoped to only the repos you choose, tokens are encrypted server-side, and code is used only to generate documentation and MCP context for your workspace.
### What programming languages does Moxie Docs support?
Documentation and search work with any GitHub repos
