For developers

CRAFT Content docs

For developers and marketing operations teams. The decision: how to call CRAFT Content from your own code or assistant.

This page covers the MCP address, the REST API behind the web forms and every input field of all 8 tools.

By Shashwat Ghosh, Co-Founder and Fractional CMO, Helix GTM Consulting · Last updated 2 November 2026

Try these prompts

Use CRAFT Content to draft a customer case study. Customer: a food delivery company. Our product: our product. Challenge: a ticket backlog growing faster than the support team could hire. Solution: AI agents that resolve refund and order-status tickets in the help desk, with human approval for refunds. Results: 45% of tickets resolved without a human in 60 days. Mode: full.
Build a practitioner newsletter with CRAFT Content about AI agents in customer support. Call to action: register for our support automation webinar.
Write a 45-minute educational webinar script with CRAFT Content on AI agents that resolve support tickets safely, for support leaders at consumer apps and SaaS companies.
Review this landing page copy with CRAFT Content and suggest improvements: 'our product leverages cutting-edge AI to empower support teams to deliver best-in-class experiences at scale.'

MCP server

Address: https://craft-content.gtmhelix.com/mcp (Streamable HTTP, stateless, JSON responses). GET returns 405 by design.
Authentication: none. Every tool is marked read-only (readOnlyHint: true, destructiveHint: false) and has a title.
Rate limit: 300 requests per minute per IP address. Server: craft-content-mcp version 2.2.23.
Limits: 262,144 bytes per call; text fields up to 4,000 characters, except the document fields interview_notes (Case Study Generator), source_content (Content Repurposer) and content (CRAFT Content Improver), which take up to 100,000; one call per request (no batches). A call over a limit is refused before the tool runs.
Local use: npx -y @shashwatgtmalpha/craft-content-mcp runs these tools over stdio (npm can lag behind this site until a new version is published).

REST API (used by the web forms)

Send POST https://craft-content.gtmhelix.com/api/tools/<tool name> with a JSON body {"input": {...}}. The answer is JSON: {"ok": true, "tool": "...", "title": "...", "text": "..."}, where text is the same Markdown the MCP tool returns. The endpoint calls the same server code as the MCP address.

Terminal

curl -s -X POST https://craft-content.gtmhelix.com/api/tools/case_study_generator \
  -H "Content-Type: application/json" \
  -d '{"input": {"customer_name": "a food delivery company", "your_product": "our product", "customer_industry": "Food delivery", "mode": "full", "challenge": "A ticket backlog growing faster than the support team could hire", "solution": "AI agents that resolve refund and order-status tickets inside the help desk, with human approval for refunds", "results": "45% of tickets resolved without a human in 60 days; first response time down from 6 hours to 2 minutes"}}'

