cf-integrations

Renders a dashboard of configured versus available MCP connectors grouped by category.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/teachskillofskills-ai/ContentForge-techshu --skill cf-integrations-teachskillofskills-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-integrations
Source: https://github.com/teachskillofskills-ai/ContentForge-techshu/tree/main/skills/cf-integrations
Command: npx skills add https://github.com/teachskillofskills-ai/ContentForge-techshu --skill cf-integrations-teachskillofskills-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? ContentForge ships with an empty .mcp.json, so users cannot tell which MCP connectors are configured, which are available, or which ones to set up next. This Skill reads the live connector status and presents it as a category-grouped dashboard with coverage totals and quick-win recommendations. ## Core Features & Use Cases - Live Status Dashboard: Runs scripts/connector-status.py to check .mcp.json and environment variables, then renders configured versus available connectors grouped by category. - Coverage and Quick Wins: Reports exact summary totals from the script and highlights the top 3 not-yet-configured connectors by workflow impact, each with a setup route. - Troubleshooting Guidance: Explains common issues such as registry name mismatches in .mcp.json, missing environment variables for npx connectors, and why a fresh install shows zero connections. - Use Case: After installing ContentForge, run the dashboard to confirm nothing is pre-wired, see that Notion and Google Sheets are the highest-impact connectors to add, and follow the pointer to /contentforge:cf-connect for guided setup. ## Quick Start Ask the assistant to show the ContentForge integration status dashboard so it runs the connector status script and lists which connectors are connected and which to set up next.

Frequently Asked Questions about cf-integrations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which MCP connectors are configured in ContentForge?

Run the cf-integrations command, which executes scripts/connector-status.py to scan .mcp.json and environment variables. It renders a category-grouped dashboard marking each connector as connected or available, plus summary coverage totals.

Why does a fresh ContentForge install show zero connectors connected?

ContentForge ships with an empty .mcp.json by design, so zero configured connectors is the expected state. Connectors are opt-in; use the cf-connect command to add your first one.

Does the integration dashboard make network calls to check connectors?

No. The status script reads only the local .mcp.json file and environment variables. It reports configuration status without contacting any external service, so it works offline.

Why does an HTTP connector still show as available after I added it to .mcp.json?

The key name in .mcp.json must exactly match the registry name, such as lowercase notion. Confirm the file contains valid JSON with a mcpServers object and restart the session after editing.

Can npx connectors like WordPress work in Cowork?

No. npx connectors require local Node.js and work in Claude Code only. HTTP connectors work in both Cowork and Claude Code once added to .mcp.json or connected through Cowork integration settings.