[Feature]: Unified repo and docs site documentation

[rnett]

Problem Description

Many libraries, including mine, don't have all of their documentation available in the repo. Some of it is generated when publishing a docs site, or permanently lives on external sites.

While context7 does support redirecting to the docs site, sometimes there is information in the repository that is not in the docs site, and the repository is often much easier to parse.

Proposed Solution

Instead of forcing us to use either the docs site or the repository, it would be helpful if we could attach multiple sources (e.g. repo, docs site) to a single library.

Alternatives Considered

No response

Priority

Would improve my workflow

Additional Context

No response

[rnett]

My particular library is repo/docs. The repo is generally superior, but the actual API docs are only available on the site, because they are generated from the source comments on CI.

Other victims of this pattern include Gradle, React (with multiple sites), Kotlin, and I'm sure many others.

[enesgules]

Hi Ryan, sorry for the late response here. This is a known issue that we haven't found a way to fix so far. There are quite a lot of duplicates between two sources and we have to mitigate that when parsing too. For now we offer both for agents to query but this is a known issue on our side

[rnett]

In the meantime, some updates to the mcp tool description describing that this is common and that agents may want to check both docs might be helpful. IME agents tend to choose one source and then only use that.