Tips & Tricks

Create a Complete Help Center with Claude and MCP

February 24, 2026

Build a fully-functional help center in minutes by chatting with Claude. Learn how to create collections, organize topics, and write articles using natural language.

Introduction

Building a help center traditionally involves navigating dashboards, filling out forms, and manually organizing content. With AppGram MCP and Claude, you can create an entire help center just by describing what you need in plain English.

In this tutorial, we'll build a complete help center from scratch—including collections, topic flows, articles, and even interactive decision trees—all through conversation with Claude.

Prerequisites

Claude Code with AppGram MCP connected (see our connection guide)
Your AppGram project ID (run list_projects to find it)

Step 1: Create a Help Center Collection

A collection is the top-level container for your help center. Think of it as a versioned snapshot of all your documentation.

Just ask Claude:

"Create a help center collection called 'Help Center v1.0' for my project"

Claude will use the help_center_create_collection tool:

{
  "project_id": "your-project-id",
  "name": "Help Center v1.0",
  "version": "1.0.0",
  "description": "Main help center documentation",
  "is_live": true
}

The is_live: true flag makes this collection the active one displayed to users.

Step 2: Organize with Flows (Topic Categories)

Flows are topic categories that organize your articles. Each flow can display content differently:

list — Simple article list
accordion — Expandable FAQ-style
decision_tree — Interactive yes/no troubleshooting
wizard — Step-by-step guided process

Ask Claude to create multiple flows:

"Create these help center flows: Getting Started (list), Account & Billing (accordion), Troubleshooting (decision tree), and Setup Guide (wizard)"

Claude will create each flow with appropriate settings:

// Getting Started flow
{
  "collection_id": "...",
  "name": "Getting Started",
  "slug": "getting-started",
  "icon": "Rocket",
  "color": "#3b82f6",
  "display_type": "list"
}

// Troubleshooting flow
{
  "collection_id": "...",
  "name": "Troubleshooting",
  "slug": "troubleshooting",
  "icon": "HelpCircle",
  "color": "#ef4444",
  "display_type": "decision_tree"
}

Step 3: Write Help Articles

Now populate your flows with actual content. Claude can write the articles for you based on your product description.

Ask Claude:

"Write a getting started article explaining how to create an account and set up a first project. Make it beginner-friendly with clear steps."

Claude creates the article with proper HTML formatting:

{
  "flow_id": "getting-started-flow-id",
  "title": "Create Your First Project",
  "slug": "create-first-project",
  "article_type": "guide",
  "is_published": true,
  "content": "

`Welcome to AppGram!`

..." }

Bulk Article Creation

You can ask Claude to create multiple articles at once:

"Create these FAQ articles for Account & Billing: How to upgrade my plan, How to cancel subscription, How to update payment method, How to download invoices"

Claude will create each article with the faq article type, perfect for accordion display.

Step 4: Build a Decision Tree (Troubleshooting)

Decision trees guide users through yes/no questions to find solutions. They're perfect for troubleshooting flows.

Describe the troubleshooting flow to Claude:

"Create a troubleshooting decision tree for login issues. Start with 'Can you reach the login page?' If yes, ask 'Are you seeing an error message?' and branch to specific solutions."

Claude creates interconnected decision nodes:

// Root node
{
  "flow_id": "troubleshooting-flow-id",
  "question": "Can you reach the login page?",
  "answer_yes_node_id": null,  // Will link after creating child
  "answer_no_node_id": null
}

// Yes branch
{
  "flow_id": "troubleshooting-flow-id",
  "question": "Are you seeing an error message?",
  "parent_id": "root-node-id"
}

// Leaf node with solution
{
  "flow_id": "troubleshooting-flow-id",
  "question": "Try clearing your browser cache",
  "article_id": "clear-cache-article-id"  // Links to detailed article
}

After creating nodes, Claude will link them together using help_center_update_decision_node.

Step 5: Create a Setup Wizard

Wizards guide users through multi-step processes. Each step shows content and optionally links to detailed articles.

Ask Claude:

"Create a 5-step setup wizard: 1) Create account, 2) Verify email, 3) Create organization, 4) Invite team members, 5) Create first project"

Claude creates sequential wizard steps:

{
  "flow_id": "setup-guide-flow-id",
  "step_number": 1,
  "title": "Step 1: Create Your Account",
  "content": "

Visit our signup page and enter your email...

", "article_id": "detailed-signup-article-id" // Optional link to full article }

Real-World Example: Complete Help Center in One Conversation

Here's how a full conversation might look:

You: I need a help center for my SaaS app. It's a project management tool. Create a complete help center with:

Getting Started section with basic guides
Features section explaining projects, tasks, and team collaboration
Billing FAQ
Troubleshooting decision tree for common issues

Claude: I'll create a complete help center for your project management app. Let me start by creating the collection and flows...

[Claude creates collection, 4 flows, 12 articles, and a decision tree with 8 nodes]

Claude: Done! I've created your help center with:

✅ Help Center v1.0 collection (live)
✅ Getting Started (3 guides)
✅ Features (4 articles on projects, tasks, teams, integrations)
✅ Billing FAQ (4 FAQs in accordion format)
✅ Troubleshooting (decision tree with 8 nodes covering login, sync, and notification issues)

Useful Commands Reference

Collections

"List all help center collections"
"Create a new collection version 2.0"
"Make collection X the live version"

Flows

"Show all flows in my help center"
"Create an FAQ flow for billing questions"
"Change the Troubleshooting flow to use accordion display"
"Reorder flows: Getting Started first, then Features, then FAQ"

Articles

"List all articles in Getting Started"
"Write an article about password reset"
"Update the pricing article with new plan details"
"Unpublish the beta features article"
"Search for articles mentioning 'API'"

Decision Trees

"Show all nodes in the troubleshooting tree"
"Add a new branch for 'mobile app issues'"
"Link node X to the cache clearing article"

Wizards

"Create step 6 for the setup wizard"
"Update step 3 content with new screenshots"

Pro Tips

1. Let Claude Write Your Content

Instead of writing articles yourself, describe your feature and let Claude generate the documentation:

"Write a comprehensive guide about our Kanban board feature. Cover creating boards, adding columns, moving cards, and using filters."

2. Batch Operations

Claude can create multiple items efficiently:

"Create 5 FAQ articles covering: refunds, plan changes, payment methods, invoices, and enterprise billing"

3. Content Migration

If you have existing documentation, paste it and ask Claude to migrate it:

"Here's our old FAQ page content: [paste]. Convert this into help center articles in the FAQ flow."

4. Iterate Quickly

Made a mistake? Just ask Claude to fix it:

"The article slug should be 'getting-started' not 'gettingstarted', please update it"

Conclusion

Building a help center with Claude and AppGram MCP transforms documentation from a tedious task into a conversation. You can:

Create complete help centers in minutes
Generate professional documentation from product descriptions
Build interactive troubleshooting flows
Update and maintain content through natural language

Start by connecting AppGram MCP to Claude, then simply describe the help center you need. Claude handles the rest.