@exposify/supabase 0.3.14 → 0.3.15

package/README.md

@@ -1,4 +1,4 @@
-# @exposify/supabase — setup guide
+# @exposify/supabase
 
 Make a Supabase-backed app's database and edge functions usable by AI agents:
 one edge function serves MCP, with tools generated from your database
@@ -7,9 +7,42 @@ register. The caller's JWT passes straight through to PostgREST — **RLS is
 the authorization layer**. The agent can do exactly what that logged-in user
 can do, nothing more.
 
-This guide walks through setup end to end. For the design rationale, see
-`docs/superpowers/specs/2026-08-15-agentify-supabase-design.md` in the repo
-root.
+> **Which package?** Use **`@exposify/supabase`** when you want an MCP
+> endpoint served straight from a Supabase **edge function** over PostgREST,
+> with RLS as the authorization layer. If you have a **Next.js app** (even one
+> whose users sign in with Supabase Auth), use
+> [**`@exposify/next`**](https://github.com/ayadagain/agentready/tree/main/packages/next)
+> instead, so tool calls run through your Next server and your own middleware
+> and checks apply.
+
+## Quickstart
+
+From your Supabase project's root (the directory containing `supabase/`):
+
+```bash
+npx @exposify/supabase init          # scaffold the migration + mcp function
+supabase db push                      # apply the exposify_meta() migration
+supabase functions deploy mcp         # deploy the MCP edge function
+```
+
+Then point an MCP client at the function's URL with a user's JWT — e.g. with
+the Claude Code CLI:
+
+```bash
+claude mcp add --transport http my-app \
+  https://<project-ref>.supabase.co/functions/v1/mcp \
+  --header "Authorization: Bearer <user-jwt>"
+```
+
+Every RLS-enabled table you can `SELECT` becomes a `query_<table>` tool
+automatically; writes and RPCs are opt-in. `init` is interactive and can run
+`db push`/`functions deploy` for you, wire in the hosted broker or Supabase
+Auth OAuth (so clients sign in by themselves instead of pasting an hourly
+JWT), and write tool descriptions from your SQL comments — see the sections
+below. Check the whole setup any time with `npx @exposify/supabase doctor`.
+
+The rest of this guide is reference, end to end. For the design rationale, see
+the [design spec](https://github.com/ayadagain/agentready/blob/main/docs/superpowers/specs/2026-08-15-agentify-supabase-design.md).
 
 ## Prerequisites
 
@@ -199,7 +232,7 @@ things:
 Until the project has a sign-in method (the Supabase preset in the
 dashboard), agents use the function signed out, as `anon`, with no sign-in
 asked: there's nothing to sign in with. The log says which it is
-(`[agentready] How agents sign in: ...`), and adding the method takes effect
+(`[exposify] How agents sign in: ...`), and adding the method takes effect
 within a minute.
 
 MCP clients then click Connect and sign in through the broker (or send a
@@ -490,7 +523,7 @@ Supabase user JWTs expire (default 1h) and their refresh tokens rotate; a plain
 MCP client can hold a bearer token but can't refresh it. Exposify's hosted
 broker holds each user's session, refreshes it, and swaps the agent's
 long-lived connection token (`extb_...`) for a live Supabase JWT on every
-call ([`docs/hosted-broker.md`](../../docs/hosted-broker.md)). `init` sets it
+call (see the [hosted broker guide](https://github.com/ayadagain/agentready/blob/main/docs/hosted-broker.md)). `init` sets it
 up (see "Using the hosted broker" above); by hand:
 
 ```sh
@@ -589,7 +622,7 @@ the function prints whether MCP is up. It shows in `supabase functions serve`
 locally and in the function's logs in production:
 
 ```
-[@exposify/supabase] MCP ready at https://<ref>.supabase.co/functions/v1/mcp: 9 tools (5 query, 2 write, 1 rpc, search_docs), 3 docs indexed, auth: passthrough (caller's JWT)
+[exposify] MCP ready at https://<ref>.supabase.co/functions/v1/mcp: 9 tools (5 query, 2 write, 1 rpc, search_docs), 3 docs indexed, auth: passthrough (caller's JWT)
 ```
 
 - **Manifest fallback:** the same line, marked "from the bundled manifest",

package/dist/cli.js

@@ -579,7 +579,7 @@ function warnOnce(message) {
   if (warned.has(message)) return;
   warned.add(message);
   try {
-    console.warn(`[@exposify/supabase] ${message}`);
+    console.warn(`[exposify] ${message}`);
   } catch {
   }
 }

package/dist/index.cjs

@@ -107,7 +107,7 @@ function warnOnce(message) {
   if (warned.has(message)) return;
   warned.add(message);
   try {
-    console.warn(`[@exposify/supabase] ${message}`);
+    console.warn(`[exposify] ${message}`);
   } catch {
   }
 }
@@ -755,7 +755,7 @@ function createSupabaseOAuthGate(oauth, supabaseUrl, fetchImpl) {
 
 // src/startup.ts
 var import_core4 = require("@exposify/core");
-var LOG_PREFIX = "[@exposify/supabase]";
+var LOG_PREFIX = "[exposify]";
 var INTROSPECTION_FIX = "check that SUPABASE_SERVICE_ROLE_KEY is available to the function and the exposify_meta migration is applied (`supabase db push`); the reason is logged above. To survive this, bundle a manifest with `npx @exposify/supabase generate`";
 function supabaseToolsPhrase(ladder, cfg, hasDocs) {
   const query = ladder.tables.length;
@@ -874,7 +874,7 @@ function aiReady(options = {}) {
       manifest: options.manifest
     }).then((ladder) => {
       for (const w of ladder.warnings) {
-        console.error(`[@exposify/supabase] degradation ladder: ${w.rung}: ${w.reason}`);
+        console.error(`[exposify] degradation ladder: ${w.rung}: ${w.reason}`);
       }
       return ladder;
     });

package/dist/index.js

@@ -70,7 +70,7 @@ function warnOnce(message) {
   if (warned.has(message)) return;
   warned.add(message);
   try {
-    console.warn(`[@exposify/supabase] ${message}`);
+    console.warn(`[exposify] ${message}`);
   } catch {
   }
 }
@@ -722,7 +722,7 @@ function createSupabaseOAuthGate(oauth, supabaseUrl, fetchImpl) {
 
 // src/startup.ts
 import { formatFailed, formatReady, formatWarning } from "@exposify/core";
-var LOG_PREFIX = "[@exposify/supabase]";
+var LOG_PREFIX = "[exposify]";
 var INTROSPECTION_FIX = "check that SUPABASE_SERVICE_ROLE_KEY is available to the function and the exposify_meta migration is applied (`supabase db push`); the reason is logged above. To survive this, bundle a manifest with `npx @exposify/supabase generate`";
 function supabaseToolsPhrase(ladder, cfg, hasDocs) {
   const query = ladder.tables.length;
@@ -841,7 +841,7 @@ function aiReady(options = {}) {
       manifest: options.manifest
     }).then((ladder) => {
       for (const w of ladder.warnings) {
-        console.error(`[@exposify/supabase] degradation ladder: ${w.rung}: ${w.reason}`);
+        console.error(`[exposify] degradation ladder: ${w.rung}: ${w.reason}`);
       }
       return ladder;
     });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exposify/supabase",
-  "version": "0.3.14",
+  "version": "0.3.15",
   "license": "MIT",
   "type": "module",
   "main": "./dist/index.cjs",
@@ -27,7 +27,7 @@
     "prepack": "yarn build"
   },
   "dependencies": {
-    "@exposify/core": "0.3.18",
+    "@exposify/core": "0.3.19",
     "@modelcontextprotocol/sdk": "^1.12.0",
     "zod": "^3.24.0"
   },