Reorganize and publish help-center articles from your AI tool

A help-center product added an MCP so users can answer internal questions and create, move or publish articles.

Difficulty
BeginnerOur rating
Time to build
Not reportedOur estimate
Monthly cost
Not reported
Revenue
Not reportedWe only show revenue the source states
Engagement
0 replies to HN commentComment in “Ask HN: Who is using MCP in production?” (198 points, 201 comments) · fetched Oct 15, 2026

What they did

peaxkl’s company HappySupport added a highly requested MCP server.

How it went

Users reorganize their help center, answer questions internally and edit or publish articles. It also made importing docs from obscure providers easy.

Worth knowing

Imports from odd providers no longer need per-provider integrations.

Builder recipe

Our own starting point, written from the source. Adapt it to your setup.

Stack

  • Help-center MCP
  • Claude or ChatGPT

Steps

  1. Collect the incoming channel (inbox, form, tickets) into one workflow.
  2. Have the model classify and extract fields, returning structured JSON.
  3. Route or draft replies; keep a human approval step for anything customer-facing.
  4. Log results and review misclassifications weekly.

Starter prompt

Find help articles that overlap, propose a new structure with categories, and draft merged versions. Do not publish yet.

Tags

Read the original

Related use cases

The Daily 5.

Five real AI agent use cases each morning, each with a recipe and a source. Plus a Sunday roundup. Free.