Moxie Docs

Moxie Docs connects to your GitHub repositories via a scoped GitHub App and generates architecture pages, convention summaries, and module walkthroughs cited directly to source code. It re-indexes on every merge, flags stale or missing documentation as advisory PR checks, and opens weekly "Friday Cleanup" pull requests so teams can review and merge docs fixes without anything auto-merging. Built by Jackalope Digital LLC, the product is actively available with a 14-day trial.

What It Is

Moxie Docs is a living documentation platform for software teams. It sits between your GitHub repository and your AI coding agents, continuously generating and updating documentation from source code and serving that context to tools like Cursor, Claude Code, and Codex over the Model Context Protocol (MCP). The core problem it addresses is documentation drift — the gap that widens between written docs and the actual codebase as code ships faster than anyone can document it.

How the Workflow Runs

The product operates in three phases:

• Setup (once): Install the scoped GitHub App on chosen repos, start the trial, and run the first index. Moxie reads source, tests, docs, and history, then produces architecture pages, convention rules, gap reports, and an MCP endpoint.
• Every PR and merge: Advisory PR checks flag stale or missing docs before merge. When code lands, affected documentation is re-checked, regenerated with cited diffs, and queued for review. RFCs citing never-built paths are not treated as deletions.
• Every Friday: A single docs-only pull request batches the week's documentation drift for team review. Nothing auto-merges; the team holds the merge button.

MCP Context Layer for AI Agents

Every plan includes an MCP server endpoint at /api/mcp with OAuth and bearer-token access. MCP-compatible agents and editors — including Cursor, Claude Code, Windsurf, Codex, Cline, JetBrains, and others — can query it for current documentation, verified conventions, and open gaps instead of re-crawling the repository on every prompt. The product exposes MCP tools including moxie.get_doc_gaps, moxie.get_doc_impact, and moxie.propose_doc_update, so missing docs can land in the same PR as the code change.

Public Knowledgebase (Beta)

A newer feature lets teams publish a hosted help center from the same reviewed documentation. Teams choose an audience — end users, developers integrating an API, or both — and Moxie drafts articles from the codebase. Drafts stay private until a human publishes them. The knowledgebase is hosted on a moxiedocs.app subdomain, with custom domains described as coming soon on Pro and Team plans.

Security and Access Model

Moxie connects through a GitHub App scoped only to the repositories the team selects. Tokens are encrypted server-side. Secrets, environment files, and dependency folders are skipped during indexing. Documentation changes are proposed exclusively as draft pull requests — the team reviews and merges every one. Branch protection integration allows teams to require Moxie's PR checks as hard gates before merge.

Language and Repository Support

Documentation and search work with any GitHub repository. The product recognizes TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig, with the deepest structured convention analysis (symbol and import graphs) available for TypeScript/JavaScript and Python. Large monorepos are supported with incremental re-indexing after the initial baseline; ignored paths can be configured to skip generated folders and vendored dependencies.