Moxie Docs
Living docs + MCP context for your GitHub repos
155 followers
Living docs + MCP context for your GitHub repos
155 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
Moxie Docs
Moxie Docs
Fantastic idea! Wondering if there is a document update every time the repo content changes? Does it run periodically? or is it all one and done (I doubt it!)
Moxie Docs
@rachid_abadli Every opened PR triggers a pass / check! Along with any AI agent utilizing the MCP, and routine checks every few hours. If docs drift from code changes - we find, fix, and surface that!
@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!
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
Really keen to test this out and see how it differs from using pre-commit documentation update hooks, which is my current setup. One quick question for ya - how do you handle the case where the docs are right and the code is wrong? On a bad merge, "sync to code" would happily overwrite the doc that describes the intended behavior. Does drift detection ever flag the code side, or is source always treated as ground truth?
Congrats on the launch! On the PR checks that keep docs honest, does it block the merge if docs go stale, or just leave a comment flagging what needs updating?