dot CMS

Your Next Teammate Might Be an AI Agent, But You’re in Control

Your Next Teammate Might Be an AI Agent, But You’re in Control

Share this article on:

What if an AI agent was your teammate? With the new dotCMS MCP Server, you can work side-by-side with AI agents and assistants to draft, edit, manage, or audit content, and always with your rules, your workflows, and your brand voice.

What Is an MCP Server?

An MCP, short for Model Context Protocol, is a secure connector that lets AI agents interact with any system the same way a human user would.

It gives your AI tools the context they need to understand:

  • What data exists

  • How that data is structured

  • What actions they can perform

  • What rules and permissions they must follow

Instead of “guessing,” your AI assistants have a standard way to read, write, and manage data, safely and with granular control and oversight.

In dotCMS, the MCP Server does exactly that for your content teams. It automatically brings in your context, then lets trusted AI agents:

  • Discover your sites, content types, and workflows

  • Draft and update content using your brand rules

  • Run workflow actions with full oversight

Your Secret to AI That Works: Context First

AI only works it best by understanding the world around it.

That’s why the dotCMS MCP Server doesn’t just connect your CMS, it shares your sites, content types, and workflows automatically.

This context keeps your AI grounded in reality, so its drafts follow your structure and workflows instead of guessing.

How to Set Up the MCP Server

Here’s how to get started.

  1. Get a dotCMS environment Cloud, on-prem, or our demo site — they all work.

  2. Create an AI User and API Token

    1. In your dotCMS admin, create a user just for your AI agent.

    2. Give it only the permissions it needs.

    3. Generate a secure API token.

  3. Configure the MCP Server in your AI tool (like Claude Desktop).

    1. Open Claude Desktop

    2. Go to Settings > Developer

    3. Click on Edit Config

    4. This will open the folder with the file claude_desktop_config.json

    5. Edit that file and add the following configuration:

{

    "mcpServers": {

        "mcp1": {},

        "mcp2": {},

        "dotcms": {

            "command": "npx",

            "args": ["-y", "@dotcms/mcp-server"],

            "env": {

                "DOTCMS_URL": "https://your-dotcms-instance.com",

                "AUTH_TOKEN": "your-auth-token"

            }

        }

    }

}
  1. Restart Claude Desktop and start prompting about dotCMS.

How to Use It: Make AI Work for Your Whole Team

Connecting your MCP Server is just the first step. Now it’s about making AI part of your team’s daily routine in a way that keeps your content on-brand, consistent, and compliant.

1. Pick Real Tasks

Start with everyday jobs that slow you down:

  • Draft a blog post from bullet points.

  • Rewrite outdated product pages.

  • Search for content with missing required disclaimers.

  • Generate meta descriptions for old content.

Keep it simple. Test with one piece at a time. Small wins build trust.

2. Build a Shared Prompt Library

Your AI only writes well if it knows your brand voice, tone, and rules. One-off instructions won’t cut it. Create a shared prompt library your whole team can use.

What goes in it:

  • Voice & Tone: How you sound. Friendly but professional? Formal? No slang?

  • Style Rules: Short sentences, active voice, words to avoid.

  • Compliance: Legal disclaimers, terms never to edit, regional requirements (like GDPR or HIPAA).

  • Approved Words: Product names, trademarked phrases.

Example Prompts:

  • “Write in a clear, neutral tone for finance customers. Keep it factual. Add our standard compliance note at the end.”

  • “Friendly and conversational for our blog. Always use approved product names exactly as listed.”

  • “Rewrite this page for EU readers. Formal tone. Include GDPR statement. Never remove legal footers.”

Keep your prompt library in an easy-to-find doc or team folder. Update it as you learn what works.

3. Test Small, Review Together

Try small tasks first. Use dotCMS workflows. Keep a human review step. Would you publish a draft from a new writer without edits?, I’m pretty sure the answer is NO, so don’t do it with AI either.

4. Share and Improve

