{"slug": "is-drupal-still-a-cms-its-new-role-in-the-agentic-stack", "title": "Is Drupal Still a CMS? Its New Role in the Agentic Stack", "summary": "Drupal is evolving beyond its traditional CMS role to become a governed environment for AI agents, leveraging existing architecture for structured content, permissions, and workflows. Through projects like AI Search, Tool API, and MCP Server, Drupal can now provide context, tools, and skills to external agent harnesses, enabling semantic retrieval and permission-aware actions. This positions Drupal as a key component in the emerging agentic stack, where it manages the rules and permissions while external agents handle reasoning and execution.", "body_md": "For most of its history, Drupal has been easy to describe: a CMS, or for developers, a content management framework.\n\nThat is still true. But in 2026, it is becoming incomplete.\n\nThrough projects such as AI Search, AI Agents, Tool API, and MCP Server, Drupal can now participate in RAG pipelines, expose application capabilities as tools, and allow external AI agents to interact with a site.\n\nWhat makes this interesting is not that Drupal suddenly \"has AI.\"\n\nIt is that much of the architecture agents need was already there.\n\nA mature Drupal application already knows how to represent structured entities, relationships, permissions, revisions, workflows, configuration, APIs, and services.\n\nDrupal doesn't just store documents. It stores **structured domain knowledge together with rules governing what can be done with it**.\n\nIn the emerging agentic stack, that maps surprisingly well to three concepts: **context, skills, and tools**.\n\nDrupal content can become **context**. AI Search can retrieve relevant entities through semantic search and feed them into RAG pipelines.\n\nDrupal capabilities can become **tools**. Tool API can expose operations such as:\n\n```\nsearch_content(query)\ncreate_article(data)\npublish_content(entity_id)\ncreate_taxonomy_term(vocabulary, name)\n```\n\nAnd higher-level combinations of tools, instructions, and domain rules can become something closer to **skills**: reusable capabilities for operating a particular Drupal application.\n\nBut there is another piece: the **harness**.\n\nThis distinction matters.\n\nAn agent is more than an LLM with access to some tools.\n\nThe harness is the runtime around the model: the system that decides what context to provide, which tools are available, how many steps the agent can take, how failures are handled, when human approval is required, and when execution should stop.\n\nThat harness might live in an external coding agent, an automation platform, or a custom agent built with something like LangGraph.\n\nDrupal can sit underneath it:\n\n```\n             Agent Harness\n                  │\n       ┌──────────┼──────────┐\n       ↓          ↓          ↓\n    Context     Skills      Tools\n       │          │          │\n       └──────────┼──────────┘\n                  ↓\n                 MCP\n                  ↓\n                Drupal\n          ┌───────┼────────┐\n          ↓       ↓        ↓\n       Content  Actions  Permissions\n```\n\nThis is where Drupal's role becomes more interesting.\n\nDrupal does not need to replace the agent framework.\n\nIt can become the **governed environment the agent operates against**.\n\nDrupal's AI Search project integrates embeddings and vector search with Search API.\n\nA Drupal site can therefore expose its structured content as semantic context:\n\n```\nDrupal entities\n      ↓\nSearch API\n      ↓\nchunking + embeddings\n      ↓\nvector database\n      ↓\nsemantic retrieval\n      ↓\nagent context\n```\n\nFor organizations whose authoritative information already lives in Drupal, this removes an awkward duplication.\n\nInstead of maintaining Drupal as the CMS and building an entirely separate knowledge system for AI, Drupal itself can participate in the retrieval architecture.\n\nThe other direction is action.\n\nTool API allows Drupal operations to be represented as structured capabilities. MCP Server can then expose those capabilities to external MCP-compatible agents.\n\nAn external agent could discover that a Drupal application provides tools for searching content, managing taxonomy, creating drafts, or triggering workflows.\n\nThe harness decides **when** to use them.\n\nDrupal decides **whether the operation is allowed**.\n\nThat separation is important.\n\nGiving an LLM unrestricted database access is easy. Giving an agent a small set of explicit, permission-aware capabilities is much safer.\n\nAnd this is where some of Drupal's old complexity suddenly becomes valuable.\n\nEntities, permissions, revisions, moderation, workflows, plugins, and configuration were originally designed to control what humans could do.\n\nNow the same architecture can help control what **agents** can do.\n\nDrupal is still a CMS.\n\nIt is not suddenly a replacement for LangGraph, an agent runtime, or a general-purpose Agent SDK.\n\nA more useful description is that Drupal is becoming a possible **application and governance layer in the agentic stack**:\n\n```\nDrupal entities     → context\nAI Search           → retrieval\nTool API            → tools\nDomain workflows    → skills\nPermissions         → governance\nMCP                 → interoperability\nExternal runtime    → harness\n```\n\nThat distinction matters.\n\nHumans see pages, fields, forms, and workflows.\n\nApplications see APIs.\n\nLLMs see context.\n\nAgents see tools and skills.\n\nThe harness sees an environment it can operate.\n\nDrupal spent more than two decades building systems for structured knowledge, permissions, workflows, and controlled operations. AI agents now need many of those same things.\n\nSo perhaps the interesting question is no longer:\n\n**\"Is Drupal still a CMS?\"**\n\nIt is:\n\n**\"Could a CMS become the governed application layer behind AI agents?\"**\n\nDrupal is starting to make a surprisingly strong case that it can.", "url": "https://wpnews.pro/news/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack", "canonical_source": "https://dev.to/yielab/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack-4mfa", "published_at": "2026-08-19 22:15:40+00:00", "updated_at": "2026-08-19 22:43:04.779622+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "developer-tools", "artificial-intelligence"], "entities": ["Drupal", "AI Search", "Tool API", "MCP Server", "Search API", "LangGraph"], "alternates": {"html": "https://wpnews.pro/news/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack", "markdown": "https://wpnews.pro/news/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack.md", "text": "https://wpnews.pro/news/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack.txt", "jsonld": "https://wpnews.pro/news/is-drupal-still-a-cms-its-new-role-in-the-agentic-stack.jsonld"}}