Ask questions of all stored content (Knowledge Articles), bring back raw content (and sources) for LLM to process (summarise) from an Experience Site.

Simplified API Approach

With Knowledge Articles only, you primarily need:

1. Knowledge REST API

• /services/data/vXX.X/support/knowledgeArticles/ - Main endpoint
• /services/data/vXX.X/support/dataCategoryGroups/ - For categories/topics

2. SOQL via REST API (as backup/alternative)

• Query KnowledgeArticleVersion object directly
• More flexibility for custom fields and complex filtering

Key Benefits

• Single content model - no need to handle multiple content types
• Built-in search capabilities - Knowledge has native full-text search
• Structured metadata - articles have titles, summaries, categories, etc.
• Version control - automatic versioning and published status
• Permissions model - built-in visibility controls

Recommended MCP Server Architecture

1. Authentication → Connected App with Knowledge permissions
2. Content Discovery → List all published articles via Knowledge API
3. Content Extraction → Fetch article details including:
   - Title, Summary, Content (HTML/Rich Text)
   - Categories, Topics, Data Categories
   - Publication status, language, version
4. Indexing → Store for your Q&A system
5. Updates → Periodic sync or webhook-based updates

Sample Knowledge API Calls

• List articles: GET /services/data/v58.0/support/knowledgeArticles/
• Get article details: GET /services/data/v58.0/support/knowledgeArticles/{id}
• Search articles: GET /services/data/v58.0/support/knowledgeArticles/?q=searchterm

This approach eliminates the complexity of handling multiple content types and gives you a clean, consistent data model to work with. The Knowledge API is specifically designed for this use case.