The Commons is open, so you can bring its content, data and tools to the places your people already work: your intranet, content and collaboration tools, your own branded copy, your systems through an open data API, and AI assistants through MCP and connectors.
| Route | Best for | Effort | Keeping up to date | What you control | Technical help needed | Status |
|---|
Embedded pages hide the Commons menu, footer and page links, show a small link back to the source, and can take your accent colour. Links inside the embedded page stay embedded.
Read-only JSON files at fixed addresses, rebuilt with every release. No key, no sign-in and no tracking. Start with api/index.json, which lists every file, its version and, for knowledge files, the owning role and last review date.
api/releases.json or feed.xml from the published Commons.Check which connectors your organisation allows before you build the flow.
pip install -r requirements.txt in that folder.python -m dqkit.mcp_server, started in the folder that holds the data you want it to read. Many assistants take a settings block like the one below.The server is read-only, only reads files inside the folder it starts in (or DQKIT_MCP_ROOT), and makes no network calls.
| Aspect | How to tailor it |
|---|
Every page has Share this page under its title: copy the link to the page or the section you are reading, share with your device, by email, to Microsoft Teams or LinkedIn, copy embed code, or print.
with %s where the words go.dq, then type dq and your words in the address bar.Follow feed.xml in a feed reader or channel, or post releases automatically with a workflow (see the API examples).
Embed pages in SharePoint or Confluence spaces your teams already use, and link to sections from your own guidance so there is one source to maintain.