Craft Content MCP Server

@shashwatgtmalpha/craft-content-mcp v2.2.15

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. It needs no sign-in and always runs the newest version (2.2.15). 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.

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

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

Generated on 27 September 2026 from the server's own tool list and checked again on 30 September 2026 against tools/list of craft-content-mcp 2.2.15 (the same code as the hosted MCP address), so every tool name, title, description and input below is exactly what the server accepts. Every tool is read-only.

Inputs of each tool

1. Case Study Generator (case_study_generator)

2. Newsletter Builder (newsletter_builder)

3. Webinar Script (webinar_script)

4. Content Repurposer (content_repurposer)

5. Thought Leadership Series (thought_leadership_series)

6. Testimonial Capture (testimonial_capture)

7. Sales Enablement Content (sales_enablement_content)

8. CRAFT Content Improver (craft_content_improver)

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. Nothing is stored: no database, no files, no cache, no logging of inputs or outputs by our code.
• 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