Public documentation talks about the product, not its source tree
The MCP tool reference is generated automatically from the definitions registered by the Pekan server, which keeps the public documentation aligned with the tools an agent can actually call. The page previously explained that guarantee by publishing the internal repository path of the source file used by the site generator. That path was useful to a contributor working inside the Pekan codebase, but it was an implementation detail with no value to someone connecting an agent.
The page now describes the same behavior in product language: the reference comes directly from the live tool definitions when the website is built, so it cannot drift like a hand-maintained list. The internal path has been removed from the page summary, the explanatory note, metadata, and generated copies. The wider public website was also audited for similar references. Paths that tell users where Pekan writes configuration inside their own projects remain, as do required upstream license links and the website's normal asset URLs. Internal build scripts remain unchanged and unpublished.
Highlights
- The MCP reference no longer exposes Pekan's repository layout.
- Automatic generation is still explained clearly.
- Generated pages and metadata carry the revised copy.
- Necessary user-project paths and license links remain intact.