# dubstack full AI context

Canonical URL: https://dubstack.ai
Status: Launching soon with early access available.

## Summary
dubstack helps technical teams create, publish, maintain, and query documentation from Git-backed sources. The platform combines a docs dashboard, hosted documentation sites, an editor, API playgrounds, public read-only MCP endpoints, AI assistant retrieval, agent workflows, and Theme Studio for advanced visual customization.

## Audience
- Developer relations teams
- API platform teams
- Product engineering teams
- Technical writers
- Internal platform teams
- Startups building developer-facing products

## Capabilities
- Git-native documentation publishing from customer-owned repositories
- MDX authoring with cards, callouts, tabs, accordions, code blocks, reusable snippets, and API reference pages
- Interactive API playgrounds and generated endpoint snippets from OpenAPI specifications
- Hosted docs sites with search, navigation, previews, custom domains, and analytics
- Public read-only MCP endpoints so agents can search and read published documentation
- AI assistant experiences for answering questions from published docs with linked sources
- Agent workflows for drafting documentation updates from code, feedback, assistant conversations, and integrations
- Theme Studio and Canvas Layout for Enterprise-grade visual customization
- Migration paths from existing public repositories through preview, claim, and adopt flows

## Differentiators
- Docs are Git-backed instead of being trapped in a proprietary content store.
- The same docs can serve humans, AI assistants, and MCP-connected agents.
- The product combines documentation hosting, editing, API playgrounds, workflows, and visual design in one platform.
- Enterprise teams can keep strict control over branding, access, integrations, and deployment workflows.

