MCP.Market

Craft Content MCP server

online · 100% uptime
by shashwatgtm·io.github.shashwatgtm/craft-content-mcp·v2.2.22
No reviews yet

CRAFT Content: 8 B2B content tools by Helix GTM Consulting

A92/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A92/100

not scanned yet

Adoption
Growing

0 stars124 downloads/wk

Reviews

Write one

Nobody has reviewed Craft Content yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Craft Content tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Craft Content compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
2,018 ms
faster than 5% of 30,031 servers
Downloads a week
124
more than 67% of 12,191 servers with a package

Release history: 2 versions in the registry since 2026-01-16, latest 2026-10-17, typically one every 274 days.

Install Craft Content in Claude Code, Cursor or VS Code

claude mcp add --transport http craft-content-mcp https://craft-content.gtmhelix.com/mcp
Add to Cursor

What the publisher says

From the Craft Content repository's README, as published. We do not edit it. Read it on GitHub

@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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Craft Content: common questions

Is Craft Content MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Craft Content safety report
How do I install Craft Content?
It runs remotely at craft-content.gtmhelix.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Craft Content need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Craft Content maintained?
The last commit was 34 days ago (2026-09-30). The latest release is v2.2.22.
Is Craft Content up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Craft Content compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 2,018 ms (faster than 5% of 30,031 servers). Full comparison.

More from shashwatgtm →