An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Magnolia Enterprise Headless CMS to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Control your enterprise content repository through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Magnolia CMS.

  1. 01

    Mg.create cms node

    This capability provisions new JSON payloads by writing models natively to your CMS.

  2. 02

    Mg.get delivery children

    Use this to perform structural extraction of properties that drive active branch nesting.

  3. 03

    Mg.get delivery node

    This capability retrieves pure JSON mappings from the JCR tree to identify bounded routing spaces.

  4. 04

    Mg.get template schema

    This capability enumerates explicitly attached structured rules to export active fields.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Magnolia CMS.

  1. 05

    Mg.patch cms node

    Use this to mutate global Web CRM boundaries by substituting draft document schemas.

  2. 06

    Mg.query delivery nodes

    This capability retrieves explicit cloud logging to trace specific payload criteria.

  3. 07

    Mg.wipe cms node

    This capability irreversibly removes explicit app nodes and drops live database bytes.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Magnolia CMS.

  1. 08

    Mg.copy delivery node

    Use this to retrieve exact structural matching for verifying delivery cloning logic.

  2. 09

    Mg.execute workspace command

    This capability dispatches automated validation checks that route explicit platform logic.

  3. 10

    Mg.list jcr workspaces

    This capability identifies precise active arrays spanning your rented context domains.

Real work

What teams actually run

01

API Testing

A developer asks the agent to fetch a specific delivery path to verify the JSON output matches the expected schema.

02

Schema Validation

An architect checks a template definition to ensure all required fields are present before content entry.

03

Content Migration

An ops engineer uses the agent to copy nodes across the repository while keeping delivery logic intact.

04

Workflow Automation

A manager triggers an activation command to move content from draft to live status.

Automate a task

Put Magnolia CMS to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Magnolia CMS works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Magnolia CMS to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

997ms average. Fast in production.

Magnolia CMS is checked daily against the live service.

Daily averagePeak 1400ms
Oct 3Today
Fastest day
829ms
Slowest day
1400ms
14-day trend
Slowing+49%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Magnolia CMS, so you can see the experience inside your AI.

It does not authenticate your account with Magnolia CMS. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Magnolia CMS Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Magnolia CMS capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "magnolia-enterprise-headless-cms-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Magnolia CMS in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Magnolia CMS owners hand off.

This MCP is designed for technical teams managing large scale headless content architectures.

  • 01

    Headless Developers

    They use the agent to test delivery API results and verify JCR properties without manual REST calls.

  • 02

    Content Architects

    They audit component schemas and manage content trees across different site environments.

  • 03

    Digital Ops Teams

    They monitor workspace health and run publishing commands across the Magnolia instance.

FAQ

Questions Magnolia CMS owners ask.

  • 01

    How do I connect my Magnolia instance to my AI client?

    You subscribe to the MCP on Vinkius and enter your Magnolia Host, Port, and Basic Auth (Base64) credentials. Once connected, you can use it in any MCP-compatible client like Claude or Cursor.

  • 02

    Can I use this to publish content?

    Yes. You can use the execute_workspace_command capability to trigger automated activation and publishing workflows.

  • 03

    Does this work with headless delivery?

    Yes. The MCP includes capabilities to navigate delivery endpoints, verify JSON mappings, and query delivery nodes.

  • 04

    Is it safe to delete nodes through the AI?

    The mg.wipe_cms_node capability is designed to irreversibly remove nodes and drop live database bytes. Use it with caution.

  • 05

    What kind of data can the agent see?

    The agent can see and interact with your JCR workspaces, including website, DAM, and configuration data, depending on your permissions.

  • 06

    Can I navigate the JCR tree structure through my agent?

    Yes. Use the mg.get_delivery_children capability by providing an endpoint and parent path. Your agent will retrieve exclusively the hierarchical descendants, allowing you to understand the branch nesting and property distribution accurately.

  • 07

    How do I audit the required fields for a specific Magnolia component?

    The mg.get_template_schema capability parses the YAML definitions of your components. Your agent will list exactly what fields and scalar parameters the template respects, making it easy to verify your content model without opening the code.

  • 08

    Can my agent trigger a content publication command?

    Absolutely. Use the mg.execute_workspace_command capability and specify 'activate' or 'publish' as the command name. Your agent will dispatch the JSON payload to Magnolia's command system to transition your content across lifecycle states.

Explore

More in Developer Tools

Suggestions

Connect Magnolia CMS to Claude, Cursor, ChatGPT & more