DocsAlot MCP Connector - Maintain your help-center by asking Claude, Cursor or Codex
by•
Create and update your knowledge base from Claude, Codex, or any compatible MCP client. Ask DocsAlot to add a page, fix an error, or improve your help center. It finds the relevant content, makes changes, creates a new version, and publishes, all from your existing workflow. See what questions users ask in your help center, discover what’s missing, and use those insights to improve your docs and decide what to build next.
Replies
This is much needed! Can I onboard through claude?
@shawn_esquivel you most certainly can. Just point claude to our landing page, it should figure everything out.
Looking real good! A lot of good things are coming out in this area, will certainly be trying it out! Does the mcp support creation for web documentations (the ones we would have in a product's site, for example?)
@matheus_paranhos1 Thanks, do let me know if you run into any friction. Feel free to book a call.
https://cal.com/faizan-khan-18shuq/30min
No, unfortunately the MCP won't have access to your source-code so it can't modify things. It only has access to the help-center hosted on DocsAlot. It can listen to source-code as a read-only thing but thats about it.
Would love to chat about what you have in-mind. Could be a good feature to add.
Which types of help centers does DocsAlot support. do you support Astro/nimbus.
@r_sri_ram No we don't at the moment, but can ship it for you.
Mind booking a call, happy to buy you lunch in return :)
https://cal.com/faizan-khan-18shuq/30min
congrats on the launch Faizan!
can the MCP key be limited to drafts only? I'm fine with an agent writing drafts all day, but I'd still want a person to be the one who hits publish.
@ahmadhajj yes, agent wont publish until you say so. We have a full CMS. So you push a draft to save a version, and then you publish to make it live.
You can also revert versions. and MCP can be limited to roles based on who can publish and who cant
@new_user_2790a57d4d Congratulations. And happy product launch.
the "creates a new version, and publishes, all from your existing workflow" part is the one thing I'd want a safety rail on. we keep our own internal docs in a similar loop where Claude proposes edits, and the failure mode isn't that it writes something wrong, it's that it writes something confidently wrong and nobody reviews it before it goes live because the whole point was to skip a step. does DocsAlot publish straight from the MCP call, or is there a draft/approve step before a Claude-made edit actually replaces what's live for your end users?
@galdayan Thanks Gal. So we have a two step process, as shown in the 2nd video. First one is PUSH, which saves a version on the CMS. This allows the human to share that version with other people in the team. Once everything is ready, only then someone can PUBLISH.
And every version is retained historically. And you can easily revert back by changing the published version.
@new_user_2790a57d4d that answers it cleanly, push/publish as a real gate rather than a single auto-commit step. the version history + revert is the part that actually matters to me though, since that's what turns "the AI published something wrong" from a slow-motion incident into a one-click rollback. are reverts scoped per-page or does rolling back one page risk touching others that referenced it