cf-connectlisted

# 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, zero config), npx connectors (API keys, environment variables, `.mcp.json` entry), unknown connector names (fuzzy matching), and post-setup verification. ## Context efficiency Pipeline phase. **Grep before Read** for `references/`, `humanization-patterns.json`, brand voice profiles. Pass earlier-phase outputs by path + line range, not by reloading. On `/contentforge:resume`, load only the failed phase's state. ## When to Use Use `/contentforge:connect <name>` when: - You want to connect a specific service (e.g., `/contentforge: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** — Determine if already connected or needs setup 3. **Present Setup Instructions** — Tailored to transport type (HTTP vs npx) 4. **Guide Credential Acquisition** — Where to get API keys, which permissions to set 5. **Provide .mcp.json Entry** — Ready-to-paste configuration for npx connectors 6. **