---
title: "dotcms"
description: "Build and maintain dotCMS sites: content types, pages, templates, containers, VTL, and headless Next.js: with an MCP server and agent skills."
canonical: https://agentpluginsdirectory.com/plugins/dotcms
last-updated: 2026-10-21
---

# dotcms
Build and maintain dotCMS sites: content types, pages, templates, containers, VTL, and headless Next.js: with an MCP server and agent skills.
- Slug: dotcms
- Publisher: dotCMS
- Repository: https://github.com/dotCMS/agent-toolkit
- Manifest: plugin.json
- Version: 0.1.0
- License: MIT
- Category (editorial): integrations
- Skills: 2 (dotcms-best-practices, dotcms-create-sites)
- MCP servers: 1 (dotcms)
- Stars: 0
- Repository created: 2026-09-01
- Repository last pushed: 2026-10-19
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/dotcms
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What dotcms does, in the publisher's words

Agent skills and an MCP server for building and maintaining dotCMS sites, content types, pages, templates, containers, content placement, VTL, and headless Next.js. Works with Claude Code, Cursor, Codex, and any Agent Skills-compatible agent.

Both support VTL-rendered and headless (Next.js) delivery.

> Why a skill and not just docs: in dotCMS a missing piece renders blank or shell-only with > HTTP 200, never an error. A successful response is not evidence that anything rendered. Every > build path in these skills ends in a verify step for that reason.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/dotCMS/agent-toolkit/HEAD/README.md

## Skills

- dotcms-best-practices: Reference for doing any single thing in dotCMS correctly, create a content type, page, template or container; place content; author VTL; wire a headless Next.js frontend; or debug a page that renders blank. Indexed by intent, so you load one file for the task at hand. Use whenever working with dot…
- dotcms-create-sites: Plans and builds a complete dotCMS site in two phases. Phase 1 interviews the user and writes PLAN.md (purpose, sitemap, data model, every fact tagged) and DESIGN.md (visual identity tokens). Phase 2 hands off to the dotcms-best-practices skill, which owns the build sequence, and holds the verify-a…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- dotcms: transport: stdio; command: npx -y @dotcms/mcp-server@latest

Read from the plugin's own mcp.json. Environment variable names only, never values.