contentful-graphql-automation

Contentful GraphQL Automation Skill

Skill Overview

Automatically perform Contentful GraphQL operations through Rube MCP (Composio), without needing an API key, enabling tool discovery, connection management, and multi-tool coordinated workflows.

Use Cases

Content Workflow Automation

For scenarios that require regularly creating, updating, or publishing Contentful content—such as content migrations, bulk metadata updates, or scheduled publishing processes. With RUBE_MULTI_EXECUTE_TOOL, multiple operations can be chained within a single session, significantly improving efficiency.

AI Skill Integration

When adding Contentful data operation capabilities to Claude skills or AI agents, this skill helps quickly complete tool discovery and invocation wrappers, avoiding direct handling of GraphQL query syntax and authentication logic.

Dynamic Schema Environments

When the model structure of the Contentful environment changes frequently, this skill’s mandatory tool discovery process ensures that the latest schema is retrieved before each execution, preventing call failures caused by hardcoding.

Core Features

Dynamic Tool Discovery

Use RUBE_SEARCH_TOOLS to fetch the current list of available Contentful tools, input schemas, and recommended execution plans in real time. This resolves issues where hardcoded calls fail due to tool schema changes. The results include the tool slug, parameter schema, and known pitfalls.

Connection Status Management

Use RUBE_MANAGE_CONNECTIONS to validate and manage Contentful GraphQL connection status. It supports checking whether the connection is active, retrieving the authentication link, and confirming connection availability—ensuring that everything is ready before tool execution.

Multi-Tool Coordinated Execution

RUBE_MULTI_EXECUTE_TOOL supports executing multiple tools within a single session, automatically handling session ID reuse and memory parameter passing. Combined with RUBE_REMOTE_WORKBENCH, it enables more complex batch operations and custom workflows.

Common Questions

Does Rube MCP require an API key?

No. Just add https://rube.app/mcp as the MCP server endpoint in the client configuration. When connecting to Contentful GraphQL, complete authorization using the authentication link returned by RUBE_MANAGE_CONNECTIONS—no manual API key management is needed.

Why do I have to call RUBE_SEARCH_TOOLS before each execution?

Composio’s tool architecture changes as the Contentful platform updates. Hardcoding tool slugs and parameters can easily cause failures. Forcing tool search ensures each run uses the latest architecture definitions—this is the core design principle of the skill.

Can a session ID be reused?

Within the same workflow, you should reuse the session ID to maintain contextual continuity. But when starting a new independent workflow, generate a new session ID. RUBE_SEARCH_TOOLS with session.generate_id: true can create a new session; subsequent steps should use the returned session.id.