By use case

Self-updating docs
Docs that rewrite themselves when your code changes.
AI doc generation
Point at a repo, get a full documentation site.
AI-ready docsNew
Answerable by Claude, Cursor, and any MCP client.
API & SDK referenceNew
Reference docs that never drift from your code.

By team

For startupsNew
Launch-ready docs before you launch.
For engineering teams
Docs in the repo, in sync with every merge.
For open source
Beautiful community docs, GitHub-native.
NewDocs your AI tools can readEvery Doccupine site ships an MCP server, so Claude, Cursor, and your own agents answer straight from your live docs.Explore MCP for docs
PricingDocsBlogSign InStart for free
Sign In
Category

Industry & Trends

Perspectives on docs-as-code, AI in technical writing, and platform engineering. Industry analysis and trends from the Doccupine team and community.

All posts

2 posts
Left: a bloated 400KB llms.txt file scrolling off the page. Right: a four-line llms.txt beside a folder of per-page .md files, with an arrow from an AI agent pointing at the .md files
Industry & Trends

llms.txt: what the spec actually says

Almost every llms.txt I open is doing too much and missing the one thing the spec actually recommends. The file itself takes four lines. The part people skip is the part an AI agent actually fetches.

Luan Gjokaj5 min read
A developer's IDE with an AI assistant pulling structured context from a documentation site
Industry & Trends

Documentation is the new SDK

AI agents have made documentation a runtime concern. The contract between your product and the developer ecosystem used to live in your SDK. Increasingly, it lives in your docs.

Luan Gjokaj6 min read
Back to all stories