@clipform/mcp-server 1.8.1 → 1.9.1

package/dist/prompts.js

@@ -1,272 +0,0 @@
-import { getSessionContext } from "./lib/session-context.js";
-export function registerPrompts(server) {
-    server.registerPrompt("create-quiz", {
-        title: "Create a Quiz",
-        description: "Build a scored knowledge quiz with narrated video questions",
-    }, async () => {
-        const sessionContext = await getSessionContext();
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: "I want to create a quiz. What's the best approach?",
-                    },
-                },
-                {
-                    role: "assistant",
-                    content: {
-                        type: "text",
-                        text: `${sessionContext ? sessionContext + "\n\n" : ""}Here's how to build a great quiz with Clipform. Read the quiz writing guide (clipform://guides/quiz) for detailed craft knowledge on question design, difficulty curves, and narration style.
-
-## Workflow
-
-1. **Research** the topic - find surprising facts, common misconceptions, myth-busters
-2. **Write questions** - follow the difficulty curve (easy start, hard middle, satisfying end). Target 5-8 questions.
-3. **Create the form** with clipform_create_form:
-   - show_step_counter: true
-   - disable_back_navigation: true
-4. **Add questions** with clipform_add_node (type: "choice"):
-   - config: { choice: { show_answer_feedback: true } }
-   - randomise_options: true in config
-   - score: 1 on correct option, score: 0 on wrong
-   - 3-4 wrong answers per question
-5. **Generate narration** with clipform_generate_tts for each question. Tease the question - do NOT reveal the answer or read options aloud. Keep each narration 5-15 seconds.
-6. **Build video** for each question:
-   - clipform_search_media (kind: "image") - 3 images per question
-   - clipform_generate_video - creates Ken Burns video synced to audio
-7. **Attach media** with clipform_upload_node_media. Include captions, set show_captions: true.
-8. **Update end screen** with clipform_update_node - EVERY quiz must have:
-   - show_score: true, icon: "trophy"
-   - show_share_button: true (drives virality)
-   - cta_type: "restart", cta_text: a short challenge like "Beat your score?" or "Try again?"
-   - score_ranges with personalised title + message per tier. Write these in the quiz's voice - short, punchy, and specific to the topic (not generic "Good job!"). Example for a geography quiz:
-     \`\`\`json
-     { "min": 0, "max": 2, "title": "Lost Tourist", "message": "You might need a map - and a compass." },
-     { "min": 3, "max": 5, "title": "Frequent Flyer", "message": "Not bad! You know your way around." },
-     { "min": 6, "max": 8, "title": "World Explorer", "message": "Impressive - you really know your stuff." }
-     \`\`\`
-9. **Publish** with clipform_update_form
-10. **Tag the form** - pass tags: one format (quiz/survey/interview/feedback/lead-gen), one genre (trivia/personality/nps/poll/testimonial), and 2-3 topic words
-11. **Log** with clipform_log_generation (sources, images, attributions)
-
-## Before building, ask
-
-1. How many questions?
-2. Media style: text only, still images, or slideshow video with narration?
-3. Any topic or style preferences?`,
-                    },
-                },
-            ],
-        };
-    });
-    server.registerPrompt("create-personality-quiz", {
-        title: "Create a Personality Quiz",
-        description: "Build a 'Which X are you?' personality quiz with category-based scoring and outcome screens",
-    }, async () => {
-        const sessionContext = await getSessionContext();
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: "I want to create a personality quiz. What's the best approach?",
-                    },
-                },
-                {
-                    role: "assistant",
-                    content: {
-                        type: "text",
-                        text: `${sessionContext ? sessionContext + "\n\n" : ""}Here's how to build a personality quiz with Clipform. Read the personality quiz guide (clipform://guides/personality-quiz) for craft knowledge on category design, option weighting, and outcome writing.
-
-## How it differs from a knowledge quiz
-
-There are NO correct answers. Each option maps to one or more outcome categories via \`scores\` (not \`score\`). The winning category at the end determines which result screen the respondent sees.
-
-## Workflow
-
-1. **Define 3-5 outcome categories** - these are the "personalities" (e.g. "Creative", "Analytical", "Leader", "Collaborator"). More than 5 gets muddy.
-2. **Write questions** - each question should feel revealing but fun. Target 5-8 questions.
-3. **Create the form** with clipform_create_form:
-   - show_step_counter: true
-   - disable_back_navigation: true
-4. **Add questions** with clipform_add_node (type: "choice"):
-   - config: { choice: { show_answer_feedback: false } } (no right/wrong!)
-   - Do NOT set randomise_options (option order matters for personality quizzes - lead with the most appealing)
-   - Each option gets \`scores: { "CategoryA": 2, "CategoryB": 1 }\` - weight towards relevant categories
-   - Every option should score in at least one category (no dead options)
-5. **Generate narration** with clipform_generate_tts - conversational, reflective tone. "What does this say about you?" not "Do you know the answer?"
-6. **Build video** + **attach media** (same as knowledge quiz workflow)
-7. **Update end screen** with clipform_update_node - EVERY personality quiz must have:
-   - show_score: false, icon: "star"
-   - show_share_button: true (personality results are inherently shareable - "I got X, what did you get?")
-   - cta_type: "restart", cta_text: "Find out again?" or "Take it again?"
-   - scoring_results (NOT score_ranges) with a result per category. Write the title as an identity reveal ("You're a Creative!") and the message as a short, flattering description that makes people want to share it. Be specific to the quiz theme, not generic. Example:
-   \`\`\`json
-   {
-     "show_score": false,
-     "icon": "star",
-     "show_share_button": true,
-     "cta_type": "restart",
-     "cta_text": "Retake quiz",
-     "scoring_results": [
-       { "category": "Creative", "title": "You're a Creative!", "message": "You see the world through colour and possibility. Where others see problems, you see raw material." },
-       { "category": "Analytical", "title": "You're an Analyst!", "message": "You don't guess - you figure it out. Your superpower is turning chaos into clarity." }
-     ]
-   }
-   \`\`\`
-8. **Publish** with clipform_update_form
-9. **Tag the form** - pass tags: one format (quiz/survey/interview/feedback/lead-gen), one genre (trivia/personality/nps/poll/testimonial), and 2-3 topic words
-10. **Log** with clipform_log_generation
-
-## Before building, ask
-
-1. What are the possible outcomes/personalities? (3-5 categories)
-2. What's the theme? ("Which city are you?", "What's your work style?", "Which character are you?")
-3. Media style: text only, still images, or slideshow video with narration?`,
-                    },
-                },
-            ],
-        };
-    });
-    server.registerPrompt("create-interview", {
-        title: "Create an Interview",
-        description: "Build a form to collect testimonials, case studies, async video interviews, or journalist responses",
-    }, async () => {
-        const sessionContext = await getSessionContext();
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: "I want to collect responses or testimonials from people. What's the best approach?",
-                    },
-                },
-                {
-                    role: "assistant",
-                    content: {
-                        type: "text",
-                        text: `${sessionContext ? sessionContext + "\n\n" : ""}Here's how to build an interview or testimonial form with Clipform. Read the interview guide (clipform://guides/interview) for detailed craft knowledge on question design and pacing.
-
-## Workflow
-
-1. **Identify the ask** - what do you need from respondents? Testimonial, case study, expert comment, job application?
-2. **Create the form** with clipform_create_form:
-   - show_step_counter: true
-   - disable_back_navigation: false
-3. **Add a warm-up question** - something easy: "Tell us your name and role" (type: "open")
-4. **Add core questions** (type: "open") - 2-3 max, one topic per question. Enable text + audio + video responses.
-5. **Add contact collection** (type: "contact") - first name + email minimum
-6. **Add consent** if needed - "I agree that my response may be used in [context]"
-7. **Update end screen** - set expectations: "Thanks! We'll be in touch."
-8. **Optional: add narration** - warm, inviting tone. "We'd love to hear your story..."
-9. **Publish** with clipform_update_form
-10. **Tag the form** - pass tags: one format (quiz/survey/interview/feedback/lead-gen), one genre (trivia/personality/nps/poll/testimonial), and 2-3 topic words
-
-## Before building, ask
-
-1. What are you collecting? (testimonial, case study, interview, application)
-2. Should respondents reply with video, audio, text, or all three?
-3. Do you need a consent statement?`,
-                    },
-                },
-            ],
-        };
-    });
-    server.registerPrompt("create-survey", {
-        title: "Create a Survey",
-        description: "Build a feedback survey, NPS form, or research questionnaire",
-    }, async () => {
-        const sessionContext = await getSessionContext();
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: "I want to collect feedback or run a survey. What's the best approach?",
-                    },
-                },
-                {
-                    role: "assistant",
-                    content: {
-                        type: "text",
-                        text: `${sessionContext ? sessionContext + "\n\n" : ""}Here's how to build a survey with Clipform. Read the survey guide (clipform://guides/survey) for craft knowledge on question design and reducing respondent fatigue.
-
-## Workflow
-
-1. **Define the key metric** - what's the one number you care about? (NPS, satisfaction, likelihood to recommend)
-2. **Create the form** with clipform_create_form:
-   - show_step_counter: true
-   - disable_back_navigation: false
-3. **Add key metric question first** (type: "choice" or "rating") - put it first while attention is highest
-4. **Add one "why?" follow-up** (type: "open") - "What's the main reason for your score?"
-5. **Add 2-3 specific questions** (type: "choice") - only ask what you'll act on
-6. **Contact** (optional) - only if you need to follow up. Many surveys work better anonymous.
-7. **Update end screen** - "Thanks for your feedback!"
-8. **Publish** with clipform_update_form
-9. **Tag the form** - pass tags: one format (quiz/survey/interview/feedback/lead-gen), one genre (trivia/personality/nps/poll/testimonial), and 2-3 topic words
-
-## Key rule: 5 questions max. Every extra question costs completions.
-
-## Before building, ask
-
-1. What feedback are you collecting? (NPS, satisfaction, event feedback, product research)
-2. Anonymous or identified?
-3. Any specific areas you want to ask about?`,
-                    },
-                },
-            ],
-        };
-    });
-    server.registerPrompt("create-funnel", {
-        title: "Create a Funnel",
-        description: "Build a lead qualification funnel or product recommendation quiz with branching logic",
-    }, async () => {
-        const sessionContext = await getSessionContext();
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: "I want to qualify leads or recommend products based on answers. What's the best approach?",
-                    },
-                },
-                {
-                    role: "assistant",
-                    content: {
-                        type: "text",
-                        text: `${sessionContext ? sessionContext + "\n\n" : ""}Here's how to build a qualification funnel with Clipform. Read the funnel guide (clipform://guides/funnel) for craft knowledge on branching logic and conversion.
-
-## Workflow
-
-1. **Define outcomes** - what segments or recommendations exist? (e.g., Basic/Pro/Enterprise, or product categories)
-2. **Create the form** with clipform_create_form:
-   - show_step_counter: false (funnels feel shorter without it)
-   - disable_back_navigation: true (prevents answer shopping that breaks scoring)
-3. **Add hook question** (type: "choice") - "What best describes you?" or "What are you looking for?" This segments the user.
-4. **Add qualifying questions** (type: "choice") - 2-3 questions that narrow down the need. Assign scores to each option.
-5. **Set branching logic** with clipform_set_logic - route based on answers
-6. **Add contact capture** (type: "contact") - name, email, phone. Place AFTER qualifying questions.
-7. **Update end screen** with score_ranges for personalised outcomes: "Based on your answers, we recommend..."
-8. **Publish** with clipform_update_form
-9. **Tag the form** - pass tags: one format (quiz/survey/interview/feedback/lead-gen), one genre (trivia/personality/nps/poll/testimonial), and 2-3 topic words
-
-## Key rule: 3-5 questions max. Every extra step loses leads.
-
-## Before building, ask
-
-1. What outcomes are you routing to? (products, plans, team members, messages)
-2. What criteria determine the routing?
-3. Do you need contact capture?`,
-                    },
-                },
-            ],
-        };
-    });
-}
-//# sourceMappingURL=prompts.js.map

