Next steps for apps in goose

[DOsinga]

Goose has consistently been at the forefront of supporting MCP standards, and the recent developments around MCP-UI and MCP-Apps are no exception. This plan describes how these evolving standards can be expanded into a full-blown vibe-coding environment, enabling anyone to build UIs and applications directly within Goose.

Step 1: MCP-UI

We launched this a few months ago. MCP-UI allows MCP servers to return rich elements so a weather extension can show the weather as a nice little widget. MCP-UI renders these interfaces as html inside an iframe.

Step 2: MCP-Apps

MCP-Apps were announced on the MCP website in a blog post on November 21st, proposing a standardized extension for interactive user interfaces, and Goose quickly became one of the first agents to support and ship the feature. An example would be a stock tracking widget that automatically updates.

Step 3: Standalone MCP-Apps

Currently MCP-Apps live inside chats. But for many interactions, having them run as standalone apps also makes sense. You might want to run the stock tracking widget as a standalone app. Or have an AI app that helps you learn a language.

First implementation

Step 4: goose as an MCP Apps provider

Goose has built-in MCP servers called platform extensions. We will create one that can manage its own apps. An app is, after all, just a bit of HTML with an API to call tools. The Apps platform extension would allow Goose, and by extension the user, to create and manage their own apps.

Step 5: allow platform apps to extent goose itself

The final step is to allow platform apps to extend Goose’s own capabilities. Instead of being passive tools, apps can become first-class extensions that add new workflows, UI surfaces, and behaviors to Goose. This enables users to shape Goose to their needs by composing and building apps that feel native rather than bolted on.