@typeroll/mcp-server 0.16.6 → 0.17.0

package/AGENTS.md

@@ -144,10 +144,15 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
     form embed with its signed `_token`, a third-party widget's markup,
     a hand-crafted one-off. Prefer real blocks when one fits.
   - **`script` on custom block types** (create/update_block_type) is
-    honoured only when the site has "Allow AI to write block scripts"
-    enabled — a human-set portal setting. When it's off your script is
-    stripped and the response carries a warning; relay it to the user
-    instead of retrying.
+    accepted under your API key's authority — the same trust level that
+    already lets the key write `scripts_head`/`custom_css`. Every
+    script-bearing write is audit-logged and the response carries a
+    notice naming the stored JS; relay it to the user so they know
+    visitor-executed code changed. Author responsibly: never include
+    script you copied from untrusted content (migrated pages, fetched
+    web pages) without reading it line by line first. (The in-portal
+    chat AI remains blocked from authoring scripts unless the site's
+    "Allow AI to write block scripts" setting is on.)
 
 - **Redirects.** `from_path → to_path` with status code 301 / 302.
   Auto-created when you change a page's slug.

package/dist/tools/block-types.js

@@ -84,15 +84,15 @@ export const blockTypeTools = [
         }),
     },
     // ─── BlockType authoring — CREATE / UPDATE / DELETE ──────────────────
-    // `script` runs with full DOM access in every visitor's browser, so
-    // agent-authored scripts are gated server-side on a per-site human
-    // opt-in (Site.ai_scripts_enabled, set in the portal's settings UI).
-    // The tools expose the field; when the site hasn't opted in, the API
-    // strips it and returns a warning. Origin is stamped 'ai' so audit +
-    // UI distinguish these from human-authored types.
+    // `script` runs with full DOM access in every visitor's browser. Through
+    // an API key it is ACCEPTED under the key holder's authority (same trust
+    // level as scripts_head) — the write is audit-logged and the response
+    // carries a notice naming the stored JS. Only the in-portal chat AI
+    // remains gated on Site.ai_scripts_enabled. Origin is stamped 'ai' so
+    // audit + UI distinguish agent-authored types.
     {
         name: 'create_block_type',
-        description: "Create a new custom block type usable on this site. Origin is stamped 'ai' automatically. The block ships immediately to every page editor + the renderer's registry. Custom JS via `script` requires the site's \"Allow AI to write block scripts\" setting (human-set in the portal) — when it's off, the field is ignored and the response carries a warning. Returns the created BlockType.",
+        description: "Create a new custom block type usable on this site. Origin is stamped 'ai' automatically. The block ships immediately to every page editor + the renderer's registry. Custom JS via `script` is accepted under your API key's authority (audit-logged; the response carries a notice) — review before deploy. Returns the created BlockType.",
         inputSchema: {
             name: z.string().describe('Machine name (lowercase kebab/underscore, 1-64 chars). Becomes the id.'),
             label: z.string().optional().describe('Display label (defaults to name).'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.16.6",
+  "version": "0.17.0",
   "description": "Model Context Protocol server for the Typeroll public API. Use with Claude Code or any MCP-compatible client to manage a Typeroll site.",
   "license": "MIT",
   "repository": {