HelpNest exposes your knowledge base through llms.txt, MCP, and A2A — so any AI agent can discover, search, and query your help articles without custom integration.
Three protocols
From simple file fetches to stateful multi-turn conversations — choose the integration level that fits your use case.
Here's what we know
A static text file at /llms.txt that describes your help center in a format any LLM can read. Zero integration required — just fetch and parse.
Call these tools
Model Context Protocol gives AI assistants like Claude structured tool access to search articles, fetch content, and ask questions — all stateless.
Let's collaborate
Agent-to-Agent protocol enables stateful, multi-turn conversations between AI agents and your help center — with task tracking and streaming.
# Discover what your help center knows
$curl https://demo.helpnest.cloud/helpnest/help/llms.txt
# HelpNest Help Center
> Support docs, guides, and answers for HelpNest.
This help center contains 17 articles across 6 collections.
## Collections
- [Getting Started](.../getting-started)
- What is HelpNest?
- Quick Start (Local Development)
- Environment Variables
- [Self-Hosting](.../self-hosting)
- [Using HelpNest](.../using-helpnest)
- [Integrations](.../integrations)
- [About](.../about)
- [Migration](.../migration)
## Full Content
For complete knowledge base content, see:
[llms-full.txt](/helpnest/help/llms-full.txt)
llms.txt
A plain-text file at /llms.txt that any model can fetch and parse. No authentication, no SDK, no integration work.
/llms.txtA concise overview of your help center — collections, article counts, available API endpoints, and protocol support. Designed for quick context injection.
/llms-full.txtThe full content of every published article, concatenated into a single file. Ideal for RAG pipelines or bulk ingestion into a vector store.
Model Context Protocol
Add HelpNest as an MCP server and AI assistants can search, read, and query your knowledge base using structured tools.
{
"mcpServers": {
"helpnest": {
"command": "npx",
"args": [
"@helpnest/mcp",
"--url", "https://help.acme.com",
"--api-key", "hn_xxx"
]
}
}
}
Available tools
search_articlesFull-text search across your knowledge base
get_articleFetch a single article by ID or slug
list_collectionsBrowse the collection hierarchy
ask_questionAI-powered Q&A over your content
Agent-to-Agent
The A2A protocol lets external agents discover capabilities, send messages, and track tasks — with optional SSE streaming for real-time responses.
# Discover the agent's capabilities
$curl https://help.acme.com/.well-known/agent-card.json
{
"name": "Acme Help Center",
"url": "https://help.acme.com",
"capabilities": {
"streaming": true,
},
"skills": [
"search", "ask", "get_article"
]
}
# Send a question via JSON-RPC
$curl -X POST /api/a2a \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "message/send",
"params": { "message": {
"role": "user",
"parts": [{ "text": "How do I reset my password?" }]
}}
}'}
message/sendSend a message and get a complete response
message/send-streamingSSE stream for real-time responses
tasks/get & tasks/cancelTrack and manage long-running tasks
Agent-optimized API
Standard REST API with Markdown output, bulk export, and incremental sync — everything an agent needs to stay current.
GET/api/articles?format=markdown
Returns articles in clean Markdown — ideal for LLM context
GET/api/articles/export
Bulk export all articles as a structured JSON payload
GET/api/articles/changes?since=ISO
Incremental sync — only articles modified since a timestamp
Every HelpNest instance ships with llms.txt, MCP, and A2A support out of the box. No configuration needed — just deploy and your knowledge base is accessible to any AI agent.