Webgora

Moxie Docs

Open Site

Moxie Docs automatically generates and maintains codebase documentation for GitHub repositories, then exposes repo context to AI agents through MCP. It helps engineering teams reduce documentation drift and give coding agents source-cited context.

Added on June 11, 2026

Moxie Docs Screenshot

Product Information

What is Moxie Docs?

Moxie Docs is an automated documentation system for GitHub repositories. It indexes a codebase, creates searchable docs, detects documentation drift when code changes, and can open cleanup pull requests. The product also serves repository conventions and source-cited context to AI agents through MCP. It is designed for engineering teams that want living documentation without assigning manual doc maintenance to developers every week.

How to use Moxie Docs?

  1. Connect Moxie Docs to a GitHub repository with the required access scope.
  2. Let it index the codebase and generate initial documentation from source files.
  3. Review the generated docs, conventions, and cited source references.
  4. Use drift detection or cleanup pull requests to keep documentation aligned with code changes.
  5. Connect AI agents through MCP so they can retrieve current repo context.

Core Features

  • Automated repo docs — Generates documentation from GitHub repositories instead of starting from a blank wiki.
  • Searchable codebase context — Makes architecture, conventions, and implementation notes easier to find.
  • Drift detection — Flags docs that no longer match merged code changes.
  • Cleanup pull requests — Can propose documentation fixes as part of maintenance workflows.
  • MCP support — Serves current repository context to AI coding agents.
  • Source citations — Grounds answers and generated docs in specific files or paths.
  • Read-only default — Starts with safer repository access for teams evaluating the tool.

Use Cases

  • Onboarding engineers — Give new teammates an up-to-date map of a GitHub codebase.
  • AI coding agent context — Provide agents with source-cited repository conventions through MCP.
  • Documentation maintenance — Catch and fix drift after code changes are merged.
  • Architecture discovery — Search how subsystems, APIs, and workflows are implemented.

You May Also Like