← ClaudeAtlas

cf-add-integrationlisted

Connect any external API or service to ContentForge as a custom MCP connector — walks non-technical users from finding a verified MCP package or HTTP endpoint to a ready-to-paste .mcp.json entry, credential setup instructions, and a post-restart verification check. Triggers on "/contentforge:cf-add-integration", "connect our internal CMS", "add a custom integration", "hook up Google Analytics to ContentForge", "there is no connector for this service". Reads .mcp.json.connectors-reference for verified endpoints and checks the registry via scripts/connector-status.py first; for connectors already in the registry, /contentforge:cf-connect is the shorter path. Configuration guidance only — never asks for secrets in chat and does not call the connected service itself.
teachskillofskills-ai/ContentForge-techshu · ★ 1 · API & Backend · score 78
Install: claude install-skill teachskillofskills-ai/ContentForge-techshu
# /contentforge:cf-add-integration ## Purpose Help users connect any external API, tool, or service to ContentForge as an MCP connector. Walk through the entire process conversationally — from finding the right MCP package to testing the connection — without requiring technical MCP knowledge. ## Input Required The user provides (or will be asked): - **What they want to connect**: The service name and what they want it to do — e.g., "Google Analytics to track content performance", "Ahrefs for keyword research", "our internal CMS to publish directly" - **Credentials**: API keys, tokens, or OAuth setup they have (or will need to obtain). The system will guide them on exactly what's needed. **Never ask users to paste secrets into the conversation.** ## Process ### Step 1: Understand what the user wants Ask the user what service they want to connect and what they want it to do within ContentForge. Map their intent to content workflow stages: | Workflow Stage | Example Integrations | |---------------|---------------------| | Research (Phase 1) | Ahrefs, Similarweb, Google Search Console | | Publishing (Phase 8) | Webflow, WordPress, HubSpot CMS | | Collaboration | Notion, Slack, Google Drive | | Tracking | Google Sheets, Google Analytics | | Translation | DeepL, Sarvam AI | | Social distribution | Twitter/X, LinkedIn, Instagram | ### Step 2: Check if a connector already exists Run `python scripts/connector-status.py --action check <name>` to see if the connector is alrea