Errors: 400 with errors (missing or invalid fields), 404 for an unknown tool, 405 for methods other than POST, 413 above 32,000 bytes, 422 when the tool itself refuses the input (ok is false and error holds the tool's message), 429 when the rate limit is reached, 500 if the tool fails.
Limits: 30 requests per minute per IP address; the whole request up to 32,000 bytes; top level text fields up to 6,000 characters and top level lists up to 50 items.
Forms without JavaScript post application/x-www-form-urlencoded and get an HTML page back.
Inputs and answers are not stored, and the input is not logged (see Privacy).

Release history

History: first released 16 January 2026, on npm and in the MCP Registry. Dates for npm and the MCP Registry come from their public records; later versions come from the commits in the GitHub repository. npm can lag behind this site until a new version is published.

Version	Date	Where
1.0.0	16 January 2026	npm
1.0.1	16 January 2026	npm and the MCP Registry
2.0.0	16 January 2026	npm
2.0.1	16 January 2026	npm
2.1.0	24 September 2026	GitHub, commit 4a8186a
2.2.0	26 September 2026	GitHub, commit 48907e9
2.2.1	26 September 2026	GitHub, commit c84c02d
2.2.2	27 September 2026	GitHub, commit 5d9aec5
2.2.3	27 September 2026	GitHub, commit 7de2eb0
2.2.4	27 September 2026	GitHub, commit 3b8da5b
2.2.5	27 September 2026	GitHub, commit c65f99d
2.2.6	28 September 2026	GitHub, commit dae40d7
2.2.7	28 September 2026	GitHub, commit a0f289e
2.2.8	28 September 2026	GitHub, commit db4a9b0
2.2.9	29 September 2026	GitHub, commit bf536f6
2.2.10	29 September 2026	GitHub, commit 616bcac
2.2.11	29 September 2026	GitHub, commit 24507f0
2.2.12	29 September 2026	GitHub, commit d6dc562
2.2.13	30 September 2026	GitHub, commit 7ed2cde
2.2.14	30 September 2026	GitHub, commit e097efe
2.2.15	30 September 2026	GitHub, commit 62838d4
2.2.18	12 October 2026	safety fix only: the instruction echo safeguard; tool list and answers otherwise unchanged
2.2.22	15 October 2026	security update only: MCP SDK 1.31.0 (advisory GHSA-6qxp-vccf-f47h); tool list and answers unchanged
2.2.23 (this site)	18 October 2026	quality update (run 42B): sector knowledge for the nine verticals on every tool; sub industry notes only when your own words name one; case studies, emails, value propositions and webinar plans keep whole phrases and quotes; a usage count per tool (no text you type is kept)

Tool reference

Generated from the server's own input schemas, version 2.2.23.

Case Study Generator

case_study_generator

Helps you turn a customer result into a case study, built from the customer name, your product and the challenge, solution and results you give (mode full), or an interview kit to collect them (mode discovery). Optional customer industry, quote, interview notes and business model fit the wording to the customer. Returns a headline, the story with each result you list, a customer quote, social and email copy, and sector notes when the sector can be read from your text. A bracket marks anything you did not give. See what it does.

Field	Type	Required	Allowed values	Meaning
`customer_name`	string	yes		Customer/company name
`customer_industry`	string	no		Customer's industry for context
`mode`	string	no	full, discovery	full = generate case study (requires challenge/solution/results), discovery = generate interview questions to gather story
`interview_notes`	string	no		Optional: Raw interview notes or transcript. Parsed into a case study when mode is 'full'
`challenge`	string	no		The customer's challenge/problem (required for full mode)
`solution`	string	no		How your product solved it (required for full mode)
`results`	string	no		Quantifiable outcomes (required for full mode)
`customer_quote`	string	no		Optional: Direct quote from customer
`your_product`	string	yes		Your product/service name
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

newsletter_builder

Helps you decide what goes in a newsletter issue and which subject line to test, from your topic and the action you want readers to take. Optional key points, audience segment, newsletter type, tone, earlier topics and your product fit it to the reader. Returns a first draft with subject line and preview, an opening, a short section for each key point, your call to action as the button, A/B subject lines, other opening hooks and sector notes. It adds no statistic or customer story and says what it did not get. See what it does.

Field	Type	Required	Allowed values	Meaning
`topic`	string	yes		Main topic/theme of the newsletter
`key_points`	string	no		OPTIONAL: Key points to cover (comma-separated). If not provided, the tool suggests 5 points based on the topic and newsletter type
`cta_goal`	string	yes		What action should readers take? (e.g., 'sign up for webinar', 'try feature', 'read blog')
`audience_segment`	string	no	executives, practitioners, technical, general, prospects, customers	Audience segment affects tone and depth
`newsletter_type`	string	no	educational, product_update, industry_news, thought_leadership, curated_links	Type of newsletter
`tone`	string	no	professional, conversational, authoritative, friendly, urgent	Writing tone
`previous_topics`	string	no		Optional: Recent newsletter topics to avoid repetition and suggest connections
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

Webinar Script

webinar_script

Helps you plan a webinar that leads to meetings, from your topic, target audience and webinar type. Optional duration, key takeaways, speakers, polls, product mention level, your product and business model shape it. Returns a run of show, a full spoken script with speaker lines and on screen cues, polls with answer options, likely questions with answers, a follow up email sequence and sector notes. It uses only what you gave and says what it did not get. See what it does.

Field	Type	Required	Allowed values	Meaning
`topic`	string	yes		Webinar topic/title
`target_audience`	string	yes		Who will attend (e.g., 'Marketing managers at B2B SaaS companies')
`webinar_type`	string	yes	educational, product_demo, panel_discussion, customer_story, workshop, ama	Type of webinar determines structure
`duration`	string	no	30_min, 45_min, 60_min, 90_min	Webinar length
`key_takeaways`	string	no		OPTIONAL: 3-5 things attendees should learn (comma-separated). If not provided, we'll suggest based on topic
`speakers`	string	no		Optional: Speaker names and titles (comma-separated)
`include_polls`	boolean	no		Include interactive poll suggestions
`product_mention_level`	string	no	none, subtle, moderate, heavy	Whether to add product tie-in placeholders to the script ('none' leaves them out)
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

Content Repurposer

content_repurposer

Helps you get more from a single piece of content: it needs the source text and its type. Optional target formats, brand voice and a key message steer the result. Returns versions for other channels (a LinkedIn post, an X thread, an email, a blog summary and quote cards), each written from whole sentences of your source with key points kept in source order. Claims it cannot support are listed to source, and any format it does not know is named. See what it does.

Field	Type	Required	Allowed values	Meaning
`source_content`	string	yes		Original content to repurpose (blog post, article, transcript, etc.)
`source_type`	string	yes	blog_post, webinar_transcript, podcast_transcript, whitepaper, case_study, research_report, presentation	What type of content is the source
`target_formats`	string	no		OPTIONAL: Formats to generate (comma-separated). Defaults to: linkedin_post, twitter_thread, email, blog_summary, quote_cards. Other options: infographic_outline, video_script, podcast_talking_points, slide_deck_outline, newsletter_section
`brand_voice`	string	no	professional, casual, authoritative, friendly, bold	Brand voice to maintain
`key_message`	string	no		Optional: Core message to emphasize across all formats
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

Thought Leadership Series

thought_leadership_series

Helps you decide what to publish to make your point of view known, from your topic, your take and the reader you write for. Optional proof points, author background, number of articles and article style shape it. Returns, for each article, a headline and a short first draft with the objection it answers, your proof and a way to test the idea, a promotional post for each, a publishing order and sector notes. Your words are quoted as written and no result, customer or figure is invented. See what it does.

Field	Type	Required	Allowed values	Meaning
`topic`	string	yes		The topic you want to establish authority on
`your_take`	string	yes		Your unique perspective or opinion on this topic. What do you believe that others don't? What's your contrarian view?
`target_reader`	string	yes		Who should read this? Be specific (e.g., 'B2B SaaS founders struggling with churn' not just 'marketers')
`proof_points`	string	no		OPTIONAL: Evidence supporting your take: personal stories, client examples, data/stats (comma-separated). If not provided, we'll suggest proof points to gather
`author_background`	string	no		Optional: Your role and why you're credible (e.g., '15 years in enterprise sales')
`num_articles`	integer (1 to 5)	no		How many articles to outline, a whole number from 1 to 5. If left out, the series has three articles
`article_type`	string	no	contrarian, how_to, lessons_learned, prediction, framework	Style of articles
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

Testimonial Capture

testimonial_capture

Helps you ask a happy customer for a testimonial, from the customer's name, company, success story and the type of testimonial you want. Optional role, relationship, intended use, incentive, your product and business model fit it to the customer. Returns a request email, interview questions for the customer's role and sector, quote drafts for the customer to edit and a sign off checklist. It uses your product name when you give it and says so when you do not. See what it does.

Field	Type	Required	Allowed values	Meaning
`customer_name`	string	yes		Customer name
`customer_company`	string	yes		Customer's company
`customer_role`	string	no		Customer's job title
`relationship_context`	string	no		How long they've been a customer, key interactions
`success_story`	string	yes		Brief description of their success with your product
`testimonial_type`	string	yes	written_quote, video_interview, case_study_interview, g2_review, reference_call	Type of testimonial needed
`use_case`	string	no		Where will this testimonial be used? (website, sales deck, etc.)
`incentive`	string	no		Optional: What you're offering in return
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

Sales Enablement Content

sales_enablement_content

Helps you decide what sellers should say at each stage of a deal, from your product, the persona you sell to and your proof points. Optional objections, value propositions, competitor objections, price context, sales stage and business model shape it. Returns a pitch order, an answer to each objection with the proof point that fits it, competitor responses, discovery questions and follow up templates. Without objections it suggests the ones your sector raises. See what it does.

Field	Type	Required	Allowed values	Meaning
`product`	string	yes		Product name and what it does
`target_persona`	string	yes		Who sales is pitching to (role, company type)
`proof_points`	string	yes		Evidence for claims: case studies, metrics, quotes (comma-separated)
`common_objections`	string	no		OPTIONAL: Sales objections you hear (comma-separated). If not provided, we'll suggest likely objections for your product type
`value_props`	string	no		OPTIONAL: Key value propositions (comma-separated). Will be DERIVED from proof points if not provided
`competitor_objections`	string	no		Optional: 'Why not [competitor]' objections
`price_context`	string	no		Optional: Your pricing vs market (e.g., 'Premium, 20% above market', 'Budget option', 'Mid-market')
`sales_stage`	string	no	prospecting, discovery, demo, negotiation, closing	What stage of sales funnel
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

CRAFT Content Improver

craft_content_improver

Helps you decide whether a draft is ready to publish and what to fix first, from the pasted copy and its content type. Optional goal, audience and tone preference refine the review. Returns a score for each area (buzzwords, claims that need proof, fragments, unfilled merge fields, claims about the reader, a missing figure or ask) with each deduction quoted from your text, and the edits it made. If it finds nothing to edit, it says so and prints no improved version. See what it does.

Field	Type	Required	Allowed values	Meaning
`content`	string	yes		Content to analyze
`content_type`	string	yes	blog_post, email, landing_page, social_post, sales_email, product_description, press_release, case_study	Type of content affects evaluation criteria
`goal`	string	no		OPTIONAL: What should this content achieve? (e.g., 'drive signups', 'educate readers'). If not given, a goal is chosen from the content type (for example 'Get meetings booked' for a sales email)
`audience`	string	no		OPTIONAL: Who is this content for? Helps tailor improvements.
`tone_preference`	string	no	more_formal, more_casual, more_urgent, more_friendly, more_authoritative, keep_same	Desired tone (accepted for compatibility; it does not change the analysis)
`your_sector`	string	no	logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

How to read the answer

Both the MCP server and the REST endpoint return the same structured Markdown text for a given input object, or, from the REST endpoint, an HTTP 400 error listing any missing or invalid fields or a 422 when the tool itself refuses the input. Inside the returned Markdown, bracketed placeholders mark missing facts and any unprovided benchmark is labelled as an example figure.

What to do next

Founder: Test a tool call with the example cURL request or MCP URL using your own product and customer facts.
CEO: Review the tool reference to see which required and optional fields your team should supply for complete drafts.
CMO: Use the input schemas to standardize the briefs your team feeds into Case Study Generator, Newsletter Builder, and Sales Enablement Content.
CRO: Check the fields for Sales Enablement Content and Case Study Generator so sellers pass complete deal and competitor context.
Demand generation head: Pass your real audience, topic, and channel parameters into Webinar Script, Newsletter Builder, and Content Repurposer.

Why come back

Come back when you wire a tool into an internal workflow, check allowed enum values, or review the latest release notes. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.

Choose your app

Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.

Connector setup guides · Skills package setup guide · Find the skills on skills.sh