cf-connect

# /contentforge:cf-connect — Guided Connector Setup Set up a specific MCP integration for ContentForge with step-by-step instructions tailored to the connector's transport type. Handles HTTP connectors (OAuth-based), npx connectors (API keys, environment variables, `.mcp.json` entry), unknown connector names (fuzzy matching), and post-setup verification. ## The ground truth about connectors ContentForge ships with an **empty `.mcp.json`** (`"mcpServers": {}`). This is deliberate (v3.9.0 Cowork-safety decision): no connector auto-connects when the plugin is installed. **Every connector is opt-in** — the user adds it to `.mcp.json` (or connects it at the platform level in Cowork/Desktop Settings → Integrations). Never claim a connector is pre-wired or already connected. All status claims must come from running `python scripts/connector-status.py` — never from this file or from memory. ## When to Use Use `/contentforge:cf-connect <name>` when: - You want to connect a specific service (e.g., `/contentforge:cf-connect wordpress`) - A skill told you a connector is missing and suggested using this command - You're setting up a new ContentForge installation and configuring integrations - You need the exact environment variables and `.mcp.json` entry for an npx connector - You want to verify an existing connector is working correctly ## What This Command Does 1. **Look Up Connector** — Find the connector in the registry, handle typos and close matches 2. **Check Current Status...