MCP Hello Page is popular: cleverly solving the readability problem of AI protocols

Core conclusion

MCP (Model Context Protocol) developer Dachande663 has open sourced an ingenious design: when the AI client makes a normal request to the MCP server, a standard JSON-RPC response is returned; but when a human opens the same endpoint with a browser, it is automatically rendered into a readable HTML page. This "Hello Page" concept received a hot 86 on Hacker News, sparking widespread discussion about API content negotiation and MCP protocol design flaws.

Key Points

• Time: 2026-05-17, HN discussion continues to heat up, 31 comments
• Core idea: Distinguish between AI clients and human browsers through the HTTP Accept header and return different content types
• MCP Ecological Enlightenment: This design exposes the shortcomings of the MCP protocol in terms of developer experience and documentation
• Reproducible Solution: Any MCP server developer can implement it in about 10 lines of code

Background: Problems with the MCP protocol and the birth of Hello Page

MCP (Model Context Protocol) is an open protocol launched by Anthropic, designed to allow AI models to standardize interaction with external tools and data. But in actual use, developers often face an embarrassing problem: the MCP server endpoint can only be understood by the AI ​​client, and humans only see the cold JSON-RPC request/response format when opening it with a browser.

Developer Dachande663 from the UK decided to solve this problem. His solution is surprisingly simple: Check the Accept header of the HTTP request.

• If Accept: application/json or text/event-stream, return standard MCP JSON-RPC response
• If Accept: text/html (browser default), returns a human-readable HTML page

I did a little trick: if the target of the request is /mcp and the Accept contains text/html but not application/json or text/event-stream, I return an HTML page.

This content negotiation (Content Negotiation) technology is not a new invention - the Kubernetes API uses the same method to switch between different output formats, and ipinfo.io also returns HTML or JSON depending on the request source. But applying it to MCP servers, this idea still makes the community shine.

Key Impact

Hot discussion in the community: Is the MCP protocol feasible?

The HN comments section presents an interesting divide. Supporters believe this small detail demonstrates good engineering taste:

This tiny convenience should be more common. I think this would also be useful when a really confused user throws the link directly to the AI ​​Agent - the agent will pass the information on to the user. — zrail

However, some developers also used the topic to criticize the MCP protocol itself:

Anyone involved in the release of MCP should be ashamed. I read the MCP specification and what I saw was a bunch of nonsense that bounced back and forth between baby-level data formats and pie-in-the-sky marketing language. Several navigation links are still broken. Thinks very poorly and communicates very poorly. — epistasis

Some community members pointed out that this kind of trick actually has a more standard approach:

This is not a trick at all. This is how the Kubernetes API works. The CLI also requires a different content type when -o yaml or -o json is specified. ipinfo.io does the same thing - browser opens return HTML, curl requests return JSON. — pvtmert

Adaptation suggestions

1. Add Hello Page to each MCP endpoint

Add Accept header check in MCP server development:

from flask import Flask, request, jsonify, render_template_string
app = Flask(__name__)

@app.route('/mcp')
def mcp_endpoint():
    accept = request.headers.get('Accept', '')
    if 'text/html' in accept and 'application/json' not in accept:
        return '<h1>MCP Server</h1><p>Hello, human!</p>'
    return jsonify({"jsonrpc": "2.0", "result": "ok"})

2. When using MCP in tools such as n8n / OpenClaw, first check whether there is a Hello Page

Before integrating a third-party MCP server, open the test endpoint in your browser. If there is a Hello Page, it means that the developer pays attention to maintainability.

3. Pay attention to the evolution of MCP protocol

The MCP Hello Page event shows that MCP needs to do more work on the developer experience. Follow Anthropic’s official plans to improve the protocol.

Tool entry

This article involves the following tools. Brand names that appear naturally in the text will be automatically matched by the system: MCP, Anthropic, Claude, n8n, OpenClaw, OpenAI

Internal link guidance

• Want to build your own MCP server? Watch the tutorial: AI Agent-Driven Content Automation: n8n MCP Building Guide from Scratch
• Someone made money using MCP + n8n: He Built an AI Automation Stack with Claude + n8n — $4K to $12K/mo in 6 Months