How to Use the Magnolia (Enterprise Headless CMS) MCP in Mastra AI

Q: Can I build a workflow that syncs content across different Magnolia workspaces?

Yes, that's a core use case. Your agent can use mg.listjcrworkspaces to see all available targets, then run a workflow that uses mg.copydeliverynode to duplicate specific content trees from one to another.

Q: Is it possible to stage changes before they go live with this MCP Server?

Absolutely. A common pattern is to use mg.createcmsnode or mg.patchcmsnode to write changes to a 'draft' or 'staging' workspace first. A separate step in your Mastra AI workflow can then seek approval before copying the content to the 'live' workspace.

Build resilient content automation for Magnolia CMS with Mastra AI's workflow engine.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Magnolia (Enterprise Headless CMS) MCP to Mastra AI

Create your Vinkius account to connect Magnolia (Enterprise Headless CMS) to Mastra AI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Magnolia (Enterprise Headless CMS) with Mastra AI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate Content Migrations Safely

Migrating content between workspaces is always a headache. With Mastra AI, you can build a workflow that handles it for you. Your agent can use `mg.query_delivery_nodes` to find the content, then call `mg.get_template_schema` to make sure the destination supports its structure. If the schema is compatible, the agent uses `mg.copy_delivery_node` to perform the copy. Mastra AI's engine adds automatic retries, so if the target workspace is temporarily locked, the workflow just waits and tries again instead of failing.

Create Failsafe Cleanup Jobs

Deleting old content is risky. This MCP Server gives your Mastra AI agent the tools to do it without causing a disaster. A workflow can first use `mg.query_delivery_nodes` to find nodes older than 90 days, then use `mg.get_delivery_children` to check if they have any active sub-pages. If a node is safe to delete, the workflow can use `mg.wipe_cms_node`. You can even add a human approval step in your Mastra AI workflow before the final deletion is triggered. It's cleanup with a safety net.

Run Complex Publishing Workflows

Some content requires more than a simple publish button. You can design a Mastra AI workflow that orchestrates a whole sequence of events inside Magnolia. For example, trigger a custom validation check with `mg.execute_workspace_command`. Based on the result, the workflow can branch. If validation passes, it might use `mg.patch_cms_node` to update the content's state to 'Published'. If it fails, it can notify a specific team and revert the changes. This lets you codify your exact editorial process.

Setup guide

Set up Magnolia (Enterprise Headless CMS) MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All Magnolia (Enterprise Headless CMS) tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "magnolia-enterprise-headless-cms-mcp-client",
  servers: {
    "magnolia-enterprise-headless-cms-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "Magnolia (Enterprise Headless CMS) Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to Magnolia (Enterprise Headless CMS) tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent Magnolia (Enterprise Headless CMS) transactions"
);
console.log(result.text);

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Magnolia CMS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Magnolia (Enterprise Headless CMS) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Magnolia (Enterprise Headless CMS) MCP in Mastra AI

You instantiate the Mastra MCP client with your unique server URL from Vinkius. The client then fetches the available tools, like `mg.copy_delivery_node`, which you can assign to your agents within your defined workflows.

Yes, that's a core use case. Your agent can use `mg.list_jcr_workspaces` to see all available targets, then run a workflow that uses `mg.copy_delivery_node` to duplicate specific content trees from one to another.

Mastra AI's workflow engine will catch the failure. You can configure it to retry the operation with exponential backoff, send an alert to an admin, or trigger a completely different branch of logic, giving you full control over error handling.

Absolutely. A common pattern is to use `mg.create_cms_node` or `mg.patch_cms_node` to write changes to a 'draft' or 'staging' workspace first. A separate step in your Mastra AI workflow can then seek approval before copying the content to the 'live' workspace.

The server only processes data relevant to the tool being called. A `mg.patch_cms_node` call handles the specific JSON patch and node ID, nothing more. Each tool runs in its own isolated process, and the connection is secured via a single Vinkius token, not your raw Magnolia credentials.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript