CRAFT Content: 8 B2B content tools by Helix GTM Consulting
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Builds a customer case study from the customer name, your product and the challenge, solution and results you give (mode full), or an interview kit for collecting 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.
Your product or service name
Customer or company name
full builds the case study and needs the challenge, solution and results; discovery returns interview questions for collecting them
Measurable outcomes, one per line or per semicolon (needed in full mode)
How your product solved it (needed in full mode)
The customer's challenge or problem (needed in full mode)
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.
Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how.
Optional: a direct quote from the customer
Optional: raw interview notes or a transcript. In full mode they fill a missing challenge, solution or results; the answer says they were not used when you gave all three
The customer's industry, used for context
Builds a customer case study from the customer name, your product and the challenge, solution and results you give (mode full), or an interview kit for collecting 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.
| Argument | Type | Description |
|---|---|---|
| mode | string | full builds the case study and needs the challenge, solution and results; discovery returns interview questions for collecting them |
| results | string | Measurable outcomes, one per line or per semicolon (needed in full mode) |
| solution | string | How your product solved it (needed in full mode) |
| challenge | string | The customer's challenge or problem (needed in full mode) |
| your_sector | string | 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. |
| your_product* | string | Your product or service name |
| customer_name* | string | Customer or company name |
| business_model | string | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| customer_quote | string | Optional: a direct quote from the customer |
| interview_notes | string | Optional: raw interview notes or a transcript. In full mode they fill a missing challenge, solution or results; the answer says they were not used when you gave all three |
| customer_industry | string | The customer's industry, used for context |
{
"type": "object",
"required": [
"customer_name",
"your_product"
],
"properties": {
"mode": {
"enum": [
"full",
"discovery"
],
"type": "string",
"description": "full builds the case study and needs the challenge, solution and results; discovery returns interview questions for collecting them"
},
"results": {
"type": "string",
"description": "Measurable outcomes, one per line or per semicolon (needed in full mode)"
},
"solution": {
"type": "string",
"description": "How your product solved it (needed in full mode)"
},
"challenge": {
"type": "string",
"description": "The customer's challenge or problem (needed in full mode)"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"your_product": {
"type": "string",
"description": "Your product or service name"
},
"customer_name": {
"type": "string",
"description": "Customer or company name"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how."
},
"customer_quote": {
"type": "string",
"description": "Optional: a direct quote from the customer"
},
"interview_notes": {
"type": "string",
"description": "Optional: raw interview notes or a transcript. In full mode they fill a missing challenge, solution or results; the answer says they were not used when you gave all three"
},
"customer_industry": {
"type": "string",
"description": "The customer's industry, used for context"
}
}
}Turns a source text into finished versions for other channels: a LinkedIn post, an X thread, an email, a blog summary and quote cards. Needs the source text and its type. Optional target formats, brand voice and a key message steer the result. Each version is written from whole sentences of your source, with key points chosen by a stated rule and kept in the source order; claims it cannot support are listed to source, and any requested format it does not know is named. Returns the versions, notes on the key points and proof used, and sector notes.
| Argument | Type | Description |
|---|---|---|
| brand_voice | string | The brand voice to keep |
| key_message | string | Optional: the core message to emphasize in every format |
| source_type* | string | The kind of content the source is |
| your_sector | string | 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. |
| source_content* | string | The original content to repurpose (a blog post, article or transcript, for example) |
| target_formats | string | 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. A name outside this list is reported, not written |
Reviews pasted copy and its content type against listed rules: buzzwords, claims that need proof, fragments, unfilled merge fields, claims about the reader and a missing figure or ask. Optional goal, audience and tone preference refine the review. Returns a score for each area with each deduction quoted from your text, and the edits it made. If it finds no edit to make, it says so and prints no improved version.
| Argument | Type | Description |
|---|---|---|
| goal | string | Optional: what the content should achieve (for example 'book a first meeting' or 'educate readers'). If not given, a goal is chosen from the content type |
| content* | string | The content to review |
| audience | string | Optional: who the content is for. The review reports when the text never mentions them |
| your_sector | string | 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_type* | string | The kind of content; it changes which checks apply |
| tone_preference | string | The tone you want. Only more_formal and more_casual are checked in the text; any other value is named in the answer as not used |
Writes a first draft of a newsletter issue 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 subject line and preview, an opening, a short section for each key point, your own call to action as the button, A/B subject lines, alternative opening hooks and sector notes. Without key points it suggests some from the topic and sector. The draft uses only what you gave: it adds no statistic or customer story, and says what it did not get.
| Argument | Type | Description |
|---|---|---|
| tone | string | The writing tone |
| topic* | string | The main topic or theme of the newsletter |
| cta_goal* | string | The action readers should take, in your own words (for example 'register for the webinar', 'book a call', 'read the guide'); it becomes the button |
| key_points | string | Optional: key points to cover, one per line, per semicolon or comma-separated. If not provided, points are suggested from the topic and newsletter type |
| your_sector | string | 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. |
| your_product |
Builds a sales kit 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, a script for each objection answered with the sector's pattern and the proof point that fits it, competitor responses, discovery questions and follow-up templates. Without objections it suggests the ones your sector raises.
| Argument | Type | Description |
|---|---|---|
| product* | string | The product name and what it does |
| sales_stage | string | The stage of the sales funnel |
| value_props | string | Optional: key value propositions, one per line, per semicolon or comma-separated. Taken from the proof points if not provided |
| your_sector | string | 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. |
| proof_points* | string | Evidence for your claims: case studies, metrics and quotes, one per line, per semicolon or comma-separated |
| price_context | string | Optional: your pricing against the market (for example 'Premium, above market', 'Budget option' or 'Mid-market') |
Prepares a testimonial request 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.
| Argument | Type | Description |
|---|---|---|
| use_case | string | Where the testimonial will be used (the website or a sales deck, for example) |
| incentive | string | Optional: what you are offering in return |
| your_sector | string | 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. |
| your_product | string | Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
| customer_name* | string | The customer's name |
| customer_role | string | The customer's job title |
| success_story |
Writes a first draft of each article in a thought leadership series from your topic, your take and the reader you write for. Optional proof points, author background, number of articles and article style shape them. Returns, for each article, a headline, a short draft with the objection it answers, your proof and a way to test the idea, a promotional post for each article, a publishing order and sector notes. Your take and proof points are quoted as you wrote them and no result, customer or figure is invented. Without proof points it names the evidence to gather.
| Argument | Type | Description |
|---|---|---|
| topic* | string | The topic you want to build authority on |
| your_take* | string | Your own view on this topic: what you believe that others do not, or your contrarian view |
| your_sector | string | 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. |
| article_type | string | The style of the articles |
| num_articles | integer | How many articles to outline, a whole number from 1 to 5. If left out, the series has three articles |
| proof_points | string |
Writes a webinar run of show and a full spoken script 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 the run of show, the script with the speaker lines and on-screen cues for each segment built from your takeaways and speakers, polls with answer options, anticipated questions with answers, a follow-up email sequence and sector notes. Without key takeaways it suggests them from the topic and type. The script uses only what you gave and says what it did not get.
| Argument | Type | Description |
|---|---|---|
| topic* | string | The webinar topic or title |
| duration | string | The webinar length |
| speakers | string | Optional: speakers as you want them listed. Separate speakers with semicolons or line breaks ('Name, Title; Name, Title'), or with commas if each is one phrase |
| your_sector | string | 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_type* | string | The kind of webinar; sets the structure |
| your_product | string | Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
{
"type": "object",
"required": [
"source_content",
"source_type"
],
"properties": {
"brand_voice": {
"enum": [
"professional",
"casual",
"authoritative",
"friendly",
"bold"
],
"type": "string",
"description": "The brand voice to keep"
},
"key_message": {
"type": "string",
"description": "Optional: the core message to emphasize in every format"
},
"source_type": {
"enum": [
"blog_post",
"webinar_transcript",
"podcast_transcript",
"whitepaper",
"case_study",
"research_report",
"presentation"
],
"type": "string",
"description": "The kind of content the source is"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"source_content": {
"type": "string",
"description": "The original content to repurpose (a blog post, article or transcript, for example)"
},
"target_formats": {
"type": "string",
"description": "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. A name outside this list is reported, not written"
}
}
}{
"type": "object",
"required": [
"content",
"content_type"
],
"properties": {
"goal": {
"type": "string",
"description": "Optional: what the content should achieve (for example 'book a first meeting' or 'educate readers'). If not given, a goal is chosen from the content type"
},
"content": {
"type": "string",
"description": "The content to review"
},
"audience": {
"type": "string",
"description": "Optional: who the content is for. The review reports when the text never mentions them"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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_type": {
"enum": [
"blog_post",
"email",
"landing_page",
"social_post",
"sales_email",
"product_description",
"press_release",
"case_study"
],
"type": "string",
"description": "The kind of content; it changes which checks apply"
},
"tone_preference": {
"enum": [
"more_formal",
"more_casual",
"more_urgent",
"more_friendly",
"more_authoritative",
"keep_same"
],
"type": "string",
"description": "The tone you want. Only more_formal and more_casual are checked in the text; any other value is named in the answer as not used"
}
}
}| string |
| Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
| newsletter_type | string | The kind of newsletter |
| previous_topics | string | Optional: recent newsletter topics, to avoid repetition and suggest connections |
| audience_segment | string | Who the newsletter is for; sets tone and depth |
{
"type": "object",
"required": [
"topic",
"cta_goal"
],
"properties": {
"tone": {
"enum": [
"professional",
"conversational",
"authoritative",
"friendly",
"urgent"
],
"type": "string",
"description": "The writing tone"
},
"topic": {
"type": "string",
"description": "The main topic or theme of the newsletter"
},
"cta_goal": {
"type": "string",
"description": "The action readers should take, in your own words (for example 'register for the webinar', 'book a call', 'read the guide'); it becomes the button"
},
"key_points": {
"type": "string",
"description": "Optional: key points to cover, one per line, per semicolon or comma-separated. If not provided, points are suggested from the topic and newsletter type"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"your_product": {
"type": "string",
"description": "Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder."
},
"newsletter_type": {
"enum": [
"educational",
"product_update",
"industry_news",
"thought_leadership",
"curated_links"
],
"type": "string",
"description": "The kind of newsletter"
},
"previous_topics": {
"type": "string",
"description": "Optional: recent newsletter topics, to avoid repetition and suggest connections"
},
"audience_segment": {
"enum": [
"executives",
"practitioners",
"technical",
"general",
"prospects",
"customers"
],
"type": "string",
"description": "Who the newsletter is for; sets tone and depth"
}
}
}| business_model | string | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| target_persona* | string | Who sales is pitching to (role and company type) |
| common_objections | string | Optional: sales objections you hear, one per line, per semicolon or comma-separated. If not provided, likely objections for your sector are suggested |
| competitor_objections | string | Optional: 'why not [competitor]' objections |
{
"type": "object",
"required": [
"product",
"target_persona",
"proof_points"
],
"properties": {
"product": {
"type": "string",
"description": "The product name and what it does"
},
"sales_stage": {
"enum": [
"prospecting",
"discovery",
"demo",
"negotiation",
"closing"
],
"type": "string",
"description": "The stage of the sales funnel"
},
"value_props": {
"type": "string",
"description": "Optional: key value propositions, one per line, per semicolon or comma-separated. Taken from the proof points if not provided"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"proof_points": {
"type": "string",
"description": "Evidence for your claims: case studies, metrics and quotes, one per line, per semicolon or comma-separated"
},
"price_context": {
"type": "string",
"description": "Optional: your pricing against the market (for example 'Premium, above market', 'Budget option' or 'Mid-market')"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how."
},
"target_persona": {
"type": "string",
"description": "Who sales is pitching to (role and company type)"
},
"common_objections": {
"type": "string",
"description": "Optional: sales objections you hear, one per line, per semicolon or comma-separated. If not provided, likely objections for your sector are suggested"
},
"competitor_objections": {
"type": "string",
"description": "Optional: 'why not [competitor]' objections"
}
}
}| string |
| A short description of their success with your product |
| business_model | string | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| customer_company* | string | The customer's company |
| testimonial_type* | string | The kind of testimonial you need |
| relationship_context | string | How long they have been a customer and the key interactions |
{
"type": "object",
"required": [
"customer_name",
"customer_company",
"success_story",
"testimonial_type"
],
"properties": {
"use_case": {
"type": "string",
"description": "Where the testimonial will be used (the website or a sales deck, for example)"
},
"incentive": {
"type": "string",
"description": "Optional: what you are offering in return"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"your_product": {
"type": "string",
"description": "Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder."
},
"customer_name": {
"type": "string",
"description": "The customer's name"
},
"customer_role": {
"type": "string",
"description": "The customer's job title"
},
"success_story": {
"type": "string",
"description": "A short description of their success with your product"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how."
},
"customer_company": {
"type": "string",
"description": "The customer's company"
},
"testimonial_type": {
"enum": [
"written_quote",
"video_interview",
"case_study_interview",
"g2_review",
"reference_call"
],
"type": "string",
"description": "The kind of testimonial you need"
},
"relationship_context": {
"type": "string",
"description": "How long they have been a customer and the key interactions"
}
}
}| Optional: evidence supporting your take: personal stories, client examples, data or stats, one per line, per semicolon or comma-separated. If not provided, proof points to gather are suggested |
| target_reader* | string | Who should read this, named specifically (for example 'Heads of IT at companies with many branches' rather than 'managers') |
| author_background | string | Optional: your role and why you are credible (for example 'a long career in enterprise sales') |
{
"type": "object",
"required": [
"topic",
"your_take",
"target_reader"
],
"properties": {
"topic": {
"type": "string",
"description": "The topic you want to build authority on"
},
"your_take": {
"type": "string",
"description": "Your own view on this topic: what you believe that others do not, or your contrarian view"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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."
},
"article_type": {
"enum": [
"contrarian",
"how_to",
"lessons_learned",
"prediction",
"framework"
],
"type": "string",
"description": "The style of the articles"
},
"num_articles": {
"type": "integer",
"maximum": 5,
"minimum": 1,
"description": "How many articles to outline, a whole number from 1 to 5. If left out, the series has three articles"
},
"proof_points": {
"type": "string",
"description": "Optional: evidence supporting your take: personal stories, client examples, data or stats, one per line, per semicolon or comma-separated. If not provided, proof points to gather are suggested"
},
"target_reader": {
"type": "string",
"description": "Who should read this, named specifically (for example 'Heads of IT at companies with many branches' rather than 'managers')"
},
"author_background": {
"type": "string",
"description": "Optional: your role and why you are credible (for example 'a long career in enterprise sales')"
}
}
}| include_polls | boolean | Include poll suggestions with answer options |
| key_takeaways | string | Optional: what attendees should learn, one per line, per semicolon or comma-separated. If not provided, takeaways are suggested from the topic |
| business_model | string | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| target_audience* | string | Who will attend (for example 'Support leaders at consumer apps') |
| product_mention_level | string | Whether to add product tie-in placeholders to the script ('none' leaves them out) |
{
"type": "object",
"required": [
"topic",
"target_audience",
"webinar_type"
],
"properties": {
"topic": {
"type": "string",
"description": "The webinar topic or title"
},
"duration": {
"enum": [
"30_min",
"45_min",
"60_min",
"90_min"
],
"type": "string",
"description": "The webinar length"
},
"speakers": {
"type": "string",
"description": "Optional: speakers as you want them listed. Separate speakers with semicolons or line breaks ('Name, Title; Name, Title'), or with commas if each is one phrase"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "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_type": {
"enum": [
"educational",
"product_demo",
"panel_discussion",
"customer_story",
"workshop",
"ama"
],
"type": "string",
"description": "The kind of webinar; sets the structure"
},
"your_product": {
"type": "string",
"description": "Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder."
},
"include_polls": {
"type": "boolean",
"description": "Include poll suggestions with answer options"
},
"key_takeaways": {
"type": "string",
"description": "Optional: what attendees should learn, one per line, per semicolon or comma-separated. If not provided, takeaways are suggested from the topic"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how."
},
"target_audience": {
"type": "string",
"description": "Who will attend (for example 'Support leaders at consumer apps')"
},
"product_mention_level": {
"enum": [
"none",
"subtle",
"moderate",
"heavy"
],
"type": "string",
"description": "Whether to add product tie-in placeholders to the script ('none' leaves them out)"
}
}
}