2026-10-29 · ← News
Everyone wants other products to become headless MCP servers while their own UI remains special
Ben Hylak captured the product blindness around MCP in one joke: everyone else's software should disappear behind an agent while your own interface remains beloved. The real shift is not the death of UI but customers gaining control over where they enter a product.
The image could not be loaded.
On 29 October Simon Willison published a quote from Ben Hylak: every product he uses should be a headless MCP feeding into an agent, so he never has to think about what sits underneath. His own product is naturally exempt because its customers love the UI. Four lines capture an uncomfortable contradiction in current product strategy.
One joke exposes the double standard applied to product interfaces
MCP gives agents a standard way to discover tools and work with data from different services. Users can complete a task through one agent instead of clicking through several applications. For every vendor, that also means its carefully designed interface may stop being the main entrance.
Hylak's point rests on the asymmetry. Product teams want frictionless access to other companies' services while treating their own UI as a customer relationship immune to the same change. The standard looks attractive while it is dissolving somebody else's surface.
Value moves from the screen into data, permissions and rules
A headless approach does not eliminate interfaces. It means the vendor's interface is no longer the only place where the product can be used. A customer may arrive through Claude, ChatGPT, an internal agent or a custom workflow. The service then competes on data quality, reliable actions, permissions and auditability.
MCP Apps have supported interactive components inside hosts since January 2026, including forms, dashboards, visualisations and multi-step workflows. The choice is therefore not UI versus no UI. It is about who hosts the interface, who owns the context and where the user makes decisions.
An agent without good UI can hide errors and consequential choices
Moving everything into conversation is not automatic progress. Selecting among dozens of records, comparing data, approving changes or tracking live state often needs visual structure. A text agent can accelerate the steps, but it can also hide parameters, price or permission scope behind a fluent sentence.
The headless layer does not solve the business incentive either. A vendor must operate APIs, authentication and safe actions while the host agent may gain the customer relationship and upsell surface. That is technically elegant and commercially uncomfortable.
Adoption will show whether customers bypass the home screen
The useful metric is the share of tasks completed through agents, not the number of MCP servers announced. It matters whether users merely read data through this channel or also approve payments, change settings and complete the product's core workflow.
Permission design and portability are the second signal. If a customer can safely use the same service through multiple agents while retaining an audit trail, the home screen loses its monopoly. UI survives, but it no longer owns the customer by default.
Lilith's verdict
Every product team imagines other software as plumbing for its agent and its own app as a beloved café. The customer may only want the coffee, not the loyalty card or the tour of the furniture.