package/dist/prompts.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,iBAAiB,EAAE,MAAM,0BAA0B,CAAC;AAE7D,MAAM,UAAU,eAAe,CAAC,MAAiB;IAC/C,MAAM,CAAC,cAAc,CACnB,aAAa,EACb;QACE,KAAK,EAAE,eAAe;QACtB,WAAW,EAAE,6DAA6D;KAC3E,EACD,KAAK,IAAI,EAAE;QACT,MAAM,cAAc,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACjD,OAAO;YACP,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAe;oBACrB,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,oDAAoD;qBAC3D;iBACF;gBACD;oBACE,IAAI,EAAE,WAAoB;oBAC1B,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,GAAG,cAAc,CAAC,CAAC,CAAC,cAAc,GAAG,MAAM,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mCAqC/B;qBACxB;iBACF;aACF;SACF,CAAC;IACF,CAAC,CACF,CAAC;IAEF,MAAM,CAAC,cAAc,CACnB,yBAAyB,EACzB;QACE,KAAK,EAAE,2BAA2B;QAClC,WAAW,EAAE,6FAA6F;KAC3G,EACD,KAAK,IAAI,EAAE;QACT,MAAM,cAAc,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACjD,OAAO;YACP,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAe;oBACrB,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,gEAAgE;qBACvE;iBACF;gBACD;oBACE,IAAI,EAAE,WAAoB;oBAC1B,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,GAAG,cAAc,CAAC,CAAC,CAAC,cAAc,GAAG,MAAM,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4EA8CU;qBACjE;iBACF;aACF;SACF,CAAC;IACF,CAAC,CACF,CAAC;IAEF,MAAM,CAAC,cAAc,CACnB,kBAAkB,EAClB;QACE,KAAK,EAAE,qBAAqB;QAC5B,WAAW,EACT,qGAAqG;KACxG,EACD,KAAK,IAAI,EAAE;QACT,MAAM,cAAc,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACjD,OAAO;YACP,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAe;oBACrB,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,oFAAoF;qBAC3F;iBACF;gBACD;oBACE,IAAI,EAAE,WAAoB;oBAC1B,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,GAAG,cAAc,CAAC,CAAC,CAAC,cAAc,GAAG,MAAM,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;oCAqB9B;qBACzB;iBACF;aACF;SACF,CAAC;IACF,CAAC,CACF,CAAC;IAEF,MAAM,CAAC,cAAc,CACnB,eAAe,EACf;QACE,KAAK,EAAE,iBAAiB;QACxB,WAAW,EACT,8DAA8D;KACjE,EACD,KAAK,IAAI,EAAE;QACT,MAAM,cAAc,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACjD,OAAO;YACP,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAe;oBACrB,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,uEAAuE;qBAC9E;iBACF;gBACD;oBACE,IAAI,EAAE,WAAoB;oBAC1B,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,GAAG,cAAc,CAAC,CAAC,CAAC,cAAc,GAAG,MAAM,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;6CAsBrB;qBAClC;iBACF;aACF;SACF,CAAC;IACF,CAAC,CACF,CAAC;IAEF,MAAM,CAAC,cAAc,CACnB,eAAe,EACf;QACE,KAAK,EAAE,iBAAiB;QACxB,WAAW,EACT,uFAAuF;KAC1F,EACD,KAAK,IAAI,EAAE;QACT,MAAM,cAAc,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACjD,OAAO;YACP,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAe;oBACrB,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,2FAA2F;qBAClG;iBACF;gBACD;oBACE,IAAI,EAAE,WAAoB;oBAC1B,OAAO,EAAE;wBACP,IAAI,EAAE,MAAe;wBACrB,IAAI,EAAE,GAAG,cAAc,CAAC,CAAC,CAAC,cAAc,GAAG,MAAM,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;gCAsBlC;qBACrB;iBACF;aACF;SACF,CAAC;IACF,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/resources.d.ts

