contentforge

Process multiple content pieces through a prioritized, checkpointed queue with progress tracking and per-piece quality gates

Add a custom MCP connector — connect any API or service to ContentForge via .mcp.json configuration.

Track content quality scores, pipeline timing, and compliance trends with insights and alerts.

Audit content library for freshness decay, coverage gaps, and optimization opportunities.

Generate research-backed content briefs with keywords, competitors, intent, and SEO strategy from a topic.

Plan content calendars with scheduling, deadlines, team assignments, and Google Calendar sync.

Set up an MCP connector with step-by-step instructions. Use to connect Notion, Canva, Webflow, etc.

Show the ContentForge user guide, available skills, pipeline overview, examples, and troubleshooting

Show active and available MCP connectors with workflow impact. Integration status dashboard.

Publish finished content to Webflow or WordPress via MCP connectors with preview, verification, and HTML export fallback

Repurpose finished articles into platform-specific social media posts for LinkedIn, Twitter/X, Instagram, Facebook, and Threads

Import brand voice profiles from documents or URLs. Use when setting up or updating a brand.

Switch tracking backend (local/airtable/google) with optional data migration

Create custom content type templates beyond the 5 built-in types with structure and quality standards.

Translate content into 15+ languages preserving brand voice, citations, and SEO. Three localization levels.

Generate scored A/B test variations of headlines, hooks, CTAs, and intros ranked by optimization goal.

Produce video scripts with hooks, scenes, and B-roll for YouTube, TikTok, Reels, and explainers.

Refresh existing content with updated data, sources, and SEO while preserving rankings and brand compliance.

Produce publication-ready, fact-checked, brand-aligned content via 10-phase autonomous pipeline. Use for any content need.

One-shot setup that wires ContentForge for team usage in Anthropic Cowork. Verifies Cowork environment, checks for a Google Drive integration, creates the canonical Drive folder layout, and confirms the team-ready output routing. Use this the first time a Cowork user installs ContentForge OR when files aren't landing in Drive.

Detect the runtime environment (Cowork sandbox vs local Claude Code) and report which ContentForge capabilities work in it. Use this when the user asks 'will this work in Cowork', sees unexpected file-path behavior, or wants a capability matrix before running a long pipeline.