Skip to content
Magnolia Author MCP

Let Claude author your Magnolia pages

An open-source MCP server that connects your AI assistant to Magnolia CMS. It discovers your templates and components at runtime, writes real structured content, verifies the render, and publishes, all in natural language.

MCP serverConnected
Claude Desktop / Claude Code3 calls / 0 errors
claude_desktop_config.jsonConfig
{
  "mcpServers": {
    "magnolia-author": {
      "command": "/path/to/magnolia-author-mcp/mcp/.venv/bin/python",
      "args": ["/path/to/magnolia-author-mcp/mcp/magnolia_author_mcp.py"],
      "env": {
        "MAGNOLIA_AUTHOR_INSTANCES": "/path/to/instances.json"
      }
    }
  }
}

One config block. The server reads your instance registry on every call, so credential and instance edits take effect with no restart.

View on GitHub →
01 / Setup

Three steps to AI-assisted authoring

Step 01

Clone and install

git clone the repo, create a Python venv, and install two dependencies. One file, no build step.

Step 02

Point it at Magnolia

Add your author instances to instances.json with a base URL and a credential source. Dev, UAT and prod tiers in one registry.

Step 03

Author in natural language

Register the server with Claude Desktop, Claude Code or Cursor, then ask. The agent discovers your components and writes real content.

02 / Capabilities

Everything an agent needs to author safely

Understands your site

It reads your live Magnolia instance to learn the page types, building blocks, and field options you actually have, so it works with your setup straight away. No access to your codebase, nothing to configure first.

Gets the details right

Rich content like option toggles, repeating lists, dates, and linked images is saved in exactly the format your CMS expects, so pages come out correct instead of looking fine but breaking quietly.

Builds whole pages at once

Create a complete page, every section included, in a single step. Or make the same change across many pages together, instead of editing them one at a time.

Checks its own work

After a change it looks at the real published page and flags broken images, missing content, and pages that load but show nothing, so issues surface before your visitors hit them.

Safe by default

Deletes preview what they would remove and can be undone, every change is recorded, and anything affecting your live site needs your explicit go-ahead.

Fits how your team works

Connect your development, staging, and production sites from one place, and use it with the AI assistant your team already has, like Claude.

03 / Open source

Free, open, and built in the open

The Magnolia Author MCP is released under the Apache License 2.0. Read the source, run it against your own instances, fork it, and contribute. It is maintained by Noice, a Magnolia Platinum Partner, and is independent of Magnolia International.

04 / Prompts

Just ask your assistant

  • List the page templates on the UAT author, then show the areas of the landing-page template

  • Build an events landing page with a hero banner and a three-card grid

  • Swap the header image on /about-us for the new team photo

  • What components can go in the main area of the article template?

  • Find every page that still references the old product name

  • Verify the homepage renders cleanly, then publish it to UAT

05 / FAQ

FAQs

It is an open-source Model Context Protocol (MCP) server. It connects an AI agent like Claude to your Magnolia CMS author instance so the agent can discover templates and components, create and update pages, verify how they render, and publish, all driven by natural language.

Yes. It is released under the Apache License 2.0 on GitHub. You can use it commercially, fork it, and contribute back. There is no SaaS account and no licence fee.

Any MCP-compatible client. It speaks the standard stdio transport, so Claude Desktop, Claude Code, Cursor, and custom MCP hosts all work. You point the client at the server and set one environment variable.

No. The server discovers your page templates, component definitions, and dialog field schemas from the running instance over Magnolia REST APIs. It makes no assumptions about your component library, so it works against any Magnolia 6.x author with the Nodes API enabled.

There are guard rails built in. Deletes are dry-run by default and snapshot the subtree before a confirmed delete; every mutating call is written to an audit log; and any instance flagged as production requires explicit confirmation before a write. We still recommend a least-privilege Magnolia role for the service account.

It does not replace AdminCentral; it automates the repetitive parts. Bulk page builds, content updates across many pages, image wiring, and structural changes that would take hours by hand become a single instruction, while a human still reviews and approves what ships.