apify
diff --git a/‎DEVELOPMENT.md‎
Lines changed: 4 additions & 4 deletions b/‎DEVELOPMENT.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎README.md‎
Lines changed: 5 additions & 5 deletions b/‎README.md‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎package-lock.json‎
Lines changed: 187 additions & 6 deletions b/‎package-lock.json‎
Lines changed: 187 additions & 6 deletions
diff --git a/‎package.json‎
Lines changed: 1 addition & 0 deletions b/‎package.json‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎res/TODO-mcp-apps-migration.md‎
Lines changed: 57 additions & 0 deletions b/‎res/TODO-mcp-apps-migration.md‎
Lines changed: 57 additions & 0 deletions
@@ -66,7 +66,7 @@ This command builds the core project and the `src/web/` widgets, then copies the
 
 All widget code lives in the self-contained `src/web/` React project. The widgets (MCP Apps) are rendered based on the structured output returned by MCP tools. If you need to add specific data to a widget, modify the corresponding MCP tool's output, since widgets can only render data returned by the MCP tool call result.
 
-> **Important (UI mode):** Widget rendering is enabled only when the server runs in UI mode. Use the `ui=openai` query parameter (e.g., `/?ui=openai`) or set `UI_MODE=openai`. Currently, `openai` is the only supported `ui` value.
+> **Important (UI mode):** Widget rendering is enabled only when the server runs in UI mode. Use the `ui=true` query parameter (e.g., `/mcp?ui=true`) or set `UI_MODE=true`.
 
 ### Hot-reload development
 
