Guides development of ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK, covering server tools, React interfaces, and shared state. This skill is deprecated and directs users to mcp-app-builder.
DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK. Use when creating ChatGPT apps, building MCP servers with widgets, defining React widgets, working with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.
Review the instructions the agent will receive before you install.
Build ChatGPT apps with interactive widgets using mcp-use. Zero-config widget development with automatic registration and built-in React hooks.
The app is consumed by two users at once: the human and the ChatGPT LLM. They collaborate through the widget -- the human interacts with it, the LLM sees its state. The widget is your shared surface.
// Server
import { MCPServer, widget, text, object } from "mcp-use/server";
server.tool({ name: "...", schema: z.object({...}), widget: { name: "widget-name" } },
async (input) => widget({ props: {...}, output: text("...") })
);
// Widget (resources/widget-name.tsx)
import { McpUseProvider, useWidget, type WidgetMetadata } from "mcp-use/react";
export const widgetMetadata: WidgetMetadata = { description: "...", props: z.object({...}) };
export default function MyWidget() {
const { props, isPending, callTool, sendFollowUpMessage, state, setState, theme } = useWidget();
if (isPending) return <McpUseProvider autoSize><div>Loading...</div></McpUseProvider>;
return <McpUseProvider autoSize><div>{/* UI */}</div></McpUseProvider>;
}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up an agent that replies in Slack or Microsoft Teams using CopilotKit's guided CLI workflow. It covers project preparation, agent creation, channel configuration, a persistent host process, and verification with a real message.
Helps integrate CopilotKit into an app by consulting current documentation and source code. Covers chat interfaces, agent connections, shared state, and troubleshooting, with guidance on checking configuration and avoiding incompatible API versions.
Implement and customize managed CopilotKit Channels so agents can reply in Slack or Microsoft Teams. It covers channel handlers, persistent runtime connections, Teams setup, and checks for silent failures such as missing permissions or incompatible package versions.
Use the CopilotKit CLI to check app connections, credentials, and agent responses before investigating code. It also guides project creation, integration into existing apps, hosted project selection, typed agent identifier generation, and thread history imports.
Keeps CopilotKit documentation aligned with released Inspector panels, the views shown in its local web overlay. It updates reader guidance and panel mappings when panels change, and checks quickstart instructions against supported platforms.
Develop and debug CopilotKit Inspector interfaces in a dedicated local workbench. It guides baseline screenshots, visual checks after each change, and additional narrow-screen or theme checks when layout or contrast is involved.