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-mcpversion 2.1.0. - Local use:
npx -y @shashwatgtmalpha/craft-content-mcpruns the same tools over stdio.
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.
curl -s -X POST https://craft-content.gtmhelix.com/api/tools/case_study_generator \
-H "Content-Type: application/json" \
-d '{"input": {"customer_name": "Northwind Clinics", "your_product": "ClinicFlow", "customer_industry": "healthcare", "mode": "full", "challenge": "Missed appointments were costing revenue", "solution": "Automated SMS reminders and online rescheduling", "results": "No-shows down 30% in 3 months"}}'
- Errors: 400 with
errors(missing or invalid fields), 404 for an unknown tool, 405 for methods other than POST, 413 above 32,000 bytes, 429 when the rate limit is reached, 500 if the tool fails. - Limits: 30 requests per minute per IP address; text fields up to 6,000 characters; lists up to 50 items.
- Forms without JavaScript post
application/x-www-form-urlencodedand get an HTML page back. - Nothing is stored and the input is not logged (see Privacy).
Tool reference
Generated from the server's own input schemas on 25 September 2026.
Case Study Generator case_study_generator
Generate case studies with DISCOVERY MODE. If you have the full story, get a complete case study. If not, get interview questions to gather the story first. Open the form.
| 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 |
Newsletter Builder newsletter_builder
Build newsletter content. Just have a topic? We'll suggest key points. Have key points? We'll craft the content. Open the form.
| 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, we'll suggest 3-5 relevant points based on topic | |
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 |
Webinar Script webinar_script
Generate webinar scripts. Know your takeaways? Get a complete script. Still planning? We'll suggest takeaways based on topic and type. Open the form.
| 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) |
Content Repurposer content_repurposer
Transform source content into multiple formats. Just paste content - we'll generate the 5 most useful formats by default, or specify exactly what you need. Open the form.
| 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 |
Thought Leadership Series thought_leadership_series
Generate thought leadership article drafts (about 600 to 800 words each) from your topic, your take and your proof points. Without proof points, the drafts include suggested proof points to gather. Drafts contain placeholders to complete before publishing. Open the form.
| 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 | number | no | Number of articles to generate (1-5) | |
article_type | string | no | contrarian, how_to, lessons_learned, prediction, framework | Style of articles |
Testimonial Capture testimonial_capture
Generate testimonial request emails, interview questions, and formatted outputs. Discovery-focused by design. Open the form.
| 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 |
Sales Enablement Content sales_enablement_content
Generate sales content. Know your objections? Get complete handlers. New product with no sales data yet? We'll suggest likely objections based on your product type. Open the form.
| 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 |
CRAFT Content Improver craft_content_improver
Analyze content for clarity, structure and engagement, score each area, and return suggestions, including a version with common jargon replaced and long sentences split. Open the form.
| 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'). Defaults to 'improve engagement and clarity' | |
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) |