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/
@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
Documentation becomes much more valuable when people trust it's always current.
Curious—do teams adopt Moxie Docs to save documentation effort, or because it reduces the friction of sharing reliable knowledge?