fixyourdocs avatar

FixYourDocs

fixyourdocs/fixyourdocs

Adds a `file_doc_feedback` tool that sends structured reports about documentation gaps, outdated sections, or contradictions to the FixYourDocs hub at fixyourdocs.io. When an AI agent hits a problem reading your docs, it can file a report with the URL, issue type, and context. The hub routes reports by domain to the verified maintainer's GitHub repo, opening an issue for triage. The wire format is an open protocol specified at docsfeedback.org. Useful if you maintain documentation and want a structured feedback channel from AI agents back to your issue tracker, or if you're building an agent that needs to surface doc quality problems it encounters while helping users follow procedures.

tool
1
transport
STDIO
env var
1
last updated
Jun 10, 2026

Tools

1 tools

Public tool metadata for what this MCP can expose to an agent.

file_doc_feedbackExposed by the @fixyourdocs/mcp-server package (run over stdio) to file a v0 documentation feedback report via the hub.

Exposed by the @fixyourdocs/mcp-server package (run over stdio) to file a v0 documentation feedback report via the hub.

No parameter schema in public metadata yet.

Sponsors

Configuration

FIXYOURDOCS_HUB_URLdefault: https://hub.fixyourdocs.io

Override the hub base URL. Defaults to https://hub.fixyourdocs.io.

Readme

Licence

This repository is licensed under FSL-1.1-Apache-2.0. After 2 years (2028-05-22) each release automatically converts to Apache 2.0 per the FSL transition clause. See LICENSE for the full text and https://fsl.software for background.

FixYourDocs

A structured feedback channel between the AI agents that read your documentation and the humans who maintain it.

AI agents read documentation to help their users follow procedures. When they hit a gap, outdated section, contradiction, or dead end, today the signal is dropped: the user gets a worse answer and you never hear about it. FixYourDocs gives those agents a place to put the signal: they file a structured report through an open protocol, and the hub routes it — by the report's doc URL — to the repo of the maintainer who has verified that they own those docs (a domain, or a GitHub Pages site), opening a GitHub Issue so maintainers triage it with the tools they already use.


View the full README on GitHub

Details

Repository
github.com/fixyourdocs/fixyourdocs
Website
fixyourdocs.io
Package
@fixyourdocs/mcp-server
Transport
STDIO
Registry
MCP registry, active