Model Context Protocol

Important

You may have been redirected to this page when attempting to access the /mcp path to your HelpGuides.io documentation.

What is Model Context Protocol

Model Context Protocol (MCP) is an emerging open standard that defines how AI systems interact with external tools and knowledge sources in a structured, predictable, and programmatic way.

Rather than relying on scraping web pages or processing unstructured text, MCP allows AI clients to discover available capabilities, query systems using well-defined inputs, and retrieve results in consistent, machine-readable formats.

This enables AI assistants, agents, and retrieval-augmented generation (RAG) workflows to integrate external context reliably, turning documentation and services into first-class components of an enterprise AI stack while reducing fragility, ambiguity, and long-term integration risk.

MCP Support Simplifies Integration for RAG-based scenarios

Content published in HelpGuides.io is automatically structured and chunked at publish time. Long articles are broken into logically related sections based on headings, then tokenized and indexed as discrete units.

This approach allows search to retrieve only the most relevant portions of content for a given query, improving response accuracy.

You can see this when searching for content in the UX as search can show relative sections. For example, there are multiple results returned for the article Setting up Text Message Marketing:

With support for Model Context Protocol (MCP), downstream AI tools, such as Microsoft Copilot when integrated via MCP, benefit from this same structure content approach. And most importantly, no longer need to rely on scraping HTML.

Instead, documentation is exposed through a clean, structured, and pre-chunked interface, ensuring that only the content most relevant to a given query is returned. In practice, MCP enables applications to interact with structured knowledge sources more intelligently, retrieving precise context optimized for retrieval-augmented generation (RAG).

Testing MCP

You can test HelpGuides.io MCP support using the following CURL requests.

Note, in practice, these interactions are handled automatically: an MCP client queries the server, discovers the supported capabilities and endpoints, and then invokes the appropriate endpoint to fulfill a request.

Initial request

For example a CURL to the DailyStory documentation returns sever info and an Mcp-Session-Id, which is required for subsequent requests:

curl -ki -X POST https://docs.dailystory.com/mcp -H "Content-Type: application/json" -d "{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"Example\",\"version\":\"1.0.0\"}}}

This returns the following which includes the Mcp-Session-Id in the header:

HTTP/1.1 200 OK Content-Type: text/event-stream Date: Fri, 16 Jan 2026 17:25:08 GMT Server: Kestrel Cache-Control: no-cache,no-store Content-Encoding: identity Transfer-Encoding: chunked Content-Security-Policy: frame-ancestors 'none' X-Frame-Options: DENY Mcp-Session-Id: MM2ZUNNpVih7r0TGZb38pg event: message data: {"result":{"protocolVersion":"2024-11-05","capabilities":{"logging":{},"tools":{"listChanged":true}},"serverInfo":{"name":"io.helpguides/sever","version":"1.0.0"}},"id":1,"jsonrpc":"2.0"}

Perform a query

Next, using the Mcp-Session-Id obtained above, make a request - such as setting up SMS marketing:

curl -k -X POST https://docs.dailystory.com/mcp -H "Content-Type: application/json" -H "Mcp-Session-Id: [YOUR MCP SESSION ID]" -d "{\"jsonrpc\":\"2.0\",\"id\":3,\"method\":\"tools/call\",\"params\":{\"name\":\"api_search\",\"arguments\":{\"s\":\"setting up SMS marketing\"}}}

We're looking forward to seeing how customers use these powerful new capabilities in their business use cases.