MCP server

@fixyourdocs/mcp-server is a Model Context Protocol server that exposes a single tool — file_doc_feedback — so any MCP client can file a Docs Feedback Protocol report as one tool call when it hits broken, incorrect, outdated, missing, or unclear docs.

No phone-home, no telemetry: the server contacts the Hub only when an agent explicitly calls the tool.

Run it

It’s designed to run via npx, so there’s nothing to install up front — your client launches it on demand over the standard MCP stdio transport:

npx -y @fixyourdocs/mcp-server

Wire it into your client

Each client has its own config file, but the shape is the same: a named server entry with command + args.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "fixyourdocs": {
      "command": "npx",
      "args": ["-y", "@fixyourdocs/mcp-server"]
    }
  }
}

Restart Claude Desktop — file_doc_feedback should appear in the tool list.

Cursor

Edit ~/.cursor/mcp.json (or your workspace’s .cursor/mcp.json):

{
  "mcpServers": {
    "fixyourdocs": {
      "command": "npx",
      "args": ["-y", "@fixyourdocs/mcp-server"]
    }
  }
}

Codex

Edit ~/.codex/config.toml:

[mcp_servers.fixyourdocs]
command = "npx"
args = ["-y", "@fixyourdocs/mcp-server"]

Verify it

Use the MCP inspector to list the tool and send a fixture report:

npx @modelcontextprotocol/inspector npx -y @fixyourdocs/mcp-server

The inspector UI lists file_doc_feedback, accepts a report, and shows the { id, url } returned by the Hub.

Reporting third-party docs (consumer side / Mode B)

There are two ways to adopt FixYourDocs, and the MCP server is the primary carrier for the second one:

• Mode A — first-party. A docs maintainer pastes the AGENTS.md snippet into their repo so agents working in it offer to report that repo’s docs — asking first.
• Mode B — consumer-side. You — a developer building something unrelated — install this server into your own, global client config (the same config blocks shown above, in your user-level config rather than one project’s). When your agent consults a third-party library’s, API’s, or framework’s docs and they turn out to be broken, it can offer to file a report on them, even though that project never instrumented its own repo. The report routes to whoever has verified that doc’s domain (or claimed its GitHub Pages site) with the Hub.

Because Mode B points an agent at the open internet on your behalf, the tool is safe-by-default:

• Ask before sending. The file_doc_feedback tool description instructs the agent to offer and wait for your confirmation, not to fire on its own.
• Public docs only. A doc_url that is localhost, a private / internal host, an RFC 1918 or link-local address, or a non-https:// page is refused before anything leaves your machine.
• Opt-out honoured. Before posting, the client fetches the doc host’s /.well-known/docs-feedback.json; if it says opt_in: false the report is refused. Results are cached per host for 24h.

Note

The consent prompt ships in this server’s tool description; the privacy guard and opt-out discovery are enforced by the SDK client the server builds on (@fixyourdocs/sdk 0.3.0 and later). They activate once this server is built against that SDK version.

Note

The server is registered in the MCP Registry as io.fixyourdocs/mcp-server. Reports go to hub.fixyourdocs.io; they become GitHub Issues once the doc owner has connected the Hub and verified their docs — by domain (DNS) or a GitHub Pages claim.

Tool schema & environment variables The mcp-server README documents the full file_doc_feedback schema and how to point at a different hub.