@typeroll/mcp-server 0.18.0 → 0.19.0

package/dist/tools/forms.js

@@ -46,7 +46,6 @@ export const formTools = [
             fields: z.array(fieldSchema).min(1),
             submit_text: z.string().optional(),
             success_message: z.string().optional(),
-            actions: z.array(z.object({ type: z.string(), config: z.record(z.unknown()) })).optional(),
         },
         handler: withErrorBoundary(async (args, { client, siteId }) => {
             const res = await client.post(siteId, 'forms', args);
@@ -63,7 +62,6 @@ export const formTools = [
                 fields: z.array(fieldSchema).optional(),
                 submit_text: z.string().optional(),
                 success_message: z.string().optional(),
-                actions: z.array(z.object({ type: z.string(), config: z.record(z.unknown()) })).optional(),
             }),
         },
         handler: withErrorBoundary(async (args, { client, siteId }) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.18.0",
+  "version": "0.19.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": {

package/skills/tr-forms.md

@@ -291,6 +291,11 @@ portal at `/app/sites/{siteId}/forms/kontakt/submissions`.
   unique per site — use descriptive names: `kontakt`, `boka`, `nyhetsbrev`.
 - **Honeypot must be invisible.** `_hp` field must have `display:none`.
   If it's visible and a real user fills it, their submission is rejected.
-- **No email notifications yet.** Submissions are stored and visible in
-  the portal's Submissions inbox; the email action handler isn't wired
-  platform-side. Confirm with the customer that they'll check the inbox.
+- **Email notifications are admin-only — not settable via MCP.** Submissions
+  are stored and visible in the portal's Forms → Submissions inbox. A site
+  admin can also configure post-submission emails (admin notification +
+  autoresponder) under **Forms → <form> → Email**, after setting up an email
+  connector under **Settings → Email & notifications**. These carry recipient
+  addresses + templates over submission data, so they're deliberately off the
+  agent surface (`create_form`/`update_form` ignore `actions`). Point the
+  customer at those screens; you can't set them up for them.