You'd reach for this when you're automating content publishing workflows and need to chain together the typical steps: finding and optimizing images, inserting affiliate links, handling SEO metadata, and pushing everything to your CMS. It's built for the full pipeline from draft to published post. The stdio transport means it runs as a local process you can pipe content through. Useful if you're building editorial automation tools or managing high volume content sites where manually handling images, SEO tags, and affiliate tracking across dozens of posts becomes a bottleneck. Think of it as plumbing for content operations rather than a one-off publishing helper.
CONTENTFORGE_CMS_URL*URL of your CMS API endpoint
CONTENTFORGE_CMS_KEY*secretAPI key for your CMS
CONTENTFORGE_PEXELS_KEYsecretPexels API key for image sourcing
CONTENTFORGE_AMAZON_TAGAmazon Associates affiliate tag
explorium-ai/vibeprospecting-mcp
io.github.compuute/lead-enrichment
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper
io.github.br0ski777/company-enrichment
com.mcparmory/apollo
mambalabsdev/mcp-gtm-tech-stack-signal-scraper