AI Tool Server for Storyblok Content Management - n8n Workflow

Developers building AI agents requiring real-time CMS access.
Content Managers looking to automate Storyblok operations via natural language.
n8n power users utilizing LangChain and Multi-Chain Platform (MCP) capabilities.
Teams seeking customizable n8n templates for AI-driven content operations.

This powerful n8n workflow is designed to function as an AI Tool Server, specifically integrating with Storyblok, a popular headless CMS. By leveraging the specialized Multi-Chain Platform (MCP) n8n trigger, this solution exposes a comprehensive suite of Storyblok operations—including fetching, publishing, unpublishing, and deleting content—as callable tools for sophisticated AI agents. This configuration allows AI models to perform complex content management tasks autonomously, making this a crucial n8n workflow component for modern, AI-driven content pipelines. Utilizing this structure within n8n streamlines content operations and enhances AI agent capabilities significantly, relying on the robust functionality of the Storyblok Tool n8n node.

The automation begins with the 'Storyblok Tool MCP Server' n8n trigger. This specialized n8n trigger is configured to listen for requests from an external AI agent or chain seeking to execute a function defined within this n8n workflow. The core mechanism involves connecting several dedicated Storyblok Tool n8n node instances directly to this trigger via the 'AI Tool' connection setting. When the AI agent determines it needs to perform an action (e.g., 'Publish a story'), the n8n trigger intercepts the instruction and routes the request parameters to the corresponding Storyblok n8n node. These linked n8n nodes handle the actual interaction with the Storyblok API, ensuring seamless execution of complex content actions based on the AI's intent. This entire n8n workflow setup efficiently transforms individual n8n node operations into a robust, centralized tool server for AI agents.

1. Import the n8n template: Copy the provided JSON and import it directly into your n8n instance.


2. Activate the Storyblok Tool MCP Server n8n trigger: This n8n trigger must be activated to start listening for AI tool requests.


3. Set up Storyblok Credentials: Ensure that all Storyblok Tool n8n node instances are configured with valid Storyblok API credentials (e.g., Management Tokens) in your n8n environment. Since the parameters are not visible in the JSON, you will need to manually open each Storyblok n8n node and set up the relevant connection for your project space.


4. Connect the AI Agent: The external AI orchestration layer (like a LangChain sequence running in another n8n workflow or service) must be configured to utilize this running n8n workflow as one of its available tools.

This n8n workflow utilizes several key n8n node types to establish the AI tool server:

1. Storyblok Tool MCP Server (mcpTrigger): The foundational n8n trigger for this service. It registers the subsequent Storyblok n8n node operations as callable functions, allowing an AI Agent/LangChain instance to dynamically use them based on its task.


2. Get a story (Storyblok Tool n8n node): Configured to retrieve specific story data from Storyblok using input provided by the AI agent interacting with this n8n workflow.


3. Get many stories (Storyblok Tool n8n node): Allows the AI agent to query and fetch lists of content entries, useful for batch operations or content discovery within the broader n8n template context.


4. Publish a story (Storyblok Tool n8n node): Executes the critical publishing operation on content, providing the AI agent with direct control over content availability through this specific n8n node.


5. Unpublish a story (Storyblok Tool n8n node): Reverses the publishing state, demonstrating the full content lifecycle control offered by this administrative n8n workflow.


6. Delete a story (Storyblok Tool n8n node): Enables permanent removal of content, highlighting the comprehensive administrative capabilities exposed by this dedicated n8n workflow tool server.