--- title: "Acquia Source MCP Server" date: "2026-04-15T12:38:30+00:00" summary: image: type: "page" url: "/acquia-source/acquia-source-mcp-server" id: "93f79d41-da66-4af2-81f2-6f31b729897f" --- Model Context Protocol (MCP) capabilities in Drupal for Acquia Source accelerate content management. Add MCP server capabilities to expose resources, resource templates, and tools. These components enable AI agents to work with content models, create content, and manage content. This document explains how to enable and use the MCP server in Acquia Source, connect external MCP clients, and identify supported resources and tools. MCP server overview  -------------------- An MCP server provides a standard method for AI agents and compatible tools to connect to external systems and data sources. With an MCP server, an AI agent or editor can perform the following actions: * Discover resources, which consist of read-only data exposed by a system. * Call tools or operations to create or update data. * Work with a consistent and well-defined API supported by multiple clients. MCP server capabilities  ------------------------ With the Acquia Source MCP server, AI-powered tools can perform the following actions: * Read and list Drupal content types, media types, vocabularies, and Drupal Canvas components. * Create and update nodes, media, and taxonomy terms. * Manage Drupal Canvas pages and component-based layouts. * Evolve the content model by creating content types and fields. These capabilities are particularly useful for the following actions: * Generate structured content in bulk. * Refactor content types or fields with guidance from an AI assistant. * Create Drupal Canvas pages and layouts by prompting AI. Enabling the MCP server ----------------------- The MCP server is an experimental feature within Acquia Source and must be enabled per site. 1. [Access your site](https://docs.acquia.com/acquia-source/creating-and-publishing-your-first-page#access-a-site). 2. In the left sidebar, click **Configurations**. 3. Click **Experimental features**. 4. On the Experimental features page, locate the **MCP Server** section. 5. Toggle **Enable MCP Server** to ON. 6. Click **Save configuration**. 7. Click **Configure** to view the MCP server connection details. * **MCP client configuration**: Integrate these parameters into claude\_desktop\_config.json or Cursor to establish a connection. * **MCP Inspector**: Execute the provided command in a terminal to launch the debug environment. * **OAuth configuration**: Define scopes and authentication parameters for the server. Note You typically do not need to modify settings on this page. Copy the connection URL provided here to configure your external client. 8. Follow the instructions in the External client connection section to complete the setup using your external tool. External client connection -------------------------- ### Claude Code To configure the server in Claude Code: 1. Run the following command: `claude mcp add acquia-source-mcp {ACQUIA_SOURCE_SITE_MCP_URL} --transport http --scope project`.  Ensure that you replace **{ACQUIA\_SOURCE\_SITE\_MCP\_URL}** with the MCP URL provided in [**MCP Client Configuration**](#enable-mcp-server) in your Source CMS site.  2. Open Claude Code. 3. Type `/mcp` to manage MCP servers. 4. Select `acquia-source-mcp`. 5. Click **Authenticate** to launch the authorization flow. MCP server domains ------------------ The MCP server exposes tools grouped into three domains: * **Content Management**: Read and write content entities such as nodes, media, taxonomy terms, and users. * **Content Modeling**: Define and evolve content structures such as content types, fields, and JSON schemas. * **Drupal Canvas**: Manage Drupal Canvas pages and component-based layouts. Each domain exposes the following components: * Resources, which provide read-only data. * Resource templates, which provide parameterized read endpoints. * Tools, which provide operations to change state. Supported resources and tools  ------------------------------ ### Content management Type Name / Purpose Identifier / URI Resource List content types drupal://content-types Resource List media types drupal://media-types Resource List vocabularies drupal://vocabularies Resource List text formats drupal://filter-formats Resource template Load entity by type and ID drupal://entity/{entity\_type\_id}/{id} Tool Create node create\_node Tool Update node update\_node Tool Batch create nodes batch\_create\_nodes Tool Create media (file-based) create\_media Tool Create remote video (OEmbed) create\_remote\_video Tool Get or create taxonomy term get\_or\_create\_term Tool List entities list\_entities ### Content modeling Type Name / Purpose Identifier / URI Resource List content-type field storages drupal://content-types/fields Resource List field types drupal://field-types Resource template Content type JSON Schema drupal://content-types/{bundle} Resource template Media type JSON Schema drupal://media-types/{bundle} Resource template Vocabulary JSON Schema drupal://vocabularies/{vid} Tool Create content type create\_content\_type Tool Add field to content type add\_field\_to\_content\_type Tool Update field config update\_field\_config ### Drupal Canvas Type Name / Purpose Identifier / URI Resource List Drupal Canvas components canvas://components Resource List Drupal Canvas pages canvas://pages Resource template Drupal Canvas component detail canvas://components/{id} Tool Create Drupal Canvas page create\_canvas\_page Tool Update Drupal Canvas page metadata update\_canvas\_page Tool Delete Drupal Canvas page delete\_canvas\_page Tool Get page layout get\_page\_layout Tool Set page layout set\_page\_layout Tool Add component to page add\_component\_to\_page Tool Move component move\_component Tool Remove component remove\_component Tool Update component props update\_component\_props Explore the MCP server with MCP Inspector  ------------------------------------------ The MCP Inspector is a development and Quality Engineering tool to debug and interact with MCP servers. For day-to-day usage, configure an AI agent or MCP-capable client. ### To start the MCP Inspector: Run the following command: `npx @modelcontextprotocol/inspector --transport http`. ### To connect the MCP Inspector: 1. Add the URL to the Acquia Source site MCP server URL. 2. Set connection type to **Direct**. 3. Click **Connect**. 4. Complete the OAuth flow for dynamic client registration. 5. Click **Allow**. After you connect, explore the exposed server components with the following options: * List Resources * List Templates * Tools