Integrations & Developer Tools
Connect DocStar to the rest of your stack. Send events to your systems, sync docs from GitHub, put the DocStar editor or search inside your own product, and call your documented APIs from the terminal.
#
Integrations and tools
| Tool | Use it to | Who it's for |
|---|---|---|
| Webhooks | Notify your systems when pages are created, changed, published or deleted | Developers, ops |
| GitHub Sync | Write docs as Markdown in a GitHub repo and sync them to DocStar on every push | Docs-as-code teams |
| Embed the Editor | Put the DocStar editor inside your own app so your users can write documents | Product teams |
| Search SDK | Add DocStar search and Ask AI to any website with one script | Web teams |
| DocStar CLI | Turn published API docs into terminal commands and AI tools | Developers, API users |
#
Where to find them
Most integrations are set up per collection:
- Open a collection.
- Click Settings in the left sidebar.
- Open the Webhooks or Integrations tab.
Embed settings appear when you open an Embed collection. The Search SDK and the CLI only need your collection's ID or docs domain.
#
Before you start
- API token: GitHub Sync and API calls need one. See API Tokens.
- Collection ID: shown in the collection's URL in DocStar, after
/collection/. - Collection slug: the short, permanent name you chose when you created the collection. The CLI and MCP tools use it.
- Published docs: the Search SDK and the CLI only see published pages. See Publish Pages.
#
Connect AI assistants
To let Claude, ChatGPT, Cursor or other AI assistants read and edit your DocStar workspace, or call your documented APIs, see MCP.
Was this helpful?