Hylak distinguishes his own UI from headless MCP agent feeds

Ben Hylak argues that the majority of software products should function as headless Model Context Protocol feeds for AI agents. He simultaneously claims his own product is an exception, noting that customers actively prefer its user interface.

The evidence

The position comes from a quotation collected by Simon Willison on his AI news site. Willison posted the statement on 29 October 2026, tagging it with model-context-protocol and ai.reported The text presents Hylak’s view that users should never need to consider underlying systems when interacting with agents. Hylak contrasts this general principle with his specific business, stating customers love their UI and the company itself. He describes this attachment as a special characteristic of their product.

The decision

Hylak distinguishes between tools he consumes and the tool he builds. For external products, he advocates for a headless architecture where the MCP feeds data directly into an agent. This removes the need for user interaction with the underlying infrastructure. For his own venture, he maintains a traditional user interface. He suggests that customer affection for the visual layer justifies deviating from his own headless preference. This creates a dual standard for product design based on ownership.

What to make of it

The statement highlights a tension between agent-centric workflows and traditional software interfaces. Hylak proposes that most applications should disappear behind an agent layer. However, he retains a graphical interface for his own company. This implies that user experience may still hold value in specific contexts. It suggests that not all products will transition to headless models immediately. The distinction relies on claimed customer preference rather than technical necessity.

In practice

Startup founders face a choice between building headless MCP feeds or maintaining user interfaces. Hylak’s view suggests most products should adopt the former approach. Users would interact only with agents, not the underlying tools. However, Hylak’s own product keeps its UI because customers reportedly love it. This indicates that some markets may still demand visual interaction. Founders must decide if their users prefer direct agent access or a dedicated interface. Availability of headless options depends on vendor adoption of the Model Context Protocol. Limitations include the need for users to trust agents with underlying processes. Access to Hylak’s specific product remains through its existing UI, not a headless feed.