Problem

An average MCP documentation server subsystem can't easily follow nested resources recursively, specifically if the content markup does not convey full URLs to be fetched subsequently. For example, the resource about CrateDB reference documentation's index page clearly demonstrates the situation.

There is a little innocent-looking backlog item, which is a leftover work item from the initial sweep of distilling a rough outline, where this obstacle has not been considered yet on a few spots.

Details

The problem refers to the spots in cratedb-outline.yaml outlined below. It needs additional work in the spirit of curating ingredients optimally for this use case.