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

Q: How do I load Magnolia (Enterprise Headless CMS) content into a LlamaIndex vector store?

Connect using BasicMCPClient and wrap it in McpToolSpec. Use the tool spec to query nodes via mg.getdeliverynode, then feed the JSON output into your index pipeline.

Q: Can LlamaIndex query nested branches in Magnolia (Enterprise Headless CMS)?

Yes. The framework uses mg.getdeliverychildren to extract structural properties of nested branches, allowing the agent to build a hierarchical map of your content inside the index.

Q: Does LlamaIndex support template schema validation with Magnolia (Enterprise Headless CMS)?

Yes, your agent can run mg.gettemplateschema to verify content fields before indexing them, ensuring your vector store only contains data matching active production schemas.

Q: How do I limit which MCP Server tools LlamaIndex can access?

You can apply an allowedtools filter when initializing your McpToolSpec to restrict your agent to read-only tools like mg.getdeliverynode and block write operations.

Index your Magnolia JCR content trees directly into LlamaIndex vector stores using this MCP Server.

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 LlamaIndex

Create your Vinkius account to connect Magnolia (Enterprise Headless CMS) to LlamaIndex 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 LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build a LlamaIndex searchable RAG index of Magnolia nodes

This MCP Server allows your LlamaIndex pipelines to extract content directly from your delivery endpoints. By calling `mg.get_delivery_node`, the framework fetches raw JCR node data and converts it into searchable document objects. These documents are then indexed into your vector store. Your agent can search past content versions and layout structures without having to query the live Magnolia delivery API repeatedly.

Query nested content branches semantically

Stop writing complex JCR queries to find related articles or pages. LlamaIndex uses the MCP Server to call `mg.get_delivery_children` to traverse your active branch nesting and fetch child properties. The retrieved properties are vectorized so your agent can answer semantic questions about your content hierarchy. It maps the relationship between parent pages and nested delivery nodes automatically.

Keep your vector index fresh with workspace tracking

Your pipeline runs `mg.list_jcr_workspaces` to identify active content domains. It then queries `mg.query_delivery_nodes` to pull the latest payload changes and update the index. This ensures your RAG applications are always grounded in actual Magnolia data. The agent compares live JCR schemas with your vector store to flag stale content or missing templates.

Setup guide

Set up Magnolia (Enterprise Headless CMS) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Magnolia (Enterprise Headless CMS) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Magnolia (Enterprise Headless CMS) tools.",
)
response = await agent.run("List recent Magnolia (Enterprise Headless CMS) data")

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 LlamaIndex

Connect using `BasicMCPClient` and wrap it in `McpToolSpec`. Use the tool spec to query nodes via `mg.get_delivery_node`, then feed the JSON output into your index pipeline.

Yes. The framework uses `mg.get_delivery_children` to extract structural properties of nested branches, allowing the agent to build a hierarchical map of your content inside the index.

Yes, your agent can run `mg.get_template_schema` to verify content fields before indexing them, ensuring your vector store only contains data matching active production schemas.

You can apply an `allowed_tools` filter when initializing your `McpToolSpec` to restrict your agent to read-only tools like `mg.get_delivery_node` and block write operations.

Yes. All REST delivery payloads and JCR branch properties are fetched over TLS and executed inside an ephemeral sandbox. Vinkius never retains your workspace data or CMS credentials, routing them strictly between your agent and your Magnolia instance.

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