@@ -1,2 +0,0 @@
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-export declare function registerResources(server: McpServer): void;

package/dist/resources.js

@@ -1,336 +0,0 @@
-import { getSessionContext } from "./lib/session-context.js";
-const WRITING_PRINCIPLES = `## Writing Principles
-
-- **Write for the ear.** Narration is spoken aloud. Short sentences. Natural rhythm.
-- **Research before writing.** Find 2-3 genuinely interesting facts per topic. Generic content doesn't hold attention.
-- **Conversational, not encyclopaedic.** "Here's what's wild about this..." not "The subject is characterized by..."
-- **Cut ruthlessly.** Every word must earn its place.
-- **Never reveal answers in narration.** The user picks from options - narration teases and builds intrigue.
-- **Don't read answer options aloud.** The viewer can see them on screen.
-
-## Narration Tips
-
-- Tease the topic, don't summarise it
-- Give one interesting fact that makes the user curious
-- 5-15 seconds per question narration
-- If TTS comes back too long, trim the copy and regenerate
-
-## Research
-
-Search for the specific subject, not generic terms ("komodo dragon habitat" not "reptile"). Cross-reference facts - quiz answers must be correct. Look for the surprising angle: what would make someone say "wait, really?"
-
-For timeless topics (history, geography, science), write from your own knowledge. For anything recent or uncertain, use web search or clipform_search_news. If neither is available, refuse rather than fabricate.`;
-const MEDIA_WORKFLOW = `## Media Workflow
-
-1. **clipform_generate_tts** - narration audio (returns word-level captions)
-2. **clipform_search_media** (kind: "image") - find 3 images per question
-3. **clipform_generate_video** - Ken Burns video from images + audio
-4. **clipform_upload_node_media** - attach video with captions (set show_captions: true)
-
-**Image selection:**
-- ONLY use URLs from clipform_search_media results
-- Search for the specific subject, not generic terms
-- Pick visually distinct images (different angles, colors, subjects)
-- Landscape images work best for pan effects
-
-**Slideshow defaults:**
-- 3 images per question, random_effects: true
-- transition: { type: "fade", duration: 1 }
-- Auto focal point detection, eased motion, and cinematic vignette are built in`;
-export function registerResources(server) {
-    server.registerResource("guide-quiz", "clipform://guides/quiz", {
-        description: "Craft knowledge for writing engaging quizzes - difficulty curves, question psychology, narration style, scoring",
-        mimeType: "text/markdown",
-    }, async () => ({
-        contents: [
-            {
-                uri: "clipform://guides/quiz",
-                mimeType: "text/markdown",
-                text: `# Quiz Writing Guide
-
-## Psychology
-
-Each question is a micro variable-reward event - the same dopamine loop that keeps people watching. Once someone answers 2-3 questions, sunk cost kicks in and they finish. Viewers mentally compete, then want to compare scores.
-
-**Target 50-60% correct.** Too easy = no challenge. Too hard = people feel stupid and won't share.
-
-## Difficulty Curve
-
-| Position | Difficulty | Purpose |
-|----------|-----------|---------|
-| Q1-Q2 | Easy (80%+ get right) | Build confidence and commitment |
-| Q3-Q5 | Medium | Peak engagement |
-| Q6-Q8 | Hard (include one "gotcha") | The "everyone gets this wrong" moment |
-| Q9-Q10 | One hard, one satisfying medium | End on a smart feeling, not defeat |
-
-## Question Design
-
-- **Myth-busters**: "Sushi means raw fish - True or False?" (False - it means seasoned rice)
-- **Sounds fake but true**: counterintuitive correct answers make people rewatch
-- **Common misconceptions**: "Capital of Australia?" (not Sydney - Canberra)
-- Under 12-15 words per question for mobile readability
-- Trigger gut reactions, not deep thinking
-
-## Wrong Answer Generation
-
-For numeric questions (population, speed, weight), scale the real answer by random multipliers (0.3x to 3x) rounded to the same magnitude. Makes wrong answers plausible but clearly different.
-
-## Narration Style
-
-You're a quiz master, not a question reader. Each question's narration should:
-
-1. **Tease** - set the scene, build intrigue ("This one catches everyone out")
-2. **Give context** - one interesting fact that makes the question richer
-3. **Pose the question** - "So here's the question..."
-
-**Don't say:**
-- "You either know it or you don't" (meaningless filler)
-- "This is a really hard one" on every question (loses impact)
-- "Welcome to my quiz" / "Hey guys" (wastes time, skip to Q1)
-
-${WRITING_PRINCIPLES}
-
-${MEDIA_WORKFLOW}`,
-            },
-        ],
-    }));
-    server.registerResource("guide-personality-quiz", "clipform://guides/personality-quiz", {
-        description: "Craft knowledge for building personality quizzes - category design, option weighting, outcome writing, no right/wrong answers",
-        mimeType: "text/markdown",
-    }, async () => ({
-        contents: [
-            {
-                uri: "clipform://guides/personality-quiz",
-                mimeType: "text/markdown",
-                text: `# Personality Quiz Guide
-
-## How it works
-
-Personality quizzes use **category-based scoring** (the \`scores\` field on options) instead of right/wrong scoring. Each option distributes points across outcome categories. The category with the highest total at the end determines the result.
-
-## Category Design
-
-- **3-5 categories** is the sweet spot. Fewer feels too binary, more feels random.
-- Categories should be **distinct but equally appealing**. Nobody wants to get the "bad" result.
-- Name them after the outcome, not the trait: "Explorer" not "Adventurous", "The Architect" not "Organised".
-
-## Option Weighting
-
-Each option scores into one or more categories:
-
-\`\`\`json
-{ "scores": { "Explorer": 3, "Homebody": 0, "Foodie": 1 } }
-\`\`\`
-
-Guidelines:
-- **Primary category**: 2-3 points (this is the option's "home" category)
-- **Secondary**: 1 point (slight lean towards another category)
-- **Unrelated**: 0 (omit or set to 0)
-- **Knockout**: -1 (use sparingly - strongly rules out a category)
-- Every option should score positively in at least one category
-- Avoid giving every option the same spread - it makes results feel random
-
-## Question Design
-
-- Questions should feel **personally revealing** but low-stakes: "Pick your ideal Saturday morning" not "What's your biggest weakness?"
-- Scenario-based questions work better than abstract preference questions
-- Each question should meaningfully differentiate between categories
-- Avoid questions where all options clearly map to one obvious personality
-
-## Outcome Screens
-
-Each category needs a \`scoring_results\` entry on the end screen:
-
-- **Title**: "You're a [Category]!" - celebratory, not clinical
-- **Message**: 2-3 sentences that feel like a personalised insight. Reference specific traits the quiz measured.
-- **Optional CTA**: link to relevant content, product, or next step
-
-## Narration Style
-
-Reflective and curious, not quizmaster-y:
-- "This one says a lot about you..."
-- "There's no wrong answer here - go with your gut"
-- "What does your choice reveal?"
-
-Do NOT say "let's see if you get this right" - there is no right answer.
-
-${WRITING_PRINCIPLES}
-
-${MEDIA_WORKFLOW}`,
-            },
-        ],
-    }));
-    server.registerResource("guide-interview", "clipform://guides/interview", {
-        description: "Craft knowledge for building interview and testimonial collection forms - warm-up pacing, open questions, consent, video responses",
-        mimeType: "text/markdown",
-    }, async () => ({
-        contents: [
-            {
-                uri: "clipform://guides/interview",
-                mimeType: "text/markdown",
-                text: `# Interview & Testimonial Guide
-
-## Purpose
-
-Collect responses from people - testimonials, case studies, journalist callouts, async video interviews, candidate screening. The common thread: you're asking someone to respond on camera or in their own words.
-
-## Structure
-
-1. **Warm-up question** - something easy and low-stakes to get them comfortable. "Tell us your name and what you do" or "What's your role?"
-2. **Core questions** - the real ask. Open-ended, one topic per question. Don't over-split - 2-3 core questions max.
-3. **Follow-up** (optional) - "Anything else you'd like to add?" catches things you didn't think to ask.
-4. **Contact collection** - first name + email minimum. Add phone/company if relevant.
-5. **Consent** - "I agree that my response may be used in [context]." Always include for testimonials and media.
-6. **End screen** - set expectations: "Thanks! We'll be in touch if we'd like to take things further."
-
-## Question Design
-
-- **Open-ended by default.** Use "open" type with text + audio + video response enabled. Let the respondent choose their format.
-- **One topic per question.** "Tell us about your experience AND what you'd change" is two questions.
-- **Prompt, don't interrogate.** "What surprised you most about working with us?" beats "Rate your satisfaction."
-- **Keep it short.** 3-5 questions total. Every extra question loses respondents.
-
-## Narration for Interviews
-
-Warmer and more personal than quiz narration. You're inviting someone to share, not testing them.
-
-- "We'd love to hear your story..."
-- "Take your time with this one - there's no wrong answer"
-- Keep narration under 10 seconds - the respondent's answer is the content, not yours
-
-## Settings
-
-- disable_back_navigation: false (let people review their answers)
-- show_step_counter: true (so they know how much is left)
-
-${WRITING_PRINCIPLES}
-
-${MEDIA_WORKFLOW}`,
-            },
-        ],
-    }));
-    server.registerResource("guide-survey", "clipform://guides/survey", {
-        description: "Craft knowledge for feedback surveys, NPS, and research forms - brevity, rating scales, respondent fatigue",
-        mimeType: "text/markdown",
-    }, async () => ({
-        contents: [
-            {
-                uri: "clipform://guides/survey",
-                mimeType: "text/markdown",
-                text: `# Survey & Feedback Guide
-
-## Purpose
-
-Collect structured feedback - NPS, customer satisfaction, product research, post-event feedback. The goal is clean, analysable data with minimal respondent fatigue.
-
-## Structure
-
-Surveys should be ruthlessly short. Every extra question costs you completions.
-
-1. **Key metric** - the one number you care about (NPS, satisfaction rating, likelihood to recommend). Put it first while attention is highest.
-2. **Follow-up** - one open-ended "why?" question. "What's the main reason for your score?" This is where the insight lives.
-3. **Specific questions** (optional) - 2-3 targeted choice questions on specific areas. Don't fish - only ask what you'll act on.
-4. **Contact** (optional) - only if you need to follow up. Many surveys are better anonymous.
-5. **End screen** - "Thanks for your feedback!" Keep it simple.
-
-## Question Design
-
-- **Choice questions for data, open questions for insight.** Don't use open-ended where a rating scale would do, and don't use ratings where you need to understand why.
-- **Balanced scales.** Equal positive and negative options. "Excellent / Good / Fair / Poor" not "Amazing / Great / Good / OK / Bad."
-- **No leading questions.** "How much did you enjoy...?" assumes they enjoyed it.
-- **5 questions max.** If you need more, you're running research, not a survey - split it up.
-
-## Narration for Surveys
-
-Optional - many surveys work fine as text only. If using narration:
-
-- Keep it brief (5-8 seconds). "We'd love your quick feedback on..."
-- Don't narrate every question - just the opener to set the tone
-- Friendly but efficient. Respect their time.
-
-## Settings
-
-- disable_back_navigation: false
-- show_step_counter: true (shows progress, reduces abandonment)
-
-${WRITING_PRINCIPLES}`,
-            },
-        ],
-    }));
-    server.registerResource("guide-funnel", "clipform://guides/funnel", {
-        description: "Craft knowledge for lead qualification funnels and product recommendation quizzes - branching logic, progressive profiling, conversion",
-        mimeType: "text/markdown",
-    }, async () => ({
-        contents: [
-            {
-                uri: "clipform://guides/funnel",
-                mimeType: "text/markdown",
-                text: `# Lead Qualification & Product Recommendation Guide
-
-## Purpose
-
-Route people to the right outcome based on their answers. Lead qualification scores and segments prospects. Product recommendation guides users to the right product. Both use branching logic to personalise the journey.
-
-## Structure
-
-1. **Hook question** - immediately relevant, low friction. "What are you looking for?" or "What best describes you?" This segments the user and determines the branch.
-2. **Qualifying questions** - 2-3 questions that narrow down the need. Each answer can branch to a different path.
-3. **Contact capture** - name, email, phone. Place AFTER qualifying questions so they've invested before you ask for details.
-4. **Outcome screen** - personalised end screen based on their answers. Use score_ranges or branching logic to show different messages.
-
-## Question Design
-
-- **Progressive profiling.** Start broad, get specific. Don't ask for budget on question 1.
-- **Every question must earn its place.** If the answer doesn't change the outcome or routing, cut the question.
-- **Choice questions, not open-ended.** You need structured data to route and score. Save open-ended for "anything else?"
-- **3-5 questions max.** Every extra step loses leads. The funnel is leaky by nature - keep it tight.
-
-## Branching Logic
-
-Use clipform_set_logic to route based on answers:
-
-- **Segment early.** Q1 answer determines which Q2 they see.
-- **Converge at capture.** All branches should reach the contact collection step.
-- **Different outcomes for different segments.** The end screen should feel personalised: "Based on your answers, we recommend..." not a generic "Thanks!"
-
-## Scoring for Product Recommendation
-
-- Assign scores to each option based on which product/outcome it points to
-- Use score_ranges on the end screen to show different recommendations
-- Example: score 0-3 = "Basic plan", 4-6 = "Pro plan", 7+ = "Enterprise - let's talk"
-
-## Narration for Funnels
-
-Short and action-oriented. You're guiding, not teaching.
-
-- "Let's find the right fit for you..."
-- "Just a couple of quick questions..."
-- Keep total narration under 30 seconds across the whole funnel
-
-## Settings
-
-- disable_back_navigation: true (prevent answer shopping that breaks scoring)
-- show_step_counter: false (funnels feel shorter without a counter)
-
-${WRITING_PRINCIPLES}`,
-            },
-        ],
-    }));
-    server.registerResource("context-session", "clipform://context/session", {
-        description: "Current session info: auth mode, workspace, plan tier, node limits, feature flags. Read this before planning content to know your constraints.",
-        mimeType: "text/markdown",
-        annotations: { audience: ["assistant"], priority: 1.0 },
-    }, async () => {
-        const text = await getSessionContext();
-        return {
-            contents: [
-                {
-                    uri: "clipform://context/session",
-                    mimeType: "text/markdown",
-                    text: text || "Session context unavailable - API may not be reachable.",
-                },
-            ],
-        };
-    });
-}
-//# sourceMappingURL=resources.js.map