Good teams share what works.

  • Show your team which prompts get the best results.

  • Refine them over time.

  • Make prompt writing part of onboarding for new team members.

The better your prompts, the better your AI will perform — and the less rewriting you’ll need.

Result: Your AI does the busywork. You focus on strategy and final edits. And every word stays true to your brand and industry rules.

Examples You Can Try Right Now

Need ideas? Here are a few ways to use your AI assistant:

Drafting First Versions

  • Turn outlines into first drafts.

  • Expand bullet points into paragraphs.

  • Rewrite a long post for a new audience.

Bulk Updates

  • Update old meta descriptions to match your new SEO strategy.

  • Find and fix product names that changed last quarter.

  • Refresh headlines for better consistency.

Repurposing Content

  • Split a long article into social posts.

  • Create newsletter snippets from your latest blog.

  • Rewrite a landing page for a new region.

Compliance Checks

  • Search for content missing required disclaimers.

  • Flag old content that mentions outdated terms.

  • Double-check tone and style for brand fit.

Build Good Habits With Your Team

AI works best when your team works together.

  • Test tasks in small batches first.

  • Always review AI drafts before publishing.

  • Use your workflows. Keep your human-in-the-loop step.

  • Share your best prompts so everyone benefits.

When everyone writes better prompts and shares what works, you build a habit. The more you do it, the faster you get.

Stay in Control

The dotCMS MCP Server keeps your governance rock solid with dotCMS content history and logs. Every AI action is:

  • Logged: You see who did what.

  • Traceable: No mystery edits.

  • Reversible: Roll back anytime.

  • Permission-based: Your AI works only where you allow it.

Your workflows don’t change — they just get faster.

Work Smarter, Stay Compliant

dotCMS is built for teams that need to publish faster without sacrificing governance. The MCP Server makes your AI work inside the rules you trust, so you spend less time on grunt work and more time on ideas that move your brand forward.

Ready to get started? Learn how to set up your MCP Server and put your new AI teammate to work.

Recommended Reading
  • AI Content Governance for Content Teams: A Practical Framework
    9 Mar 26
    AI in CMS

    AI Content Governance for Content Teams: A Practical Framework

    Learn why AI content governance is essential for content teams. Discover how to protect brand consistency, reduce legal risk, and manage AI across dozens of sites with dotCMS’s built-in governance tools.

    Fatima

    Fatima Nasir Tareen

    Marketing Specialist

  • 7 Business Benefits of Content Governance Done Right
    9 Mar 26
    Content Management

    7 Business Benefits of Content Governance Done Right

    Discover how strong content governance drives faster time to market, reduces compliance risk, and ensures brand consistency for compliance-led organizations managing content across dozens of sites.

    Fatima

    Fatima Nasir Tareen

    Marketing Specialist

  • AI Search Made Easy
    8 Mar 26
    Technical Guides

    AI Search Made Easy

    dotAI Search is now built into the @dotcms/client SDK. One method call gives your headless app semantic AI-powered search in under 15 minutes.

    Marc

    Marc Boutillette

    Director Outbound Product

  • Java 25 is Here — Try It Today
    4 Mar 26
    Innovation

    Java 25 is Here — Try It Today

    Give your dotCMS a test drive on modern Java. Our new Java 25-based containers are live, easy to spin up with a single Docker command, and already showing faster startup, leaner memory use, and a stronger security footing. In this post, I’ll walk you through how to try the ‎`java-25` images locally, what to expect from the upgrade, how to rebuild your plugins in a few minutes, and why we’re asking you to kick the tires now, long before Java 11 support sunsets.

    Stephen

    Stephen Freudenthaler

    Director of Engineering

Explore dotCMS for your organization

image

dotCMS Named a Major Player

In the IDC MarketScape: Worldwide AI-Enabled Headless CMS 2025 Vendor Assessment

image

Explore an interactive tour

See how dotCMS empowers technical and content teams at compliance-led organizations.

image

Schedule a custom demo

Schedule a custom demo with one of our experts and discover the capabilities of dotCMS for your business.