Edit Knowledge Base drafts with an agent
Updated October 8, 2026 · 2 min read
On this page
Once connected through MCP, your coding agent can review articles and save changes as drafts. You can publish those drafts yourself from the Knowledge Base Editor.
A safe first task
Ask your agent:
“Read my Knowledge Base drafts. Check the setup instructions for unclear steps. Propose improvements, then save the agreed changes as drafts. Preserve formatting, images, links, and custom blocks. Do not publish.”
Your connection needs Edit drafts permission to save changes.
What the tools do
Tool | Purpose |
get_context | Confirm the workspace, permissions, and content format |
list_articles | List articles in draft or published view |
search_articles | Search articles in the chosen view |
get_article | Read the full article and its current revision |
update_article | Save an existing article's title or content as a draft |
preview_site_publication | Show all pending site changes without publishing |
publish_site | Publish the reviewed site version, with publication permission |
The agent must choose draft or published view explicitly. A draft can differ from the article your customers currently see.
The current MCP tools update existing articles. Create new pages and change navigation, topics, or site settings in the Knowledge Base Editor.
Review the saved draft
Open Knowledge Base Editor.
Reload to load the latest draft.
Review changed articles, including formatting and links.
Check navigation and Page storage.
Select Publish changes when you are ready.
Review the full summary, then confirm publication.
An MCP edit saves the Knowledge Base draft in Supahelp. It does not edit Markdown files on your computer and does not publish the public help center.
If you ask the agent to publish
Publishing is site-wide. It includes every pending article, navigation, branding, homepage, and visibility change, including changes made by teammates. There is no “publish only this article” MCP action.
Ask the agent to show the complete publication preview. Review all changes and explicitly approve before it calls the publication tool. If unwanted changes are included, resolve them in the editor and ask for a fresh preview.
A preview expires after ten minutes. A changed draft also needs a fresh preview. Your agent's own approval policy can prevent publication even when the connection has permission; you can still publish from the editor.
Request form questions are published separately in the Request form Editor.
Concurrent edits
If someone edits the Knowledge Base while your agent is working, saving can fail because the draft version changed. Have the agent reread the latest draft and reapply only the intended edits.
Never ask it to overwrite another person's changes to bypass a version conflict.
After publishing
Check the public help center. AI search preparation may continue after publication, so customer Ask Supa can take longer to pick up the new content.