kontent-ai-automation
Automate Kontent AI tasks via Rube MCP (Composio). Always search tools first for current schemas.
Author
Category
Development ToolsInstall
Hot:21
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-kontent-ai-automation&locale=en&source=copy
Kontent AI Automation Guide
Skill Overview
Kontent AI Automation uses the Rube MCP and the Composio toolkit to automate various operations of the Kontent.ai content management platform without writing code—from content retrieval to batch workflow processing.
Use Cases
Core Features
RUBE_SEARCH_TOOLS to fetch the latest Kontent AI tool architecture and input parameters in real time, avoiding outdated errors caused by hard-coding RUBE_MANAGE_CONNECTIONS to verify and manage the Kontent AI connection, ensuring the connection is in an ACTIVE state before workflow execution RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH FAQs
What is Rube MCP? How do I connect to Kontent AI?
Rube MCP is a Model Context Protocol service. Simply add the
https://rube.app/mcp endpoint in your client configuration to use it. After connecting, use RUBE_MANAGE_CONNECTIONS to specify the kontent_ai toolkit to complete the authorization connection to Kontent.ai—no API keys are required.Why do I need to search for tools before running a workflow each time?
The tool architecture for Kontent AI may change as the platform is updated. Hard-coding tool names or parameters can cause workflow failures. By using
RUBE_SEARCH_TOOLS to retrieve the latest architecture in real time, you ensure operations remain compatible with the current platform version—this is a key guarantee of automation reliability.What prerequisites are required to use Kontent AI Automation?
There are three requirements: the Rube MCP service must be connected and verifiable via
RUBE_SEARCH_TOOLS; the Kontent AI connection established through RUBE_MANAGE_CONNECTIONS must be in an ACTIVE state; and all parameters must be formatted precisely according to the architecture returned by the tool search. These checks can be performed automatically when the workflow starts.