feat(mcp): expose current context page resource (#335)

Author: vamgan

examples/analytics-dashboard-react/package.json

@@ -9,7 +9,7 @@
     "start": "next start"
   },
   "dependencies": {
-    "@askable-ui/react": "^0.13.1",
+    "@askable-ui/react": "^0.14.0",
     "@hookform/resolvers": "^3.9.1",
     "@radix-ui/react-accordion": "1.2.12",
     "@radix-ui/react-alert-dialog": "1.1.15",

examples/react-native-expo/package.json

@@ -11,8 +11,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@askable-ui/core": "^0.13.1",
-    "@askable-ui/react-native": "^0.13.1",
+    "@askable-ui/core": "^0.14.0",
+    "@askable-ui/react-native": "^0.14.0",
     "@react-navigation/native": "^7.2.5",
     "@react-navigation/native-stack": "^7.16.0",
     "expo": "^55.0.26",

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "askable",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "private": true,
   "workspaces": [
     "packages/*"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askable-ui/context",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "description": "Open Context packet types and schema for AI-native interfaces",
   "type": "module",
   "main": "./dist/index.js",

packages/context/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askable-ui/core",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "description": "Framework-agnostic context tracker for LLM-aware UIs",
   "type": "module",
   "main": "./dist/index.js",
@@ -38,7 +38,7 @@
   "homepage": "https://askable-ui.com",
   "license": "MIT",
   "dependencies": {
-    "@askable-ui/context": "^0.13.1"
+    "@askable-ui/context": "^0.14.0"
   },
   "devDependencies": {
     "jsdom": "^29.1.1",

packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askable-ui/create-app",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "description": "Scaffold a React + Vite + CopilotKit + askable-ui starter app",
   "type": "module",
   "bin": {

packages/create-askable-app/package.json

@@ -2,7 +2,7 @@ import fs from 'node:fs';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 
-const ASKABLE_VERSION = '0.12.0';
+const ASKABLE_VERSION = '0.14.0';
 const COPILOTKIT_VERSION = '1.59.2';
 
 const __filename = fileURLToPath(import.meta.url);

packages/create-askable-app/src/scaffold.js

@@ -145,9 +145,9 @@ Hosted Web MCP is the server-side path. For local browser workflows, a page
 cannot expose MCP directly to Claude or ChatGPT by itself. It needs a trusted
 browser extension or local companion process. `createAskableMcpPageBridge()`
 adds the page-side handoff: the page listens for approved bridge requests and
-returns the current packet or prompt-ready text through `window.postMessage()`.
-The extension or companion can then expose that data through its own local MCP
-server.
+returns the current packet, prompt-ready text, or a resource-shaped
+`askable://current` payload through `window.postMessage()`. The extension or
+companion can then expose that data through its own local MCP server.
 
 ```ts
 import { createAskableMcpContextProvider, createAskableMcpPageBridge } from '@askable-ui/mcp';
@@ -181,6 +181,29 @@ window.postMessage({
 ```
 
 Use `type: 'format_context_for_prompt'` when the bridge needs prompt-ready text
-instead of the structured packet. Keep user consent and installation trust in
+instead of the structured packet.
+
+Use `type: 'read_current_resource'` when the extension or companion wants a
+resource-shaped response that can map directly to MCP `resources/read` output:
+
+```ts
+window.postMessage({
+  protocol: 'askable.mcp.page_bridge',
+  version: '0.1',
+  channel: 'askable:mcp',
+  type: 'read_current_resource',
+  requestId: crypto.randomUUID(),
+  options: {
+    sources: ['accounts'],
+    resource: {
+      uri: 'askable://current',
+      format: 'packet',
+    },
+  },
+}, window.location.origin);
+```
+
+Set `resource.format` to `prompt` to receive `text/plain` prompt context at a
+URI such as `askable://current.txt`. Keep user consent and installation trust in
 the extension or companion, and enable the page bridge only when the app wants
 to participate in local browser MCP workflows.

packages/mcp/README.md

@@ -1,6 +1,6 @@
 {
   "name": "@askable-ui/mcp",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "description": "MCP bridge for exposing Context packets to agents",
   "type": "module",
   "main": "./dist/index.js",
@@ -36,8 +36,8 @@
   "homepage": "https://askable-ui.com",
   "license": "MIT",
   "dependencies": {
-    "@askable-ui/context": "^0.13.1",
-    "@askable-ui/core": "^0.13.1",
+    "@askable-ui/context": "^0.14.0",
+    "@askable-ui/core": "^0.14.0",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.4.3"
   },