Discovery · DNS
agentproto's Setup Wizard Now Discovers MCP Apps Before You Ask
A small but telling change landed in agentproto's October 1 TypeScript runtime release: the CLI's interactive setup wizard now folds MCP panel app discovery directly into first-run onboarding. Previously, finding and installing available MCP panel apps meant a separate invocation after setup. Now the wizard surfaces what's available and installs it as part of the same flow.
That's a small UX fix, but it points at a real friction point in the MCP ecosystem: discovery has been bolted on after the fact in most runtimes, treated as a power-user feature rather than a default. Folding it into onboarding is an implicit admission that most users won't go looking for a discovery command on their own — if an agent runtime wants apps to actually get used, discovery has to happen automatically, at setup time, not as an opt-in step.
The same release also carries OpenAI's MCP-extensions metadata through the app install pipeline — the AgnoMcpApp type now carries an optional OpenAIAppDescriptor field tied to section 3.2 of the OpenAI MCP Extensions spec. That's a narrower change, but it matters for the same reason: it means an app installed through agentproto can carry enough descriptor metadata to render correctly in contexts that expect OpenAI's extension format, rather than requiring a separate adapter layer per host.
Neither change is a new protocol or a new registry. It's plumbing — the unglamorous work of making discovery the default path rather than a side door, and making metadata survive the trip between install pipelines that weren't originally built to agree with each other. That's also where most of the actual friction in agent tooling lives right now: not in whether a discovery mechanism exists, but in whether it's the first thing a new user hits, and whether descriptors from one spec survive being installed through another runtime's pipeline.
It's worth being clear about scope: this is one runtime's release notes, not an industry-wide standard shift. But it's a concrete data point in a pattern worth tracking — MCP tooling is slowly moving app and tool discovery out of the 'documented but skippable' category and into the default install path, which is usually where interoperability either gets real or stays theoretical.