Skip to main content
Glama
CRAFT Content MCP Server

CRAFT Content MCP Server

@shashwatgtmalpha/craft-content-mcp v2.2.25

By Helix GTM Consulting (https://gtmhelix.com), built by Shashwat Ghosh, Co-Founder and Fractional CMO.

CRAFT Content Framework MCP Server: a complete redesign with user-centric inputs, actual content analysis, and a structured draft with placeholders for each output.

Use it hosted (no install)

Add https://craft-content.gtmhelix.com/mcp to Claude or ChatGPT as a custom connector, or to Codex or Gemini CLI as an MCP server. It needs no sign-in and always runs the newest version (2.2.25). The same tools run as a free web app with a form per tool at https://craft-content.gtmhelix.com/, and the setup steps are at https://craft-content.gtmhelix.com/connect/.

The npm package below is an older version (2.0.1 on npm on 27 September 2026) until the next npm release. Use it only if you need a local stdio server.

Related MCP server: my-mcp

Design Philosophy

Every tool was redesigned using chain of thought from the user's perspective:

  1. What does the user actually want? (Not what looks impressive in a demo)

  2. What do they already know? (Keep inputs simple: don't ask for things they need to figure out)

  3. Does the output save them work? (A structured draft with placeholders, not a blank template)

What's New in v2.0.0

Tool

Before

After

thought_leadership_series

200-300 word posts with [Expand] placeholders

Byline article drafts of about 600 to 800 words, with placeholders to complete before publishing

craft_content_improver

Blank scorecard output

Actually analyzes content, scores dimensions, generates improved version

case_study_generator

Requires full story

Discovery mode: generates interview questions if you don't have the story

sales_enablement_content

Generic pitches

Objection-mapped handlers with your proof points

newsletter_builder

Good

Enhanced with A/B subject lines, 4 hooks, segment targeting

webinar_script

Good

Type-specific structures (demo vs educational vs panel)

content_repurposer

Excellent

Kept: transforms to 10 formats

testimonial_capture

Excellent

Kept: request emails, interview guides

Installation

npm install -g @shashwatgtmalpha/craft-content-mcp

Or add to Claude Desktop config:

{
  "mcpServers": {
    "craft-content": {
      "command": "npx",
      "args": ["-y", "@shashwatgtmalpha/craft-content-mcp"]
    }
  }
}

Tools and inputs

Tool names and input formats were checked against tools/list of craft-content-mcp 2.2.25 on 17 November 2026. Query tools/list for current descriptions.

#

Tool

Title

What it does

1

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.

2

newsletter_builder

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.

3

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.

4

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.

5

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.

6

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.

7

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.

8

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.

Inputs of each tool

1. Case Study Generator (case_study_generator)

Input

Required

Type

Description

customer_name

Yes

string

Customer/company name

your_product

Yes

string

Your product/service name

customer_industry

No

string

Customer's industry for context

mode

No

one of: full, discovery

full = generate case study (requires challenge/solution/results), discovery = generate interview questions to gather story

interview_notes

No

string

Optional: Raw interview notes or transcript. Parsed into a case study when mode is 'full'

challenge

No

string

The customer's challenge/problem (required for full mode)

solution

No

string

How your product solved it (required for full mode)

results

No

string

Quantifiable outcomes (required for full mode)

customer_quote

No

string

Optional: Direct quote from customer

your_sector

No

one of: 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.

2. Newsletter Builder (newsletter_builder)

Input

Required

Type

Description

topic

Yes

string

Main topic/theme of the newsletter

cta_goal

Yes

string

What action should readers take? (e.g., 'sign up for webinar', 'try feature', 'read blog')

key_points

No

string

OPTIONAL: Key points to cover (comma-separated). If not provided, the tool suggests 5 points based on the topic and newsletter type

audience_segment

No

one of: executives, practitioners, technical, general, prospects, customers

Audience segment affects tone and depth

newsletter_type

No

one of: educational, product_update, industry_news, thought_leadership, curated_links

Type of newsletter

tone

No

one of: professional, conversational, authoritative, friendly, urgent

Writing tone

previous_topics

No

string

Optional: Recent newsletter topics to avoid repetition and suggest connections

your_sector

No

one of: 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.

3. Webinar Script (webinar_script)

Input

Required

Type

Description

topic

Yes

string

Webinar topic/title

target_audience

Yes

string

Who will attend (e.g., 'Marketing managers at B2B SaaS companies')

webinar_type

Yes

one of: educational, product_demo, panel_discussion, customer_story, workshop, ama

Type of webinar determines structure

duration

No

one of: 30_min, 45_min, 60_min, 90_min

Webinar length

key_takeaways

No

string

OPTIONAL: 3-5 things attendees should learn (comma-separated). If not provided, we'll suggest based on topic

speakers

No

string

Optional: Speaker names and titles (comma-separated)

include_polls

No

boolean

Include interactive poll suggestions

product_mention_level

No

one of: none, subtle, moderate, heavy

Whether to add product tie-in placeholders to the script ('none' leaves them out)

your_sector

No

one of: 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.

4. Content Repurposer (content_repurposer)

Input

Required

Type

Description

source_content

Yes

string

Original content to repurpose (blog post, article, transcript, etc.)

source_type

Yes

one of: blog_post, webinar_transcript, podcast_transcript, whitepaper, case_study, research_report, presentation

What type of content is the source

target_formats

No

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

brand_voice

No

one of: professional, casual, authoritative, friendly, bold

Brand voice to maintain

key_message

No

string

Optional: Core message to emphasize across all formats

your_sector

No

one of: 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.

5. Thought Leadership Series (thought_leadership_series)

Input

Required

Type

Description

topic

Yes

string

The topic you want to establish authority on

your_take

Yes

string

Your unique perspective or opinion on this topic. What do you believe that others don't? What's your contrarian view?

target_reader

Yes

string

Who should read this? Be specific (e.g., 'B2B SaaS founders struggling with churn' not just 'marketers')

proof_points

No

string

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

No

string

Optional: Your role and why you're credible (e.g., '15 years in enterprise sales')

num_articles

No

integer (1 to 5)

How many articles to outline, a whole number from 1 to 5. If left out, the series has three articles

article_type

No

one of: contrarian, how_to, lessons_learned, prediction, framework

Style of articles

your_sector

No

one of: 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.

6. Testimonial Capture (testimonial_capture)

Input

Required

Type

Description

customer_name

Yes

string

Customer name

customer_company

Yes

string

Customer's company

success_story

Yes

string

Brief description of their success with your product

testimonial_type

Yes

one of: written_quote, video_interview, case_study_interview, g2_review, reference_call

Type of testimonial needed

customer_role

No

string

Customer's job title

relationship_context

No

string

How long they've been a customer, key interactions

use_case

No

string

Where will this testimonial be used? (website, sales deck, etc.)

incentive

No

string

Optional: What you're offering in return

your_sector

No

one of: 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.

7. Sales Enablement Content (sales_enablement_content)

Input

Required

Type

Description

product

Yes

string

Product name and what it does

target_persona

Yes

string

Who sales is pitching to (role, company type)

proof_points

Yes

string

Evidence for claims: case studies, metrics, quotes (comma-separated)

common_objections

No

string

OPTIONAL: Sales objections you hear (comma-separated). If not provided, we'll suggest likely objections for your product type

value_props

No

string

OPTIONAL: Key value propositions (comma-separated). Will be DERIVED from proof points if not provided

competitor_objections

No

string

Optional: 'Why not [competitor]' objections

price_context

No

string

Optional: Your pricing vs market (e.g., 'Premium, 20% above market', 'Budget option', 'Mid-market')

sales_stage

No

one of: prospecting, discovery, demo, negotiation, closing

What stage of sales funnel

your_sector

No

one of: 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.

8. CRAFT Content Improver (craft_content_improver)

Input

Required

Type

Description

content

Yes

string

Content to analyze

content_type

Yes

one of: blog_post, email, landing_page, social_post, sales_email, product_description, press_release, case_study

Type of content affects evaluation criteria

goal

No

string

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

No

string

OPTIONAL: Who is this content for? Helps tailor improvements.

tone_preference

No

one of: 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

No

one of: 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.

Input Design Principles

  1. Only ask for what users actually know: don't require "value propositions" if they're calling because they haven't articulated them yet

  2. Make required inputs minimal: 3 to 4 required, the rest optional with smart defaults

  3. Use natural language: "your_take" not "contrarian_perspective_thesis"

  4. Derive what you can: if the user gives a topic, auto-generate related elements

Output Design Principles

  1. A structured draft with placeholders: each tool returns a structured draft to edit, with placeholders where your inputs gave no fact

  2. Right length for the format: bylines 600 to 800 words, social posts 200 to 300 words

  3. Include metadata: word counts, posting times, headlines

  4. Add promotional content: social snippets to promote longer content

Author

Shashwat Ghosh, Co-Founder and Fractional CMO, Helix GTM Consulting, with 24+ years in B2B and 10+ years of fractional experience

License

MIT

Hosted connector (Streamable HTTP)

The same tools are also available as a hosted MCP server, so they work in Claude on the web, desktop and mobile without installing anything.

  • Server URL: https://craft-content.gtmhelix.com/mcp

  • Transport: Streamable HTTP (stateless, JSON responses). Authentication: none.

  • Setup guide: https://craft-content.gtmhelix.com/connect/

  • In Claude: Customize, then Connectors, then Add custom connector, and paste the server URL.

  • In Claude Code: claude mcp add --transport http craft-content https://craft-content.gtmhelix.com/mcp

The npm package (stdio) and the hosted server run the same createServer() code in src/server.ts.

Privacy Policy

Full policy: https://craft-content.gtmhelix.com/privacy/ (also in PRIVACY.md).

  • Data collection: the hosted server receives only the tool name and the inputs of each tool call. The npm package runs on your computer and sends nothing to us.

  • Use and storage: inputs are used only to build that call's reply. Inputs and answers are not stored: no database, no files, no cache, no logging of inputs or outputs by our code. Each call adds one anonymous usage record (date and time, site and tool name, app kind, web form or assistant); see the privacy page.

  • Third-party sharing: none by us. Netlify hosts the server and processes requests under its own policy (https://www.netlify.com/privacy/). Fonts are served from this site, so loading a page contacts no one else.

  • Retention: we keep no tool inputs or outputs. Netlify keeps its own platform logs under its policy.

  • Contact: shashwat@gtmhelix.com

Turn this customer result into content

The new customer_result_to_content tool lives in chat. The assistant collects an exact result sentence with its qualifier and source label, a source and date, the writer's role, approval for each use, the writer's own view and a reader action. The server builds a proof card, chains the existing case study, repurposer and newsletter functions, and checks each final first draft. It makes no network requests and stores no brief.

For the vendor or their own customer, written approval must name the approver, date and each use, with a future review date. A public page does not grant new uses. Missing approval or the writer's view returns the card and questions without drafts. An already published story is used as source and is not rebuilt. Unknown proof fields stay marked as not stated. A sentence check does not establish meaning or independent verification.

The derived results view is at ui://helix/results/chains/v1.html. It reuses the shared results view's host bridge and copy control, adds display parts for the proof card, checks, handoffs and first drafts, and sends next actions back to chat. The original byte-pinned results resource is unchanged. Text-only hosts receive the full same answer. The tool page is /tools/customer-result-to-content/ and has no form.

If a public source has no visible publication date, set source_date to not stated and keep the retrieval date in source_checked_date. The card keeps that gap visible. A retrieval date must not stand in for a publication or measurement date. To regenerate the additive offline results view, run python scripts/build-chain-view.py, then build. Font licences are included beside the bundled fonts.

Available Tools

9 tools
case_study_generatorCase Study GeneratorA
Read-only
Inspect

Helps you decide how to present a customer result as 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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of testimonial_capture when you need a full challenge, solution and results story. Ask whether written customer approval covers the exact material and intended use.

Inputs: your_product (required), customer_name (required), mode, results, +8 more.

content_repurposerContent RepurposerA
Read-only
Inspect

Helps you decide how to reuse 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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of thought_leadership_series when you already have source copy to adapt into other formats. Ask whether written customer approval covers the exact material and intended use.

Inputs: source_type (required), source_content (required), brand_voice, key_message, +3 more.

craft_content_improverCRAFT Content ImproverA
Read-only
Inspect

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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of content_repurposer when you need to review and edit an existing draft for quality.

Inputs: content (required), content_type (required), goal, audience, +2 more.

customer_result_to_contentTurn this customer result into contentA
Read-only
Inspect

Helps you decide how to turn a customer result into a case study, a post and a newsletter while preserving its exact sentence. Needs the exact result sentence with its qualifier and source label, source and date, your role, approval, your own view and a reader action. Returns a proof card, first drafts and a sentence check. Optional proof details expose gaps. Written approval is required for your own customer; without it, returns the card and questions only. Chat collects the facts; the results view shows them. No form. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing or invalid brief fields return field-specific errors. Missing written approval for your own customer returns the proof card and questions only. Use this instead of case_study_generator when you need a proof card and several drafts preserving one exact result sentence.

Inputs: product (required), approval (required), as_of_date (required), buyer_role (required), +17 more.

newsletter_builderNewsletter BuilderA
Read-only
Inspect

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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of thought_leadership_series when you need one newsletter issue with a reader action. Ask whether written customer approval covers the exact material and intended use.

Inputs: topic (required), cta_goal (required), tone, key_points, +6 more.

sales_enablement_contentSales Enablement ContentA
Read-only
Inspect

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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of email_sequence_generator when you need seller messaging, objection responses and discovery prompts.

Inputs: product (required), proof_points (required), target_persona (required), sales_stage, +6 more.

testimonial_captureTestimonial CaptureA
Read-only
Inspect

Helps you decide how to 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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of case_study_generator when you need a testimonial request, interview questions and quote approval. Ask whether written customer approval covers the exact material and intended use.

Inputs: customer_name (required), success_story (required), customer_company (required), testimonial_type (required), +9 more.

thought_leadership_seriesThought Leadership SeriesA
Read-only
Inspect

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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of newsletter_builder when you need a sequence of articles developing a supplied point of view. Ask whether written customer approval covers the exact material and intended use.

Inputs: topic (required), your_take (required), target_reader (required), your_sector, +5 more.

webinar_scriptWebinar ScriptA
Read-only
Inspect

Helps you decide how to 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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of thought_leadership_series when you need a live session script, polls and follow-up emails. Ask whether written customer approval covers the exact material and intended use.

Inputs: topic (required), webinar_type (required), target_audience (required), duration, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct content format (case study, newsletter, webinar script, repurposing, article series, testimonial request, sales enablement, draft review, proof card), and descriptions explicitly route between them with 'Use this instead of X when...' guidance. The only real friction is the three-way overlap among case_study_generator, customer_result_to_content and testimonial_capture, which all touch customer proof and depend on the routing sentences to be told apart.

    Naming Consistency4/5

    All names are snake_case and overwhelmingly follow a noun-object pattern (case_study_generator, newsletter_builder, testimonial_capture, content_repurposer). Minor deviations exist: craft_content_improver carries a brand prefix that no other tool has, and customer_result_to_content uses a prepositional phrase rather than the noun+agent pattern.

    Tool Count5/5

    Nine tools sit comfortably in the well-scoped 3-15 range, and each maps to a genuinely different deliverable rather than a variation on the same output. No tool appears redundant padding.

    Completeness3/5

    The surface covers most marketing deliverables, but sales_enablement_content points to an email_sequence_generator that is not in the tool set, leaving a referenced-but-missing operation. There is also no standalone email nurture/sequence or long-form blog tool, only email copy embedded in other outputs and a blog summary via content_repurposer.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      An MCP server framework featuring dynamic tool loading and a modular one-tool-per-file architecture for rapid development. It supports both Stdio and HTTP transport modes, offering automated test generation and centralized configuration management.
      11
      -