Or just build your own remote MCP server for docs? It's easy enough now that the protocol and supporting SDKs have stabilized.

Most folks are familiar with MCP tools but not so much MCP resources[0] and MCP prompts[1]. I'd make the case that these latter two are way more powerful and significant because (most) tools support them (to varying degrees at the moment, to be fair).

For teams/orgs, these are really powerful because they simplify delivery of skills and docs and moves them out of the repo (yes, there are benefits to this, especially when the content is applicable across multiple repos) on top of surfacing telemetry that informs usage and efficacy.

Why would you do it? One reason is that now you can index your docs with more powerful tools. Postgres FTS, graph databases to build a knowledge base, extract code snippets and build a best practices snippet repo, automatically link related documents by using search, etc.

[0] https://modelcontextprotocol.io/specification/2025-06-18/ser...

[1] https://modelcontextprotocol.io/specification/2025-06-18/ser...

I think that might make sense for teams or people working in multiple repos. Maybe less so for individuals working on a side project.