@@ -150,7 +150,7 @@ You can use [MCPJam](https://www.mcpjam.com/) to connect to and test the MCP ser
 
 1. Click **"Add new server"**
 2. Fill in a name for the server
-3. Enter the URL: `http://localhost:3001/?ui=openai` (Note: the `ui=openai` query parameter is required for widget rendering)
+3. Enter the URL: `http://localhost:3001/mcp?ui=true` (Note: the `ui=openai` query parameter is required for widget rendering)
 4. Select **"No authentication"** as the auth method
 5. Click **Add**
 
@@ -196,13 +196,13 @@ Then start the tunnel:
 ngrok start app
 ```
 
-The MCP server API will be reachable at `https://mcp-apify.ngrok.dev/?ui=openai`.
+The MCP server API will be reachable at `https://mcp-apify.ngrok.dev/mcp?ui=true`.
 
 #### Adding the server in ChatGPT
 
 1. Go to [chatgpt.com](https://chatgpt.com) and open **Settings → Connectors**
 2. Click **"Add a custom connector"**
-3. Enter the URL: `https://mcp-apify.ngrok.dev/?ui=openai`
+3. Enter the URL: `https://mcp-apify.ngrok.dev/mcp?ui=true`
 4. Save and start a new chat
 
 > **Important:** After restarting ngrok, use the **Refresh** button in the connector settings to reconnect — ChatGPT does not detect the tunnel restart automatically.
@@ -294,34 +294,34 @@ As above, this exposes only the specified Actor (`apify/my-actor`) as a tool. No
 
 ### UI mode configuration
 
-The `uiMode` parameter enables OpenAI-specific widget rendering in tool responses. When enabled, tools like `search-actors` return interactive widget responses optimized for OpenAI clients.
+The `ui` parameter enables [MCP Apps](https://mcp.apify.com/) widget rendering in tool responses. When enabled, tools like `search-actors` return interactive MCP App responses.
 
 **Configuring the hosted server:**
 
 Enable UI mode using the `ui` query parameter:
 
 ```
-https://mcp.apify.com?ui=openai
+https://mcp.apify.com?ui=true
 ```
 
 You can combine it with other parameters:
 
 ```
-https://mcp.apify.com?tools=actors,docs&ui=openai
+https://mcp.apify.com?tools=actors,docs&ui=true
 ```
 
 **Configuring the CLI:**
 
 The CLI can be configured using command-line flags. For example, to enable UI mode:
 
 ```bash
-npx @apify/actors-mcp-server --ui openai
+npx @apify/actors-mcp-server --ui true
 ```
 
 You can also set it via the `UI_MODE` environment variable:
 
 ```bash
-export UI_MODE=openai
+export UI_MODE=true
 npx @apify/actors-mcp-server
 ```
 
 
@@ -43,6 +43,7 @@
     "@apify/datastructures": "^2.0.3",
     "@apify/log": "^2.5.16",
     "@apify/utilities": "^2.25.1",
+    "@modelcontextprotocol/ext-apps": "^1.1.2",
     "@modelcontextprotocol/sdk": "^1.25.2",
     "@segment/analytics-node": "^2.3.0",
     "@sentry/node": "^10.38.0",
 
@@ -0,0 +1,57 @@
+# TODO: MCP Apps Full Migration
+
+Remaining work to achieve full MCP Apps (`@modelcontextprotocol/ext-apps`) compliance.
+Tracks items not covered by the initial metadata migration PR.
+
+## Server-side
+
+### Capability negotiation (high priority)
+- [x] Check `io.modelcontextprotocol/ui` extension in client capabilities during `initialize`
+- [x] Use `getUiCapability()` equivalent inline (`getUiCapability()` from `@modelcontextprotocol/ext-apps/server` can't be imported without `moduleResolution: 'node16'` — implemented as 3-line inline check)
+- [ ] Conditionally register UI tools/resources only when client supports `text/html;profile=mcp-app` (capability flag is informational for now; future PR)
+- [ ] Provide text-only fallback tools when client doesn't support MCP Apps (future PR)
+
+> **Note**: `registerAppTool()`/`registerAppResource()` from `@modelcontextprotocol/ext-apps/server` require `McpServer` (high-level SDK class), but our server uses the low-level `Server` class. Adoption requires a separate `McpServer` migration effort.
+
+### Mode decoupling
+- [ ] Decouple `ui` metadata from `mode: 'openai'` — the `_meta.ui.*` keys are the MCP standard and should be available in all modes, not just `openai`
+- [ ] Only gate `openai/*` legacy keys behind `mode: 'openai'`
+- [ ] Widget resources should be served when widgets are available, regardless of mode
+
+### CSP dual format
+- [ ] Remove snake_case CSP fields (`connect_domains`, `resource_domains`) from `WIDGET_CSP` in `src/resources/widgets.ts` once MCP Jam and all hosts support camelCase (`connectDomains`, `resourceDomains`). Currently shipping both for compatibility.
+
+### Cleanup / renames
+- [x] Rename `stripOpenAiMeta` → `stripWidgetMeta` in `src/utils/tools.ts`
+- [x] Rename `filterOpenAiMeta` → `filterWidgetMeta` in `ToolPublicFieldOptions` and `src/mcp/server.ts`
+- [x] Update `stripOpenAiMeta` comment references in 6 tool files
+- [ ] Remove `openai/resultCanProduceWidget` (no MCP equivalent) once ChatGPT no longer needs it
+- [ ] Remove `openai/widgetAccessible` once ChatGPT fully supports `ui.visibility`
+
+## Client-side (`src/web/`)
+
+### Replace `window.openai` with MCP Apps SDK `App` instance
+- [x] Install `@modelcontextprotocol/ext-apps` in the web package
+- [x] `window.openai.theme` → `app.getHostContext()?.theme` (`src/web/src/utils/init-widget.tsx`, `src/web/src/hooks/use-open-ai-global.ts`)
+- [x] `window.openai.toolOutput = ...` → `app.ontoolresult` callback (`src/web/src/widgets/actor-run-widget.tsx:225`)
+- [x] `window.openai.callTool(...)` → `app.callServerTool(...)` (`src/web/src/pages/ActorRun/ActorRun.tsx:367`)
+- [x] `window.openai.openExternal({href})` → `app.openLink({url})` (`src/web/src/pages/ActorRun/ActorRun.tsx:464,472`)
+- [x] `window.openai.widgetState` / `setWidgetState` → plain React state (`src/web/src/hooks/use-widget-state.ts`) — no MCP equivalent yet
+- [x] Replace `src/web/src/hooks/use-open-ai-global.ts` hook with MCP Apps context
+- [x] Update `src/web/src/utils/mock-openai.ts` dev mock for new `App` API
+- [x] Remove/update `window.openai` type declarations
+
+### Theming
+- [ ] Adopt MCP Apps CSS variables (`--color-background-primary`, `--color-text-primary`, etc.) from host context
+- [ ] Use `applyHostStyleVariables` / `applyDocumentTheme` utilities from ext-apps SDK
+
+## Blocked upstream (not yet available in MCP Apps SDK)
+
+| Feature | OpenAI API | Status |
+|---------|-----------|--------|
+| Tool invocation progress | `openai/toolInvocation/invoking` / `invoked` | Not yet implemented |
+| Widget description | `openai/widgetDescription` | Use `app.updateModelContext()` |
+| Widget state persistence | `widgetState` / `setWidgetState` | Use `localStorage` or server-side |
+| File operations | `uploadFile` / `getFileDownloadUrl` | Not yet implemented |
+| Modal management | `requestModal` / `requestClose` | Not yet implemented |
+| Open in app URL | `setOpenInAppUrl` | Not yet implemented |