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.

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 domain.

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