Connect Docsheaf to the rest of your stack
Slack and GitHub built in, OAuth apps you build on a REST API for everything in the app, embeds for the tools your team already uses, and open formats in and out.
Available today: Slack notifications, Git Sync with GitHub with commit statuses, integration apps over OAuth, the REST API with scoped tokens, signed webhooks, an MCP server per site, embeds from YouTube, Vimeo, Loom, Figma and CodeSandbox, Markdown import and export, llms.txt, S3 or Cloudflare R2 storage and SMTP email. Coming soon: custom blocks and extensions that run inside Docsheaf, and Git Sync with GitLab.
Built in today
No marketplace to browse — these work out of the box, and your own apps install in a few clicks.
Slack
Post change requests, reviews, merges, comments and publishing to the channels you choose — with “Add to Slack” or an incoming webhook.
GitHub
Two-way Git Sync with a repository. Change requests opened from a push report their review back as a commit status.
Learn moreREST API
Everything in the app — content, change requests, sites, members — over JSON, described in OpenAPI.
Learn moreScoped tokens
API tokens that only read, or only reach one organization or a few spaces, and that can expire.
Your own apps
OAuth apps that admins install from your site, choosing the spaces they reach. They call the API and hear events at their webhook URL.
Learn moreWebhooks
Signed events for change requests, reviews, comments, content and publishing, retried until they arrive.
Learn moreMCP server
A Model Context Protocol server for every published site, so agents can search and read your docs.
Learn moreEmbeds
Paste a YouTube, Vimeo, Loom, Figma or CodeSandbox link to embed it. Other links render as link cards.
Markdown in and out
Import Markdown with GitBook-style blocks, and read every page back as Markdown — llms.txt included.
Learn moreRuns on infrastructure you choose
Docsheaf stores data in services you already trust, configured with environment variables — no code changes.
PostgreSQL
All content, revisions and settings live in Postgres. Migrations run automatically on start-up.
AWS S3 or Cloudflare R2
Uploads go to an S3-compatible bucket in production, or to local disk on a single server.
Any SMTP provider
Sign-up codes, password resets and security alerts are delivered through the SMTP service you configure.
Coming soon
Custom blocks and extensions
Blocks and extensions that run inside Docsheaf and on your published sites.
Git Sync with GitLab
The same two-way sync, with GitLab repositories.
Learn moreFrequently asked questions
What can I connect Docsheaf to today?
Slack channels and GitHub repositories out of the box, and anything that can call a REST API with a token or receive a webhook. Inside pages you can embed YouTube, Vimeo, Loom, Figma and CodeSandbox, and every site exposes Markdown, llms.txt and an MCP server for other tools to read.
How do I connect Slack?
In Organization settings → Integrations, choose “Add to Slack” (or paste an incoming webhook URL), then pick what the channel hears about. Restricted spaces stay out of channels unless you choose them.
Can I build my own integration?
Yes. For scripts and CI, a scoped API token is enough. For a product other teams install, register an app in Organization settings → Apps: admins install it with OAuth, choose the spaces it reaches, and it calls the REST API as their admin — at most like an editor — and hears events at its webhook URL. Blocks that run inside Docsheaf are on the roadmap.
Is there an app marketplace?
Not yet. Public apps are installed from a link their developer shares; the consent screen shows who built the app and what it can do, and admins can uninstall it at any time.
Which embed providers are supported?
YouTube, Vimeo, Loom, Figma and CodeSandbox render inline. Any other http(s) link is shown as a link card.
Do I need S3 or R2?
Not for a single server — uploads can be stored on local disk. For production, configure an AWS S3 or Cloudflare R2 bucket.
Accurate docs. Better answers.
Start writing for free, or talk to us about bringing your team and your existing docs.