ClickHelp Release Notes: April 2026

This update introduces the ClickHelp MCP Server for AI-assisted documentation management, expands the ClickHelp API, and adds focused improvements for AnswerGenius widgets and Markdown workflows.

Manage ClickHelp documentation from AI agents

ClickHelp MCP Server helps turn product knowledge into structured ClickHelp content earlier in the documentation lifecycle. Specs, code changes, source files, and team conversations can become draft topics, TOC updates, and workflow changes while ClickHelp remains the source of truth for permissions, structure, review, and publishing.

This work can now start in AI tools such as Claude Desktop and Cursor. A developer can turn a spec, code change, or source file into a draft topic from the same environment where the source material already lives. A technical writer can use the same workflow to reorganize a TOC branch, update topic owners, or prepare a set of unpublished topics for review. See MCP Server Use Cases for more examples.

The connection uses the regular ClickHelp login flow, including SSO and 2FA. After login, AI tools act with the same permissions as the signed-in user. A user with read-only access, including a Power Reader account, can read the publications available to that account; a user with authoring rights can use the writing tools allowed by their ClickHelp permissions. AI-assisted work becomes part of the same documentation lifecycle instead of a separate copy-paste step. See Connect to MCP Server for setup steps.

The first version focuses on the draft-to-review part of documentation work: creating projects, creating and editing regular topics, updating assignee, owner, and status fields, and making supported TOC changes. Publishing and portal administration stay in ClickHelp, so documentation owners keep control over what goes live. Some advanced operations, including deletion, project import, and portal-level configuration, are not included yet. API documentation topics cannot be edited through MCP, and translated projects allow workflow-field updates only.

A cleaner API for automation and AI workflows

ClickHelp API v2 has cleaner REST patterns and a more consistent response structure. Project actions that previously shared one endpoint are separate operations in API v2, which makes the API easier to read, document, test, and use from developer tools.

API v1 remains supported and backward compatible. We also expanded API v1 with new methods for project creation, project publications, and Custom Workflow statuses and transitions, so existing integrations can use these capabilities without moving to API v2.

We are also moving public API documentation to OpenAPI. Development teams get a structured API description they can use in developer tools, generated clients, and AI-assisted integration workflows.

Teams can move to API v2 when they need the newer structure, cleaner response fields, or Markdown output.

API v2 can return topic content, search snippets, and AnswerGenius answers in Markdown. This makes ClickHelp content easier to use in AI workflows, internal tools, code repositories, and other systems that already work with Markdown.

We also simplified topic draft creation and added project-language metadata for multilingual integrations.

Choose sources for external AnswerGenius widgets

The external AnswerGenius widget now has its own source selection. You can choose which public publications it uses, so answers in an embedded assistant can be limited to the content you selected for that website or application.

Copy topics as Markdown

Authors can now copy a topic as Markdown directly from the authoring interface. Use it when you need clean, structured topic content for an AI prompt, issue, pull request, review thread, or a quick handoff to a developer without running a full export.

Improvements

• Feature pages for unavailable add-ons now explain what the feature does and how to request access from the same screen.
• Added a language selector to Next Reader UI for multilingual portals. Readers can switch between localized versions, and ClickHelp keeps the selected language across home pages, search results, and articles.
• Custom portal scripts can now read public publication data anonymously, making it easier to build branded publication selectors, language switchers, and home page elements.

Back
to top