Magnolia CMS Connector for AI agents.
10 live capabilities
Manage headless content and JCR repository nodes through natural conversation.
Waiting for input…
Why people use Magnolia CMS
Magnolia CMS JCR Node Management for Headless Content
This Connector changes that by bringing the repository into your chat interface. Instead of hunting for a node path, you just ask your agent to find it. You can audit schemas, check delivery endpoints, and move content nodes in seconds. You get a direct line to your JCR repository, turning a multi-tab chore into a single conversation.
What Vinkius changes
You get a direct natural language interface for your Magnolia CMS repository.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Verifying content mappings
A developer needs to check a specific tour's JSON data.
- Real-world use case 02
Auditing component schemas
A content architect needs to see what fields a news article template requires.
- Real-world use case 03
Mapping content hierarchy
A content manager wants to see how content is nested.
Complete set · 10capabilities
The complete Magnolia CMS capability set.
These are the exact actions your AI can choose when you ask it to work with Magnolia CMS.
01—04
4 capabilities in this set.
Part of 10 available through Magnolia CMS.
- 01 Capability
Mg.copy delivery node
Retrieve the exact structural matching for delivery cloning logic. Use this to replicate content structures without breaking delivery rules.
- 02 Capability
Mg.create cms node
Provision a highly-available JSON payload writing model natively. This creates new content nodes that follow your system's rules.
- 03 Capability
Mg.wipe cms node
Irreversibly vaporize explicit App nodes to drop live database bytes. Use this to clean up your repository and remove old data.
- 04 Capability
Mg.execute workspace command
Dispatch an automated validation check routing explicit platform logic. This helps you run workspace commands like activation or publishing.
05—07
3 capabilities in this set.
Part of 10 available through Magnolia CMS.
- 05 Capability
Mg.get delivery children
Perform structural extraction of properties driving active branch nesting. It helps you see how your content nodes are organized.
- 06 Capability
Mg.get delivery node
Return pure JSON mappings from the JCR tree securely. This identifies bounded routing spaces inside your Magnolia delivery layers.
- 07 Capability
Mg.get template schema
Enumerate explicitly attached structured rules exporting active fields. Use this to see exactly what fields a component expects.
08—10
3 capabilities in this set.
Part of 10 available through Magnolia CMS.
- 08 Capability
Mg.list jcr workspaces
Identify precise active arrays spanning rented context domains. This shows you how your project data is distributed across the site.
- 09 Capability
Mg.query delivery nodes
Retrieve explicit cloud logging tracing explicit payload criteria. Use this to find specific content fragments based on your criteria.
- 10 Capability
Mg.patch cms node
Mutate global Web CRM boundaries by substituting draft document schemas. This lets you update existing content nodes and schemas.
Set up in minutes
One URL. Then ask Magnolia CMS to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Magnolia CMS from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Magnolia CMS, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Magnolia CMS for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Magnolia CMS URL.
- Step 03
Save and start
Save the connection and enable Magnolia CMS in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"magnolia-enterprise-headless-cms": {
"url": "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Magnolia CMS
Open Agent mode in chat and ask: "Using Magnolia CMS, help me...". 10 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"magnolia-enterprise-headless-cms": {
"url": "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Magnolia CMS
Ask Copilot: "Using Magnolia CMS, help me...". 10 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"magnolia-enterprise-headless-cms": {
"url": "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Magnolia CMS
Open Cascade and ask: "Using Magnolia CMS, help me...". 10 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"magnolia-enterprise-headless-cms": {
"url": "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Magnolia CMS
Ask Cline: "Using Magnolia CMS, help me...". 10 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add magnolia-enterprise-headless-cms --transport http "https://edge.vinkius.com/vk_preview_u6bjdVVF5duWxI08JFgNFgIEqXftnazuC33oVsOc/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Magnolia CMS
Ask Claude: "Using Magnolia CMS, show me...". 10 tools are ready
Where the request belongs
Work Magnolia CMS can move forward.
The headless developer who's tired of manually checking JSON mappings, the content architect auditing complex trees, and the ops person managing multi-site publishing.
Headless Developer
Verifies delivery API results and checks JCR node properties during development.
Content Architect
Audits component schemas and manages large hierarchical content trees across environments.
Digital Ops Specialist
Monitors workspace health and executes publishing commands across the entire instance.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsElemeno
Equip your AI agent to manage content collections, track singletons, and monitor items via the Elemeno CMS API.
ContentStack (Management)
Grant your AI agent read-write capabilities using ContentStack CMA. Update, publish, and manage contents, schemas, and environments from chat.
Crafter CMS
Manage headless content via Crafter CMS. execute GraphQL queries, write Git-based XML content, and publish to delivery engines directly from any AI agent.
Drupal
Manage headless content via Drupal. list nodes, handle taxonomy terms, manage files, and audit users directly from any AI agent.
Payload CMS
Manage headless content via Payload CMS. manipulate documents, patch JSON states, retrieve singletons, and structure database endpoints using AI.
DatoCMS
Manage headless content via DatoCMS. execute GraphQL queries, handle record CRUD, manage content models, and audit media uploads directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep Magnolia CMS connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Magnolia CMS.
The practical details behind the request, access and result.
Can I use the Magnolia CMS MCP to check my content schemas?
Yes, you can use it to pull the exact field definitions and structured rules for any template. This helps you ensure your content matches what the system expects before you hit publish.
How does the Magnolia CMS MCP handle content publishing?
You can trigger automated workspace commands like activation and publishing through your agent. It moves content through its lifecycle without you having to click through the admin UI.
Can I move content between different folders with Magnolia CMS MCP?
Yes, you can move or copy content nodes across your repository. This helps you maintain structural matching while moving content to new locations.
Does Magnolia CMS MCP work for headless content delivery?
It's designed specifically for headless delivery. You can verify JSON mappings and navigate through configured delivery endpoints like pages or tours.
Can I see all my active workspaces using Magnolia CMS MCP?
Yes, you can list all active JCR workspaces like your website, DAM, or configuration domains. This gives you a clear view of how your data is distributed.
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.
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.
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.
One connection away
Give your agent a direct line to Magnolia CMS.
Connect Magnolia CMS once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available