Moxie Docs
Living docs + MCP context for your GitHub repos
217 followers
Living docs + MCP context for your GitHub repos
217 followers
Moxie Docs indexes your GitHub repo once, then puts that understanding where the work happens: repo context inside your AI agents over MCP, a searchable docs workspace, and PR checks that keep documentation honest.
This is the 2nd launch from Moxie Docs. View more
Moxie Docs: Knowledgebases
Launching today
Now in Beta: Public Sites!
Create auto-generated, public-facing help centers and knowledgebases at https://moxiedocs.app. Features rich layouts, white-labelling, full search, and no vendor lock-in. Integrates directly with Changelog! Example: https://docs.moxiedocs.app
Also shipped:
Webhooks & Slack integration for indexing/PR alerts
UI/UX pagination & bulk action improvements
DB/infrastructure upgrades for faster loading
Continued improvements on document generation quality
Free Options
Launch Team / Built With
the PR check that keeps docs honest is the part that would actually get me to adopt this - every docs tool I've tried eventually goes stale because nothing forces the update at merge time. does it block the PR outright when docs drift too far from the code change, or just flag it as a warning someone can ignore?
Moxie Docs
@omri_ben_shoham1 We run via the checks in GitHub as well as leave comments in the PR - so from the GitHub side you can configure a passing moxie docs check to be required. But our Friday recap is meant to solve that directly as well, every Friday we open a PR automatically that fixes, deletes, updates, etc any docs that may have drifted from recent changes or weren’t already documented.
@cadenjs - love the idea, but don't like the subscription model too much. What if you only need this for 1 repo and the docs are only typically updated 2 to 3 times a year? Paying a monthly fee seems excessive, are you not considering a pay as you go model for smaller projects? Perhaps something tiered based on usage volume rather than a flat monthly/annual subscription.
Moxie Docs
@codeandsea great question! We do offer free support for qualified open source projects, but a big chunk of the value is the MCP itself. We categorize your code based conventions, docs, context and surface it all directly to agents via skills and an MCP - so even if docs only update periodically (which often is not the case) the MCP will continually provide benefit by giving AI agents direct context and conventions.
If you’ve ever had to say “follow our conventions” or ask AI to update docs it immediately caused to drift from truth, that’s what we solve for.
@cadenjs - Understood, and thanks for getting back to me so quickly. Best of luck with everything!
This is interesting. What's the indexing latency on a large monorepo with frequent commits?
Moxie Docs
@dhiraj_patel5 indexing starts immediately and begins surfacing insights / opportunities immediately! Within minutes the MCP will have codebase context and conventions start getting populated.
For a full index depending on repo size could be up to 5/10 minutes - but the value is that it’s never a one time thing, we continually improve / re scan over time - code changes faster than ever with AI tooling so we directly connect to the tools where they work (AGENTS.md, skills, MCP, etc) so our detection has to keep up pace with any repos development speed.
Is this a kind of protection against accidental changes made by the AI?
Moxie Docs
@masterbek we don’t make any changes on your codebase! All documentation updates, changelog entries, and public knowledgebase pages are opened via a PR request to your connected codebase, or require a user to 1-click to publish (for changelog / knowledge bases).
We understand AI can make mistakes and the only thing worse than no docs is wrong docs. We surface suggestions but leave the power to decide when they ship in the hands of maintainers.
Moxie Docs
Hey all!
We've greatly expanded and improved our developer documentation & MCP tooling - giving internal devs useful docs that are always up to date, and tools for their AI agents that reduce token usage and improve code quality output. We've build a public open-source MCP server, a CLI setup tool, and a prompt to get setup easily in 1-paste.
The biggest ask we've seen was: How do we manage public-facing docs? Help centers? Knowledgebases?
Now you can! - https://moxiedocs.app/ Starting in Beta any Moxie Docs user can opt-in themselves to start using our Public Sites feature. This unlocks:
Automatically generated documentation for both developers and consumers targeted for public consumption. Rich with layouts, charts, codeblocks, internal linking, and more.
White-labelling - add your logo, brand color, and light instruction changes
Coming soon custom domains and remove Moxie Docs linking for Pro or higher plans
Fully hosted, you control what documentation is published, all exists in your code base no vendor lock-in, you own your data. Always.
Full document search, reading time, reading indicator, table of contents, documentation groupin
Integrates directly with our Changelog feature - get a hosted changelog directly linkable and tied to your help center
Check it out with our own dogfooding example 👉https://docs.moxiedocs.app/
What else has shipped?
Webhooks integration - set up any custom webhook endpoint to get alerted when moxie docs finishes indexing, PRs are opened, or Friday Recap is ready for review
Slack integration - set up the same alerts and summaries to any Slack workspace
Improved UI / UX for pagination, bulk actions, and more
Faster loading times app-wide, and an upgrade to our DB and infrastructure to improve performance
See what else is new on our hosted Moxie Docs changelog: https://docs.moxiedocs.app/changelog
The PR check is the real forcing function here. Quick question—when an agent hits undocumented code through the MCP, does it try to fill the gap or just work around it? That behavior probably determines whether this compounds your docs problem or solves it.
Congrats on the launch. Living docs plus an MCP server for the same repo is a smart pairing, most tools solve doc-drift or agent-context but not both from one source of truth. Before I'd point Public Sites at a client's docs: is there a filter step before publishing that catches anything meant to stay internal, a staging URL or an internal-only heading written into the markdown, or does that rely on the team keeping the source clean themselves?