## Documentation sections
### Getting started
Create a site, connect Git, use the hosted starter flow, and publish your first docs site.
- [Product overview](https://dubstack.ai/docs#getting-started)
- [Quickstart](https://dubstack.ai/docs#quickstart)
- [Connect Git](https://dubstack.ai/git-native-documentation)
- [Deploy docs](https://dubstack.ai/docs#deployment)

### Writing content
Author MDX with structured components, reusable snippets, code blocks, images, and tables.
- [MDX authoring](https://dubstack.ai/docs#writing-content)
- [Components](https://dubstack.ai/docs#components)
- [Code blocks](https://dubstack.ai/docs#code-blocks)
- [Reusable snippets](https://dubstack.ai/docs#snippets)

### API documentation
Document APIs with OpenAPI specs, endpoint pages, generated snippets, and interactive playgrounds.
- [API docs platform](https://dubstack.ai/api-documentation-platform)
- [API playground](https://dubstack.ai/api-documentation-platform#api-playground)
- [OpenAPI specs](https://dubstack.ai/api-documentation-platform#openapi)

### AI and MCP
Make docs useful to assistants and coding agents with retrieval, source links, and MCP access.
- [AI assistant](https://dubstack.ai/ai-assistant-for-docs)
- [AI documentation platform](https://dubstack.ai/ai-documentation-platform)
- [MCP docs platform](https://dubstack.ai/mcp-docs-platform)
- [Documentation workflows](https://dubstack.ai/documentation-workflows)

### Theme Studio
Use visual editing and Canvas Layout for branded Enterprise documentation experiences.
- [Theme Studio](https://dubstack.ai/theme-studio)
- [Canvas Layout](https://dubstack.ai/theme-studio#canvas-layout)
- [Enterprise controls](https://dubstack.ai/theme-studio#enterprise)

## Use-case pages
### AI Documentation Platform | dubstack
URL: https://dubstack.ai/ai-documentation-platform
dubstack turns developer documentation into a reliable source of truth that can be read by people, searched by assistants, and queried by agents through public MCP endpoints.

Key points:
- Publish AI-ready docs from Git-backed MDX and structured configuration.
- Give users an assistant that answers from the published docs and links back to source pages.
- Expose public read-only MCP endpoints so coding agents can search and read documentation directly.
- Use workflows to keep docs fresh as code, feedback, and product changes land.

#### Why AI-ready docs matter
AI tools are becoming a primary interface for developer research. If documentation is not structured, crawlable, and source-linked, assistants either ignore it or answer from stale third-party context.
- Clear canonical pages help AI systems identify the product and its use cases.
- Source-linked assistant responses build trust with developers and support teams.
- Agent-readable documentation reduces repeated manual answers from engineering teams.

#### How dubstack supports AI experiences
dubstack combines hosted documentation, search, assistant retrieval, MCP, and Git workflows so the same source content can support multiple AI surfaces.
- Published docs are available to the user-facing assistant.
- Public MCP endpoints let external agents search and read the docs site.
- Dashboard workflows can draft documentation updates for review instead of silently changing production docs.

### API Documentation Platform | dubstack
URL: https://dubstack.ai/api-documentation-platform
dubstack helps teams publish API references alongside guides, examples, generated snippets, and interactive API playgrounds from Git-backed content.

Key points:
- Upload or connect OpenAPI specifications for API reference content.
- Show generated examples and reusable snippets for endpoints.
- Keep API docs in the same Git workflow as guides and product docs.
- Let users test API behavior from an interactive playground experience.

#### A complete API documentation surface
API docs are more useful when reference pages, guides, code examples, and endpoint testing live together instead of being split across tools.
- Reference pages describe endpoints and schemas.
- Guides explain how developers should use the API in real workflows.
- Playgrounds let developers test quickly without leaving the docs.

#### Git-backed API docs
dubstack keeps documentation changes reviewable. Teams can connect repositories, preview changes, and publish through the same workflow they already use for engineering changes.
- Docs changes can be reviewed through pull requests.
- Preview deployments help teams validate docs before publishing.
- Git ownership avoids content lock-in.

### Git-Native Documentation | dubstack
URL: https://dubstack.ai/git-native-documentation
dubstack keeps documentation source in Git while providing hosted docs sites, dashboard editing, previews, and publishing workflows.

Key points:
- Connect documentation repositories instead of copying content into a locked content store.
- Use pull requests and branch previews for documentation review.
- Let AI and workflow automation draft changes without bypassing Git review.
- Publish hosted docs from source-controlled MDX and configuration.

#### Why Git-native matters
Documentation is part of the product. Keeping it in Git preserves ownership, review history, and collaboration with engineering teams.
- Docs changes can follow normal engineering review processes.
- Content can be backed up, mirrored, and migrated more easily.
- Agents can create draft changes without direct production writes.

#### Hosted publishing without losing source control
dubstack provides the hosted docs experience while Git remains the source of truth for content and configuration.
- MDX files define documentation pages.
- dubstack.json defines site metadata, navigation, theme, and behavior.
- Sync and preview flows keep published docs aligned with repository state.

### MCP Docs Platform | dubstack
URL: https://dubstack.ai/mcp-docs-platform
dubstack gives documentation sites public read-only MCP access so compatible agents can query docs without scraping or guessing.

Key points:
- Public docs can expose MCP tools for search and read-only filesystem-style access.
- Agents can retrieve authoritative docs content with URLs and page paths.
- MCP access is separate from authenticated authoring tools for customers.
- Read-only public access protects customer docs while improving agent usability.

#### Public MCP for documentation readers
A public docs site should be useful to humans and agents. MCP gives agents a structured way to search and read published documentation.
- Search tools return relevant pages and snippets.
- Read tools expose published docs files without write access.
- Agents can cite the same public URLs that human users can open.

#### Clear boundary from authoring access
Public MCP is for reading published docs. Authenticated authoring and workflow actions belong to customer-owned dashboard and agent surfaces.
- Public readers get search and read-only access.
- Site owners control writing through authenticated dashboard and Git workflows.
- This split keeps public discovery useful without exposing privileged operations.

### AI Assistant for Documentation | dubstack
URL: https://dubstack.ai/ai-assistant-for-docs
dubstack docs can include an assistant that answers from published content, points users back to source pages, and helps teams understand where docs need improvement.

Key points:
- Answer questions from published documentation content.
- Show source links so users can verify the answer.
- Use assistant question trends to identify missing or confusing docs.
- Keep assistant behavior configurable by site and tier.

#### Better answers without leaving the docs
Documentation users often need a direct answer before they know which page to read. A docs assistant can shorten that path while still linking back to authoritative pages.
- Users can ask natural-language questions.
- Answers can include relevant docs links.
- Teams can use question trends to improve content coverage.

#### Built around published docs
The assistant should answer from the documentation site rather than inventing product behavior. dubstack is designed around retrieval and source-linked answers.
- Published docs remain the source of truth.
- Advanced retrieval can be configured behind the platform boundary.
- Enterprise controls can shape assistant instructions and behavior.

### Documentation Workflows | dubstack
URL: https://dubstack.ai/documentation-workflows
dubstack workflows help teams draft docs updates from product changes, code changes, feedback, and assistant conversations while keeping humans in the review loop.

Key points:
- Draft content updates from source code changes and product updates.
- Generate changelog drafts and improvement suggestions.
- Use assistant questions and user feedback to find documentation gaps.
- Run maintenance workflows for broken links, SEO metadata, translations, and grammar.

#### Automation with review
Documentation automation is safest when it drafts changes for review instead of bypassing the source-of-truth workflow.
- Workflows can create targeted update drafts.
- Git review keeps teams in control.
- Run history and context make automation auditable.

#### Signals that create better docs
Useful workflows start from real signals: code changes, feedback, support questions, assistant trends, and product releases.
- Code changes can trigger docs review.
- Feedback can identify stale or unclear pages.
- Assistant questions can reveal missing documentation.

### Theme Studio | dubstack
URL: https://dubstack.ai/theme-studio
Theme Studio gives Enterprise teams a visual layer for layout, branding, components, and custom documentation experiences while keeping content structured.

Key points:
- Customize layout, colors, branding, and components visually.
- Use Canvas Layout for premium documentation experiences.
- Keep docs content and configuration structured under the same platform.
- Gate advanced visual customization for Enterprise use cases.

#### Visual control for advanced teams
Some documentation sites need more than a standard docs shell. Theme Studio provides a visual design surface for teams that need deeper branding and layout control.
- Canvas Layout supports richer page structure.
- Visual controls reduce repetitive CSS work.
- Teams can build reusable presentation patterns.

#### Structured docs underneath
Visual customization should not break documentation operations. dubstack keeps docs content, navigation, and configuration structured while adding a design layer on top.
- Content remains compatible with docs workflows.
- Navigation and metadata stay configurable.
- Enterprise teams can align docs with brand requirements.

## FAQ
### What makes dubstack AI-ready?
dubstack focuses on structured docs, source-linked retrieval, public MCP access, and Git-backed workflows so AI systems can read and cite authoritative documentation.

### Does dubstack replace human documentation review?
No. AI workflows draft and assist, while Git-backed review keeps humans in control of production documentation changes.

### Can dubstack document APIs and guides together?
Yes. API references, quickstarts, tutorials, and conceptual guides can live in the same docs site and navigation system.

### Does dubstack support OpenAPI?
Yes. The platform is designed around OpenAPI-backed API references, playgrounds, and generated examples.

### Do docs have to live in Git?
Git-backed documentation is the recommended path because it preserves ownership and review. Hosted starter flows can help teams begin quickly before deeper repository setup.

### Can AI workflows still respect Git review?
Yes. The intended workflow is to draft changes and open reviewable updates, not silently mutate production documentation.

### Is public MCP read-only?
Yes. Public documentation MCP is intended for search and reading published docs, not editing customer content.

### Why expose docs through MCP?
MCP gives agents a structured interface to retrieve current docs content instead of relying only on general web search or stale model memory.

### Can the assistant answer from docs content?
Yes. The assistant is designed to use published documentation as the primary answer source and return source links where possible.

### Can teams customize assistant behavior?
The platform is designed for site-level assistant configuration, with advanced controls intended for higher tiers.

### Can workflows directly change docs?
The safer operating model is draft-first: workflows prepare changes for review through Git-backed processes.

### Which docs maintenance tasks can be automated?
Common tasks include changelog drafts, content improvements, translations, broken link fixes, SEO metadata audits, and grammar corrections.

### Is Theme Studio for every plan?
Theme Studio is intended for Enterprise-grade customization where teams need deeper control over layout and branding.

### Does visual editing replace MDX?
No. Theme Studio controls presentation and layout while docs content remains structured and workflow-friendly.