Contentforge
Run an agent-driven content pipeline: source images (Pexels), tune SEO, attach Amazon affiliate links, and publish to your CMS API.
Overview
io.github.gentry-ai-bot/contentforge is a Launch-phase MCP server that automates image sourcing, SEO steps, affiliate links, and CMS publishing for content sites.
What is this MCP server?
- End-to-end content pipeline MCP: image sourcing, SEO, affiliate links, CMS publish
- Required env: CONTENTFORGE_CMS_URL and CONTENTFORGE_CMS_KEY
- Optional Pexels (CONTENTFORGE_PEXELS_KEY) and Amazon Associates tag (CONTENTFORGE_AMAZON_TAG)
- npm contentforge-mcp stdio (package row 0.2.1; server metadata 1.0.0)
- Repository gentry-ai-bot/contentforge for CMS-centric blogs and affiliate sites
- Server description version 1.0.0; npm package contentforge-mcp listed at 0.2.1
- Four documented environment variables (2 required CMS, 2 optional Pexels/Amazon)
- Transport stdio via npm registry
What problem does it solve?
Publishing SEO content with images and affiliate links means repeating CMS, Pexels, and Amazon wiring every time your agent writes a post.
Who is it for?
Indie site owners and affiliate bloggers who already have a CMS API and want agent-assisted production at scale.
Skip if: Builders without a CMS endpoint, strict regulated niches without human review, or teams avoiding Amazon affiliate monetization.
What do I get? / Deliverables
One MCP install lets your agent source assets, optimize posts, tag affiliates, and publish to your CMS API in a single workflow.
- Agent tools for image sourcing, SEO-oriented content steps, and CMS publish
- Affiliate-tagged output when CONTENTFORGE_AMAZON_TAG is set
- Repeatable launch-ready posting workflow from the IDE
Recommended MCP Servers
Journey fit
Launch/SEO is the canonical shelf because the server’s stated jobs—SEO, publishing, monetized links—map to getting pages live and discoverable. SEO subphase reflects on-page optimization and publishing hooks rather than pure frontend component work.
How it compares
CMS-focused content pipeline MCP, not a standalone keyword research-only skill.
Common Questions / FAQ
Who is contentforge for?
Solo builders using MCP agents to produce and publish SEO-oriented articles with optional Pexels images and Amazon affiliate tags.
When should I use contentforge?
At Launch and into Grow when you need repeatable publish flows—SEO, images, affiliates, CMS—not ad-hoc one-off markdown files.
How do I add contentforge to my agent?
Add stdio server contentforge-mcp from npm, set CONTENTFORGE_CMS_URL and CONTENTFORGE_CMS_KEY, optionally Pexels and Amazon tag env vars, then restart MCP.