What problem does it solve? Configuring MCP connectors for ContentForge is error-prone: users guess endpoint URLs, miss required environment variables, or assume connectors are pre-wired when the plugin ships with an empty .mcp.json. This skill walks you through setting up a specific connector with transport-specific instructions and post-setup verification. ## Core Features & Use Cases - Transport-aware setup guidance: HTTP connectors get verified endpoint URLs and OAuth flow instructions; npx connectors get required env vars and a ready-to-paste .mcp.json entry. - Status from scripts, never memory: All connection status comes from running scripts/connector-status.py, with fuzzy name matching (e.g., wp → wordpress, gsheets → google-sheets). - Credential and verification support: Explains where to obtain API keys or application passwords, checks which env vars are set vs missing, and confirms configuration after setup. - Use Case: A user wants to publish articles to WordPress. Running the skill for wordpress returns the npm package to verify, the WORDPRESS_SITE_URL and WORDPRESS_AUTH_TOKEN variables to export, the exact .mcp.json block to paste, and a reminder to restart Claude Code. ## Quick Start Ask the assistant to set up the WordPress connector for ContentForge and follow the step-by-step instructions it returns.