Kontent AI Automation

What This Skill Does

This skill automates Kontent AI operations using Composio's Kontent AI toolkit through Rube MCP. It's designed for users who need to manage their Kontent AI content and integrate it with other systems. The skill requires an active Kontent AI connection and familiarity with Rube MCP.

When to Use

• Discover available Kontent AI tools.
• Check the status of the Kontent AI connection.
• Execute specific Kontent AI tools.
• Automate content creation.
• Manage Kontent AI content items.
• Integrate Kontent AI with other services.

Key Features

• Uses Rube MCP to automate Kontent AI operations.
• Requires an active Kontent AI connection.
• Relies on RUBE_SEARCH_TOOLS for tool discovery.
• Provides a core workflow pattern for execution.
• Offers documentation for the Kontent AI toolkit.
• Emphasizes the importance of schema compliance.

Manual Installation

Kontent AI Automation via Rube MCP

Automate Kontent AI operations through Composio's Kontent AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/kontent_ai

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Kontent AI connection via RUBE_MANAGE_CONNECTIONS with toolkit kontent_ai Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit kontent_ai If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Kontent AI operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Kontent AI task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["kontent_ai"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference