Connecting every app to every other app
Tired of playing OAuth whack-a-mole? This post dissects the 'n² problem' of app integration and hails Dynamic Client Registration (DCR) and Client ID Metadata Documents (CIMD) as the unsung heroes. It's popular because it tackles a pervasive developer pain point with a visionary look at a seamlessly interconnected future, sans manual config.
The Lowdown
Steve Krouse of Val Town dives headfirst into the 'n² problem' of application integration, where connecting every app to every other app traditionally means a painful, manual OAuth client registration dance. He argues that this tedious process is ripe for disruption, and the solution is already emerging from the trenches of AI-driven protocols.
- The core issue: Every app needs to register as an OAuth client for every other app, an often ad-hoc, manual, and time-consuming headache involving forms, demos, and even video calls.
- Enter Dynamic Client Registration (DCR): This OAuth extension automates the client registration process, allowing an app to dynamically provision an OAuth client and initiate a flow with an app it's never encountered before.
- Its adoption was spurred by Anthropic and OpenAI, who needed seamless connections for their Model Context Protocol (MCP) servers, integrating AI with user applications without manual setup.
- Further refining the process is Client ID Metadata Documents (CIMD), which allows applications to self-host their OAuth client data at a well-known URL, enabling immediate OAuth flows without any prior registration.
- The author demonstrates a live app showcasing 3,613 connectors, emphasizing that deploying a copy (e.g., via Val Town's 'remix' feature) makes all connections instantly functional, no OAuth client setup required.
- However, challenges persist: some "dynamic" registrations aren't truly dynamic (requiring pre-registration in platform catalogs), and DCR/CIMD often apply to MCP endpoints rather than traditional REST APIs.
- The article differentiates between the stable contracts of REST APIs and the flexible, inference-driven nature of MCPs, suggesting a social convention could allow DCR/CIMD tokens to work across both.
- Looking ahead, the author advocates for a public registry of connectors and open-source tooling to standardize and simplify integration.
- Coupled with payment solutions like x402 (for pay-per-use APIs), DCR/CIMD paves the way for a future of "no clicks, no keys" — a significant leap for malleable software and the burgeoning "vibe coding" paradigm.
This convergence of protocols offers a tantalizing glimpse into a world where apps effortlessly discover and connect to each other, largely eradicating the friction that currently plagues API integrations and opening new avenues for dynamic, on-the-fly interoperability.