FixYourDocs
Let your agent file structured documentation feedback from the repo straight into FixYourDocs so doc gaps get tracked in one hub.
Overview
FixYourDocs MCP is a MCP server for the Build phase that files structured documentation feedback reports to the FixYourDocs hub via file_doc_feedback.
What is this MCP server?
- Exposes a file_doc_feedback tool for structured docs-issue reports
- stdio npm package @fixyourdocs/mcp-server v0.1.1
- Optional FIXYOURDOCS_HUB_URL override (default https://hub.fixyourdocs.io)
- Pairs with fixyourdocs.io hub for centralized doc triage
- Lightweight MCP bridge—no broad browser or repo crawl surface
- Server schema version 0.1.1
- 1 primary tool surface: file_doc_feedback
- stdio transport via @fixyourdocs/mcp-server on npm
What problem does it solve?
Agents spot wrong or missing docs during coding but those findings vanish in chat instead of a trackable queue.
Who is it for?
Indie builders who already use or plan to use FixYourDocs and want agents to log doc issues with consistent fields during feature work.
Skip if: Teams that need autonomous doc rewrites, site search, or repo-wide doc linting without a FixYourDocs hub workflow.
What do I get? / Deliverables
Structured doc-feedback reports land in the FixYourDocs hub so you can triage and fix documentation like product bugs.
- Structured documentation feedback reports submitted to the FixYourDocs hub
- Repeatable agent workflow for logging doc gaps discovered during implementation
- Centralized doc-issue intake without custom webhook glue
Recommended MCP Servers
Journey fit
Documentation quality work sits in the build phase when you are shipping features and keeping guides accurate. The sole exposed workflow is filing doc feedback reports, which maps directly to the docs subphase rather than generic integrations.
How it compares
MCP doc-feedback intake, not a markdown authoring or static-site generator skill.
Common Questions / FAQ
Who is FixYourDocs MCP for?
Solo and small-team builders who maintain product docs and want their coding agent to file structured feedback into FixYourDocs instead of informal chat notes.
When should I use FixYourDocs MCP?
Use it during build and doc updates whenever the agent finds outdated steps, missing API fields, or broken examples and you want those issues queued in the hub.
How do I add FixYourDocs MCP to my agent?
Add the @fixyourdocs/mcp-server npm package as a stdio MCP server in Claude Code, Cursor, or Codex, and optionally set FIXYOURDOCS_HUB_URL if you do not use the default hub.