Server data from the Official MCP Registry
File structured docs-feedback reports to the FixYourDocs hub via a file_doc_feedback tool.
File structured docs-feedback reports to the FixYourDocs hub via a file_doc_feedback tool.
Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
19 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: FIXYOURDOCS_HUB_URL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-fixyourdocs-mcp-server": {
"env": {
"FIXYOURDOCS_HUB_URL": "your-fixyourdocs-hub-url-here"
},
"args": [
"-y",
"@fixyourdocs/mcp-server"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.
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 host — to the repo of the maintainer who has verified (DNS-TXT) that they own that domain, opening a GitHub Issue so maintainers triage it with the tools they already use.
This repository contains the reference implementation of the hosted product running at fixyourdocs.io — SPA, REST API, and the MCP client package — alongside the docsfeedback.org Starlight site that hosts the open spec. The production CDK pipeline lives in a separate private infrastructure repository. The wire protocol it implements is specified in the open at docsfeedback.org.
fixyourdocs/ org)| Repo | Purpose | Licence |
|---|---|---|
| fixyourdocs/fixyourdocs (this repo) | Hosted product (SPA + REST API + MCP package) and the docsfeedback.org Starlight site | FSL-1.1-Apache-2.0 |
| fixyourdocs/protocol | Open spec of the Docs Feedback Protocol — message shapes, JSON Schemas, versioning | Apache-2.0 (code) + CC-BY 4.0 (prose) |
| fixyourdocs/sdk-python | Reference Python SDK for the protocol | Apache-2.0 |
| fixyourdocs/sdk-typescript | Reference TypeScript SDK for the protocol | Apache-2.0 |
| fixyourdocs/agents-md-snippet | Drop-in AGENTS.md / CLAUDE.md / .cursorrules block that teaches an agent to file reports | Apache-2.0 |
| fixyourdocs/manifesto | The "why" — the case for an open protocol between agents and docs maintainers | Apache-2.0 (code) + CC-BY 4.0 (prose) |
If you want to understand the protocol, start at fixyourdocs/protocol. If you want to emit reports from an agent, use one of the SDKs or drop in the AGENTS.md snippet. If you want to run your own backend, read on.
/v1/reports* plus Cognito-protected /v1/orgs/* and /v1/integrations/*; an async-invoked forwarder Lambda turns each accepted report into a GitHub Issue.@fixyourdocs/mcp-server, run via npx -y @fixyourdocs/mcp-server over stdio) exposing a single file_doc_feedback tool. Calls POST https://hub.fixyourdocs.io/v1/reports to file a v0 report; the hub routes it to a GitHub Issue on the repo of the maintainer who has verified ownership of the doc's domain.Requires Node.js 20 and pnpm 10.
pnpm install
pnpm -r typecheck
pnpm --filter @fyd/frontend dev # SPA on http://localhost:5173
pnpm --filter @fyd/docsfeedback-site dev # docs site on http://localhost:4321
pnpm --filter @fyd/e2e test # Playwright suite
The frontend points at whatever API_BASE_URL you configure at runtime via frontend/public/env.js (not committed — generate it at deploy time from your stack outputs).
The production hosted variant runs on AWS Lambda + API Gateway HTTP API + DynamoDB + Cognito + CloudFront, deployed via AWS CDK v2. The CDK app itself is operated from a separate private infrastructure repository; a public reference template will follow once the hosted variant is stable.
Self-hosters writing their own CDK app today can match the contract by passing the following env vars through to the backend Lambdas:
| Variable | Required | Notes |
|---|---|---|
CDK_DEFAULT_ACCOUNT (or FYD_AWS_ACCOUNT) | yes | Target AWS account ID. |
CDK_DEFAULT_REGION (or FYD_AWS_REGION) | no | Defaults to us-east-1. Don't change unless you understand the CloudFront cert constraint. |
FYD_ROOT_DOMAIN | no | Defaults to fixyourdocs.io. The SPA, API, and Cognito callback URLs derive from it. |
FYD_HOSTED_ZONE_ID | yes | Route 53 hosted zone ID for FYD_ROOT_DOMAIN. |
FYD_OPS_ALERT_EMAIL | yes | Subscribed to CloudWatch alarms + billing budget. |
FYD_GITHUB_REPO | no | org/repo allowed to assume the OIDC deploy role. |
FYD_COGNITO_DOMAIN_PREFIX | no | Cognito Hosted UI prefix. Defaults to fyd-auth-${account} so deployments don't collide (Cognito prefixes are globally unique per region). |
FYD_STACK_PREFIX | no | Prefix applied to all stack names. |
The agent-facing surface is the hub's POST https://hub.fixyourdocs.io/v1/reports endpoint. Reports are anonymous (rate-limited by IP) and conform to the v0 schema specified at docsfeedback.org/spec/v0 and in the protocol repo.
Two ways to wire an agent to it:
AGENTS.md block — paste the snippet from fixyourdocs/agents-md-snippet into your project's AGENTS.md / CLAUDE.md / .cursorrules. Works with any agent that reads those files; no MCP client required.mcp-server/ to expose a file_doc_feedback tool to clients that speak MCP (Claude Desktop, Cursor, …).PRs welcome. We use the standard Developer Certificate of Origin — sign your commits with git commit -s. Issues against this repo should be about the implementation; issues against the protocol repo should be about the wire format.
A CLA is required for non-trivial contributions (see fixyourdocs/.github for the text); the CLA-assistant bot will post a sign-off link on your first PR.
FSL-1.1-Apache-2.0. The Functional Source License keeps the code source-available with a non-compete carve-out for two years, then automatically converts each release to Apache 2.0. See LICENSE and fsl.software.
The protocol itself, the SDKs, and the AGENTS.md snippet ship under permissive licences (Apache 2.0 / CC-BY 4.0) so the open spec stays unencumbered regardless of what this repo does. See each repo's own LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.