package/dist/resources.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"resources.js","sourceRoot":"","sources":["../src/resources.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,iBAAiB,EAAE,MAAM,0BAA0B,CAAC;AAE7D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;mNAoBwL,CAAC;AAEpN,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;gFAgByD,CAAC;AAEjF,MAAM,UAAU,iBAAiB,CAAC,MAAiB;IACjD,MAAM,CAAC,gBAAgB,CACrB,YAAY,EACZ,wBAAwB,EACxB;QACE,WAAW,EACT,iHAAiH;QACnH,QAAQ,EAAE,eAAe;KAC1B,EACD,KAAK,IAAI,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR;gBACE,GAAG,EAAE,wBAAwB;gBAC7B,QAAQ,EAAE,eAAe;gBACzB,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA0Cd,kBAAkB;;EAElB,cAAc,EAAE;aACT;SACF;KACF,CAAC,CACH,CAAC;IAEF,MAAM,CAAC,gBAAgB,CACrB,wBAAwB,EACxB,oCAAoC,EACpC;QACE,WAAW,EACT,+HAA+H;QACjI,QAAQ,EAAE,eAAe;KAC1B,EACD,KAAK,IAAI,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR;gBACE,GAAG,EAAE,oCAAoC;gBACzC,QAAQ,EAAE,eAAe;gBACzB,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAoDd,kBAAkB;;EAElB,cAAc,EAAE;aACT;SACF;KACF,CAAC,CACH,CAAC;IAEF,MAAM,CAAC,gBAAgB,CACrB,iBAAiB,EACjB,6BAA6B,EAC7B;QACE,WAAW,EACT,oIAAoI;QACtI,QAAQ,EAAE,eAAe;KAC1B,EACD,KAAK,IAAI,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR;gBACE,GAAG,EAAE,6BAA6B;gBAClC,QAAQ,EAAE,eAAe;gBACzB,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAmCd,kBAAkB;;EAElB,cAAc,EAAE;aACT;SACF;KACF,CAAC,CACH,CAAC;IAEF,MAAM,CAAC,gBAAgB,CACrB,cAAc,EACd,0BAA0B,EAC1B;QACE,WAAW,EACT,4GAA4G;QAC9G,QAAQ,EAAE,eAAe;KAC1B,EACD,KAAK,IAAI,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR;gBACE,GAAG,EAAE,0BAA0B;gBAC/B,QAAQ,EAAE,eAAe;gBACzB,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAoCd,kBAAkB,EAAE;aACb;SACF;KACF,CAAC,CACH,CAAC;IAEF,MAAM,CAAC,gBAAgB,CACrB,cAAc,EACd,0BAA0B,EAC1B;QACE,WAAW,EACT,wIAAwI;QAC1I,QAAQ,EAAE,eAAe;KAC1B,EACD,KAAK,IAAI,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR;gBACE,GAAG,EAAE,0BAA0B;gBAC/B,QAAQ,EAAE,eAAe;gBACzB,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA+Cd,kBAAkB,EAAE;aACb;SACF;KACF,CAAC,CACH,CAAC;IAEF,MAAM,CAAC,gBAAgB,CACrB,iBAAiB,EACjB,4BAA4B,EAC5B;QACE,WAAW,EACT,gJAAgJ;QAClJ,QAAQ,EAAE,eAAe;QACzB,WAAW,EAAE,EAAE,QAAQ,EAAE,CAAC,WAAW,CAAC,EAAE,QAAQ,EAAE,GAAG,EAAE;KACxD,EACD,KAAK,IAAI,EAAE;QACT,MAAM,IAAI,GAAG,MAAM,iBAAiB,EAAE,CAAC;QACvC,OAAO;YACL,QAAQ,EAAE;gBACR;oBACE,GAAG,EAAE,4BAA4B;oBACjC,QAAQ,EAAE,eAAe;oBACzB,IAAI,EAAE,IAAI,IAAI,yDAAyD;iBACxE;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/server.d.ts

@@ -1,2 +0,0 @@
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-export declare function createServer(): McpServer;

package/dist/tools/add-node.d.ts

@@ -1,2 +0,0 @@
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-export declare function registerAddNodeTool(server: McpServer): void;