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.
On the Experimental features page, locate the MCP Server section.
Toggle Enable MCP Server to ON.
Click Save configuration.
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.
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:
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 in your Source CMS site.
Open Claude Code.
Type /mcp to manage MCP servers.
Select acquia-source-mcp.
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
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
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:
Add the URL to the Acquia Source site MCP server URL.
Set connection type to Direct.
Click Connect.
Complete the OAuth flow for dynamic client registration.
Click Allow.
After you connect, explore the exposed server components with the following options:
List Resources
List Templates
Tools
Acquia Source MCP Server
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.
On the Experimental features page, locate the MCP Server section.
Toggle Enable MCP Server to ON.
Click Save configuration.
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.
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:
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 in your Source CMS site.
Open Claude Code.
Type /mcp to manage MCP servers.
Select acquia-source-mcp.
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
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
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:
Add the URL to the Acquia Source site MCP server URL.
Set connection type to Direct.
Click Connect.
Complete the OAuth flow for dynamic client registration.
Click Allow.
After you connect, explore the exposed server components with the following options:
List Resources
List Templates
Tools
Tool
Create remote video (OEmbed)
create_remote_video
Tool
Get or create taxonomy term
get_or_create_term
Tool
List entities
list_entities
Tool
Move component
move_component
Tool
Remove component
remove_component
Tool
Update component props
update_component_props
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Tool
Create remote video (OEmbed)
create_remote_video
Tool
Get or create taxonomy term
get_or_create_term
Tool
List entities
list_entities
Tool
Move component
move_component
Tool
Remove component
remove_component
Tool
Update component props
update_component_props
Acquia Source MCP Server | Acquia Product Documentation
Acquia Source
Acquia Source MCP Server
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia Source