The WebMCP Hub Thesis: Configs Are the Product
WebMCP Hub converts fragile per-run UI knowledge into persistent, composable, community-validated operational knowledge. The config publisher who converts void to state at the session boundary owns the domain.
The WebMCP Hub Thesis
Configs are not metadata. Configs are the product.
The Core Insight
WebMCP Hub is a shared interaction intelligence layer for the web. It converts fragile, per-run UI trial-and-error into persistent, composable, community-validated operational knowledge.
Without the Hub, every AI agent re-learns selectors every run. Knowledge dies when the session ends. One agent's work benefits only itself. With the Hub, selector knowledge persists across agents. One discovery benefits all agents. Pre-resolved mappings compose without internal knowledge.
The Primitive Decomposition
The Hub's value is a void-to-state conversion at the session boundary:
| Layer | Without Hub | With Hub |
|---|---|---|
| DOM discovery | Agent wastes tokens re-learning | Selector knowledge persists |
| Session boundary | Knowledge dies at session end | Config survives the boundary |
| Community scale | Work benefits one agent | Work benefits all agents |
| Tool composition | Agents must understand internals | Pre-resolved mappings compose |
The fundamental operation: convert Void (per-run ephemeral knowledge) into State (persistent config) at the Boundary (between agent sessions).
The Moat
Configs are the chokepoint because they are the only mechanism that converts ephemeral DOM knowledge into durable operational state. The publisher who creates the config owns the void-to-state boundary for that domain.
The config is not the product — the void-to-state conversion is the product. Anyone can write a CSS selector. The value is in publishing it to the Hub where it becomes shared operational state. First publisher owns the boundary.
The Rail Network
| Element | Analog |
|---|---|
| Sites and pages | Terrain — the raw web surface |
| Hub configs | Stations — persistent operational knowledge |
| Tools | Standardized routes and signals |
| Agents | Trains — run on existing track instead of surveying |
The entity that lays the most track becomes the default route. NexVigilant's position: sole pharmacovigilance domain publisher, 25 configs, 193 tools.