Nitrosend
An AI-native email platform docs site combining product guides, MCP tool reference, CLI docs, and OpenAPI reference in one Sourcey build.
Features demonstrated
- Product guides and concepts written in MDX
- MCP tool reference generated from a nitrosend.mcp.json snapshot
- OpenAPI reference generated from the live API spec
- CLI documentation in the same navigation model
- Static deployment with clean URLs and no docs runtime
Nitrosend is a live product docs site built with Sourcey for an AI-native email platform. It is useful as an example because it is not only an API reference and not only a guide site. The docs combine product onboarding, MCP integration guides, generated MCP tool reference, CLI documentation, and generated REST API reference in one build.
The result is a single docs surface for both human users and agents.
Source
The docs are wired from several inputs:
- MDX guides for onboarding, authentication, product concepts, integrations, and CLI usage;
nitrosend.mcp.jsonfor the MCP tools tab;- the public OpenAPI spec at
https://api.nitrosend.com/openapi.yamlfor the API reference tab; - a single
sourcey.config.tsthat defines the tabs, groups, theme, logo, search highlights, and deployment shape.
Output
The live site publishes product docs, MCP reference, CLI docs, and REST API
reference under one design system with shared navigation and search. The static
build also emits llms.txt, llms-full.txt, sitemap.xml, and
search-index.json from the same documentation graph.
Why it matters
Nitrosend shows the Sourcey shape for AI-native products: the docs need to serve developers reading in a browser, AI tools connecting through MCP, and API consumers inspecting REST endpoints. Keeping those surfaces in one site avoids a split between guides, API reference, and agent-facing documentation.