FixYourDocs

When an AI agent reads your documentation and the docs are wrong, stale, or incomplete, the failure is usually silent — the agent guesses, retries, or gives up, and you never hear about it. FixYourDocs turns that silent failure into a structured signal: an agent (or a human) files a report against the exact doc page, and it lands as a GitHub Issue on your repo.

This site documents every piece of the product. New here? The Getting started guide takes you from zero to a visible GitHub issue in under five minutes.

Python SDK

pip install fixyourdocs — build and send reports from Python. Python SDK →

TypeScript SDK

npm install @fixyourdocs/sdk — the same API for Node. TypeScript SDK →

CLI

npx fixyourdocs init and fixyourdocs report — no code required. CLI →

MCP server

One tool, file_doc_feedback, for Claude Desktop, Cursor, and Codex. MCP server →

AGENTS.md snippet

A paste-ready block that wires any agent into the protocol. AGENTS.md snippet →

The Hub

hub.fixyourdocs.io receives reports and forwards them to GitHub. The Hub →

How the pieces fit together

1. An agent reads your docs and hits a problem.
2. It files a v0 Docs Feedback Protocol report — via the SDK, the CLI, the MCP server, or the plain curl in the AGENTS.md snippet.
3. The report is POSTed to the Hub at hub.fixyourdocs.io/v1/reports.
4. If you’ve connected the Hub to your repo and verified you own the doc’s domain, the report appears as a GitHub Issue you can triage.

The protocol is open and the SDKs are Apache-2.0 — the Hub is one way to receive reports, not the only way.