Codex + Moxie Docs

MCP context for Codex - conventions before the first edit

Codex works faster when it already knows your build commands, module boundaries, and documentation gaps. Moxie Docs indexes your GitHub repository and exposes that context through MCP tools formatted for agents.

  • Compact lookups. Replace dozens of file reads with scoped MCP queries for conventions and docs.
  • Doc-impact hints. See which docs and gaps apply to the files Codex plans to change.
  • Same index as your team. Humans search the workspace; agents read it over MCP - one source of truth.
Set up with one promptConnect GitHub repoMCP overview

Set up Codex with Moxie

  1. Step 1

    Index your repo

    Connect GitHub and run the first index on the repository Codex will edit.

  2. Step 2

    Add the MCP endpoint

    Run moxie-docs setup or paste the MCP config from your dashboard.

  3. Step 3

    Prompt for context first

    Ask Codex to read conventions and gaps before implementing the task.

$ npx moxie-docs setup

Sign in, configure your editor, and install the skill - one command.

FAQ

Does Moxie work with Codex out of the box?+

Yes. Moxie exposes a standard MCP endpoint. Run npx moxie-docs setup after connecting a repository, or copy the MCP config from your dashboard once the first index finishes.

What context do agents receive?+

Conventions, generated docs, open doc gaps, verified commands, and doc-impact hints for the files an agent plans to change - all scoped to the repository you selected.