Build source-owned API and MCP documentation with Sourcey
Use Sourcey to turn OpenAPI, MCP, Doxygen, godoc, rustdoc, MkDocs, and Markdown sources into static documentation, search, code samples, changelogs, roadmaps, and LLM context exports.
npx skills add agentskillexchange/skills --skill build-source-owned-api-and-mcp-documentation-with-sourcey
Use Sourcey when an agent or operator needs to produce and maintain source-owned documentation from technical inputs that already exist in a repository: OpenAPI specs, MCP tool definitions, Doxygen XML, Go docs, Rust docs, MkDocs navigation, and Markdown guides. Sourcey builds a static site with reference pages, guides, search, code samples, changelog and roadmap pages, plus llms.txt and llms-full.txt context exports.
What this skill actually does
The repeatable workflow is concrete: install Sourcey, run sourcey init to detect or configure documentation sources, define tabs with adapters such as openapi(), mcp(), doxygen(), godoc(), rustdoc(), mkdocs(), or Markdown, preview with sourcey dev, then publish static output with sourcey build. Invoke it instead of using a hosted docs dashboard when the docs should be generated from repository-owned sources and reviewed in code. The scope boundary is documentation build automation and LLM-readable context export, not a generic CMS, SDK, API platform, or MCP server listing.
Inputs and prerequisites: Sourcey CLI, Node.js 20 or newer, and repository-owned OpenAPI, MCP, Doxygen, godoc, rustdoc, MkDocs, or Markdown documentation sources..
Setup notes: Install with npm install -g sourcey , brew tap sourcey/tap && brew install sourcey , docker run -v “$PWD”:/docs sourcey/sourcey , or nix run github:sourcey/sourcey . Start a project with sourcey init , preview with sourcey dev , and build static output with sourcey build .
Source and verification boundary: use https://sourcey.com/docs as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.