Documents that people and their AI agents write together, with a person reviewing what the agent changes.
An agent (Claude Code, Codex, Cursor or any MCP client) connects to DocForge with an API key and writes into the same document the person has open in the browser. Two kinds of document:
- Markdown documents. By default, every agent write becomes a suggestion the person reviews as a diff, hunk by hunk, before it lands. Versions, comments, a quality gate run by the agent, publishing and public links come with it.
- Layout documents — pages and slides made of components placed on a grid (text, tables, KPIs, charts, steps, timelines, cards). The agent never sees the page: it reads a text map of each page, and every write tells it what the layout did on its own (what moved, grew or split). The person edits the same document in a visual editor. The engine is
@docforge-lib/layout, an open-source library.
Experimental — DocForge is a work in progress and may change or be discontinued at any time.
flowchart LR
person["Person<br/>(browser)"] -->|HTTPS| frontend["frontend<br/>React SPA"]
agent["AI agent<br/>(MCP client)"] -->|"Streamable HTTP<br/>API key"| mcp["mcp<br/>Python, FastMCP"]
frontend -->|"REST + SSE<br/>Clerk JWT"| backend["backend<br/>FastAPI"]
mcp -->|"REST<br/>API key"| backend
backend --> postgres[("Postgres")]
backend -->|"validate, apply ops,<br/>map, render"| layout["layout-service<br/>Node, @docforge-lib/layout"]
| Package | What it is |
|---|---|
packages/backend |
FastAPI API: documents, versions, suggestions, sharing, layout documents, plans and billing. Owns storage and permissions. |
packages/frontend |
React 19 + Vite app: the Markdown editor with review, the layout editor, the dashboard and the public pages. |
packages/mcp |
The MCP server agents connect to: 42 tools over Streamable HTTP, plus writing guides and recipes as resources. |
packages/layout-service |
The layout library's HTTP server, packaged for the backend (which is Python and cannot run it in-process). |
DocForge never calls a language model itself. Agents run on the person's side, with their own model and credentials; DocForge is where their work is stored, checked and reviewed.
- Running DocForge locally — the stack in Docker, or each package on its own; tests; connecting an agent.
- Architecture, part by part:
- Overview — services, request paths, and the decisions behind them
- Backend — data model, auth, permissions, the review loop, plans
- Layout documents — the library, the layout service, revisions and publishing
- MCP server — transport, authentication, tools and resources
- Frontend — app structure, the two editors, the design system
- Deploying — a single VPS with Docker Compose, CI/CD, backups and rollback.
- Contributing — branches, checks and commits.
- MCP reference: tools and setup.
git clone https://github.com/maxjneto/doc-forge.git && cd doc-forge
cp packages/backend/.env.example packages/backend/.env # set CLERK_JWKS_URL
cp packages/frontend/.env.example packages/frontend/.env # set VITE_CLERK_PUBLISHABLE_KEY
docker compose up --buildOpen http://localhost:5173. Signing in needs a (free) Clerk development instance; to look at every screen without one, run npm run dev:preview in packages/frontend. The details are in docs/development.md.
| Layer | Technology |
|---|---|
| Frontend | React 19, TypeScript, Vite, Tailwind CSS v4, CodeMirror 6 |
| Backend | Python 3.11, FastAPI, SQLAlchemy 2 (async), Alembic, Pydantic v2 |
| Layout engine | @docforge-lib/layout (TypeScript, fontkit), resvg for page images |
| Agents | MCP over Streamable HTTP (Python MCP SDK) |
| Data | PostgreSQL 16; Redis optional (SSE fan-out across replicas) |
| Auth and billing | Clerk (people), hashed API keys (agents), Stripe |
| Analytics | PostHog: in the browser only after cookie consent, anonymous on the server otherwise, never document text (docs) |
| Infrastructure | Docker Compose on a VPS, Caddy (automatic HTTPS), GitHub Actions → GHCR → SSH deploy |
Licensed under the MIT License.