Why a repository is not enough

MCP projects are small pieces of infrastructure, but their value depends on the details around them: which systems they connect, how they authenticate, what they expose and where they fail. A source repository alone is rarely enough context.

I wanted one place where I could answer those questions without making somebody search through a README, old issues and release tags. Each page links back to the source but keeps the practical information beside it.

What I publish with a project

  • A concise statement of the problem the server solves.
  • Requirements and a repeatable installation path.
  • Supported clients, services and known constraints.
  • A changelog that separates fixes from breaking changes.
  • Direct links to source, issues and the relevant evidence.

What came next

The first listing is now live: the Octopus Energy Private MCP. I will add another project only when its installation path and basic documentation are ready for somebody else to follow.