MCP Tools

MCP Tools is a module that provides AI assistant tools for Drupal sites. It includes 223 tools, supports read - write operations, resource access, and prompt functions. It is mainly used for local development and prototyping, with a modular architecture and a three - layer access control security mechanism.

Developer tools Artificial intelligence chatbots #Drupal tools #AI assistant #Site building #Configuration management .php

rating : 2.5 points

downloads : 6.7K

update time : 2026-03-12

Open Site

What is MCP Tools?

MCP Tools is an AI assistant toolkit designed for Drupal websites. It allows AI assistants (such as Claude, ChatGPT, etc.) to interact with Drupal sites through natural language and perform various operations, from simple content queries to complex site building tasks. Imagine that you can tell the AI assistant: 'Create a blog system that includes articles, categories, tags, and editor roles', and the AI will automatically create content types, fields, category vocabularies, user roles, and permissions for you.

How to use MCP Tools?

Using MCP Tools is very simple: 1. Install the MCP Tools module on your Drupal site. 2. Select a connection method (the local STDIO method is recommended). 3. Configure your AI assistant to connect to the MCP server. 4. Start interacting with your Drupal site through natural language. MCP Tools provides two main connection methods: the local STDIO method (recommended for development) and the remote HTTP method (for test environments).

Applicable scenarios

MCP Tools is most suitable for the following scenarios: • Local development environment: Rapid prototyping and site building. • Content management: Batch creation, update, and deletion of content. • Site configuration: Management of users, roles, permissions, and menus. • Automation tasks: Execution of repetitive management operations. • Learning and teaching: Understanding various functions of Drupal. Note: It is recommended to use read-only mode in the production environment to ensure site security.

Main features

Complete site building capabilities

Supports the creation of a complete site structure including content types, fields, category vocabularies, user roles, permissions, views, blocks, etc. The AI assistant can build complex Drupal sites through natural language descriptions.

Modular architecture

Adopts a modular design. 35 sub - modules provide 198 write - operation tools and 25 read - only tools. You can enable specific functional modules as needed to keep the system lightweight.

Multi - layer security control

Provides three - layer access control: module level, global read - only mode, and connection scope. Built - in protection mechanisms prevent dangerous operations, such as protecting user ID 1 and the administrator role.

Multiple connection methods

Supports the local STDIO method (recommended) and the remote HTTP method. The STDIO method runs through Drush commands, and the HTTP method provides API key authentication.

Resources and prompts

Provides read - only resources (such as site status and configuration snapshots) and reusable analysis prompts to help the AI assistant better understand the site context.

Observability hooks

All tool executions trigger events, supporting custom log recording, metric collection, or Webhook notifications for easy monitoring and auditing.

Advantages

Significantly improve development efficiency: Quickly complete complex Drupal configuration tasks through natural language.

Reduce the learning curve: Non - technical personnel can also manage Drupal sites through AI assistants.

Modular design: Enable functions as needed to keep the system lightweight.

Enterprise - level security: Multi - layer access control and built - in protection mechanisms.

Flexible deployment: Supports local and remote connection methods.

Complete coverage: 223 tools cover core Drupal functions.

Limitations

Production environment risks: Write operations may cause configuration drift. It is recommended to use read - only mode.

Dependence on AI assistants: Requires an AI assistant that supports the MCP protocol.

Learning cost: Requires an understanding of the MCP protocol and basic Drupal concepts.

Performance considerations: Complex operations may take a long time.

Version limitations: Only supports Drupal 10.3+ and Drupal 11.

How to use

Install MCP Tools

Install and enable the MCP Tools module via Composer.

Select a connection method

Select a connection method according to your usage scenario. The STDIO method is recommended for local development.

Start the MCP server

Start the MCP server using the Drush command. It is recommended to use uid = 1 for local development.

Configure the AI assistant

Configure the MCP server connection in your AI assistant (such as Claude Desktop).

Enable required functional modules

Enable specific functional modules as needed. You can start with the core site building modules.

Usage examples

Create a blog system

Create a complete blog system through natural language instructions, including content types, categories, user roles, and permissions.

Batch content management

Batch create, update, or delete content to improve content management efficiency.

Site health check

Check the health status of the Drupal site, including security updates, performance issues, and error logs.

User permission management

Manage user roles and permissions to ensure site security.

Frequently Asked Questions

Is MCP Tools secure? Can it be used in a production environment?

Which Drupal versions are supported?

How to control the access permissions of the AI assistant?

Will MCP Tools affect site performance?

How to back up the configurations created by MCP Tools?

Which AI assistants are supported?

Related resources

Official documentation

The GitHub repository for MCP Tools, containing complete documentation, installation guides, and examples.

Drupal project page

The official project page on Drupal.org, containing release versions and issue tracking.

Quick start guide

A 5 - minute quick start guide, suitable for new users.

Troubleshooting

Solutions to common problems and error fixes.

Client integration guide

How to configure various AI clients to connect to MCP Tools.

Usage cases

Examples of actual workflows and best practices.

MCP protocol specification

The official specification document for the Model Context Protocol.

Drupal community support

Join the Drupal Slack community for help and support.

🚀 MCP Tools

Batteries-included MCP tools for AI assistants working with Drupal sites.

🚀 Quick Start

MCP Tools offers a set of high - value tools for AI assistants interacting with Drupal sites. To get started, make sure your Drupal version and PHP version meet the requirements, then follow the installation steps.

✨ Features

Comprehensive Tools: A total of 223 tools, including 25 read - only and 198 write/analysis operations across 35 submodules, solve real - world problems rather than just providing generic CRUD operations.
Resource Exposure: Exposes read - only resources like drupal://site/status and drupal://site/snapshot for lightweight site context and provides prompts such as mcp_tools/site - brief for reusable analysis instructions.
Observability Hooks: Dispatches tool execution events for custom logging, metrics, or webhooks.
AI - Powered Site Building: Enables full AI - powered site building, including creating content types, fields, roles, taxonomies, views, blocks, media, webforms, themes, layouts, and applying recipes through natural conversation.
Admin UI: Allows configuration of settings at /admin/config/services/mcp - tools, including access control, rate limiting, and webhook notifications.

📦 Installation

To install MCP Tools, run the following commands:

composer require drupal/mcp_tools
drush en mcp_tools

Local MCP (STDIO) setup (recommended)

drush en mcp_tools_stdio
drush mcp - tools:serve --uid = 1

Tip: Drush often boots as uid 0 (anonymous). For local development, use --uid = 1. For shared environments, use a dedicated user with only the MCP Tools permissions you need.

Gateway mode (optional):

drush mcp - tools:serve --uid = 1 --gateway

Gateway tools:

mcp_tools/discover - tools
mcp_tools/get - tool - info
mcp_tools/execute - tool

Remote MCP (HTTP) setup (experimental)

drush en mcp_tools_remote
drush mcp - tools:remote - key - create --label="My Key" --scopes=read --ttl = 86400

Configure the endpoint at /_mcp_tools in your MCP client, and send the key as Authorization: Bearer … or X - MCP - Api - Key: ….

💻 Usage Examples

Local (STDIO via Drush) — recommended

# Enable the transport.
drush en mcp_tools_stdio -y

# Run the MCP server over STDIO (Claude Desktop, Claude Code, etc).
drush mcp - tools:serve --uid = 1

# With specific scopes (local only)
MCP_SCOPE = read,write drush mcp - tools:serve --uid = 1
# or: drush mcp - tools:serve --uid = 1 --scope = read,write

Remote (HTTP) — experimental

# Enable the transport.
drush en mcp_tools_remote -y

# Create a read - only API key (shown once).
drush mcp - tools:remote - key - create --label="My Key" --scopes=read --ttl = 86400

CLI Helpers

# List server profiles.
drush mcp:servers

# Apply the recommended development preset and enable bundles.
drush mcp:dev - profile

# Inspect a server profile and list components.
drush mcp:server - info --server = default --tools --resources --prompts

# Smoke - test server configuration and dependencies.
drush mcp:server - smoke --server = default

# Validate component registry definitions.
drush mcp:components - validate

# Scaffold a component module.
drush mcp:scaffold --machine - name = my_module --name="My MCP Module"

📚 Documentation

mcp_tools/docs/QUICKSTART.md — 5 - minute onboarding
mcp_tools/docs/TROUBLESHOOTING.md — Common errors and fixes
mcp_tools/docs/CLIENT_INTEGRATIONS.md — MCP client configs (STDIO + HTTP)
mcp_tools/docs/USE_CASES.md — Real - world workflows

🔧 Technical Details

Version Compatibility

Drupal Version	PHP Version	Status	Notes
10.3.x	8.3	✅ Tested	Minimum supported version
11.x	8.4	✅ Tested	Drupal 11 requires PHP 8.4+

PHP Support: 8.3, 8.4

Architecture: Granular Submodules

MCP Tools uses a modular architecture where each functional area is a separate submodule.

mcp_tools/                        # Base module (25 read - only tools)
├── src/
│   ├── Form/SettingsForm.php     # Admin UI at /admin/config/services/mcp - tools
│   └── Service/
│       ├── AccessManager.php     # Three - layer access control
│       ├── RateLimiter.php       # Rate limiting for write operations
│       ├── AuditLogger.php       # Audit logging with sanitization
│       ├── WebhookNotifier.php   # Webhook notifications
│       └── ErrorFormatter.php    # Standardized error responses
└── modules/
    ├── mcp_tools_content/        # Content CRUD (4 tools)
    ├── mcp_tools_structure/      # Content types, fields, taxonomy, roles (20 tools)
    ├── mcp_tools_users/          # User management (5 tools)
    ├── mcp_tools_menus/          # Menu management (5 tools)
    ├── mcp_tools_views/          # Views management (6 tools)
    ├── mcp_tools_blocks/         # Block placement (5 tools)
    ├── mcp_tools_media/          # Media management (6 tools)
    ├── mcp_tools_webform/        # Webform integration (7 tools)
    ├── mcp_tools_theme/          # Theme settings (8 tools)
    ├── mcp_tools_layout_builder/ # Layout Builder (9 tools)
    ├── mcp_tools_recipes/        # Drupal Recipes (6 tools)
    ├── mcp_tools_config/         # Configuration management (5 tools)
    ├── mcp_tools_observability/  # Tool execution logging subscriber
    ├── mcp_tools_paragraphs/     # Paragraphs integration (6 tools)
    ├── mcp_tools_moderation/     # Content Moderation (6 tools)
    ├── mcp_tools_scheduler/      # Scheduled publish (5 tools)
    ├── mcp_tools_metatag/        # SEO meta tags (5 tools)
    ├── mcp_tools_image_styles/   # Image styles (7 tools)
    ├── mcp_tools_cache/          # Cache management (6 tools)
    ├── mcp_tools_cron/           # Cron management (5 tools)
    ├── mcp_tools_ultimate_cron/  # Ultimate Cron (6 tools)
    ├── mcp_tools_pathauto/       # URL aliases (6 tools)
    ├── mcp_tools_redirect/       # URL redirects (7 tools)
    ├── mcp_tools_sitemap/        # XML sitemap (7 tools)
    ├── mcp_tools_search_api/     # Search API (9 tools)
    ├── mcp_tools_entity_clone/   # Entity cloning (4 tools)
    ├── mcp_tools_analysis/       # Site analysis (8 tools)
    ├── mcp_tools_batch/          # Bulk operations (6 tools)
    ├── mcp_tools_templates/      # Site templates (5 tools)
    ├── mcp_tools_migration/      # Content migration (7 tools)
    ├── mcp_tools_jsonapi/        # JSON:API entity CRUD (6 tools)
    └── mcp_tools_remote_media/   # Remote file fetch & media (1 tool)

Access Control

MCP Tools provides three layers of access control:

Module - Based Access: Only enabled submodules expose their tools.
Global Read - Only Mode: Site - wide toggle to disable all write operations.

// In settings.php or via config
$config['mcp_tools.settings']['access']['read_only_mode'] = TRUE;

Connection Scopes: Per - connection access levels (read/write/admin).

Server Profiles (YAML - only)

Define multiple MCP server profiles in mcp_tools_servers.settings.yml and select them via the STDIO --server option or the remote server_id setting.

default_server: default
servers:
  default:
    name: 'Drupal MCP Tools'
    version: '1.0.0'
    pagination_limit: 50
    include_all_tools: false
    gateway_mode: false
    enable_resources: true
    enable_prompts: true
    component_public_only: false
    transports: ['http', 'stdio']
    scopes: ['read', 'write']
    # permission_callback: 'my_module.server_access:check'

Read - Only Tools (25)

Site Health

Tool	Description
`get_site_status`	Drupal/PHP version, module counts, cron, maintenance mode
`get_system_status`	System requirements, PHP info, database status
`check_security_updates`	Security updates for core and contrib
`check_cron_status`	Cron health and last run time
`analyze_watchdog`	Log analysis - errors, warnings, summaries
`get_queue_status`	Queue item counts and worker status
`get_file_system_status`	Directory permissions, disk usage

Content

Tool	Description
`list_content_types`	Content types with field definitions
`get_recent_content`	Recently created/modified content
`search_content`	Title - based content search
`get_vocabularies`	Taxonomy vocabularies with term counts
`get_terms`	Terms from vocabulary (flat or hierarchical)
`get_files`	Managed files with MIME breakdown
`find_orphaned_files`	Unused file detection

Configuration

Tool	Description
`get_config_status`	Config sync status (active vs staged)
`get_config`	View specific configuration object
`list_config`	List config names with optional prefix filter
`list_text_formats`	List all available text formats
`get_text_format`	Get details about a specific text format

Users

Tool	Description
`get_roles`	Roles with permissions
`get_users`	User accounts, status, activity
`get_permissions`	All permissions by provider

Structure

Tool	Description
`get_menus`	All menus with link counts
`get_menu_tree`	Hierarchical menu structure

Discovery

Tool	Description
`mcp_tools_list_available`	List all available MCP tools by category or search

Write Submodules (198 tools across 31 submodules)

Submodule	Tools	Description
`mcp_tools_content`	4	Content CRUD (create, update, delete, publish)
`mcp_tools_structure`	20	Content types, fields, vocabularies, roles, permissions
`mcp_tools_users`	5	User accounts, roles, blocking
`mcp_tools_menus`	5	Menus and menu links
`mcp_tools_views`	6	Views creation and management
`mcp_tools_blocks`	5	Block placement and configuration
`mcp_tools_media`	6	Media types, uploads, entities
`mcp_tools_webform`	7	Webform management and submissions (requires `webform`)
`mcp_tools_theme`	8	Theme settings, enable/disable
`mcp_tools_layout_builder`	9	Layout sections, blocks, plugins (requires `layout_builder`)
`mcp_tools_recipes`	6	Drupal Recipes — apply requires `admin` scope (10.3+)
`mcp_tools_config`	5	Configuration diff, export, MCP change tracking, preview
`mcp_tools_paragraphs`	6	Paragraph types and fields (requires `paragraphs`)
`mcp_tools_moderation`	6	Content moderation workflows (requires `content_moderation`)
`mcp_tools_scheduler`	5	Scheduled publish/unpublish (requires `scheduler`)
`mcp_tools_metatag`	5	SEO meta tags (requires `metatag`)
`mcp_tools_image_styles`	7	Image styles and effects
`mcp_tools_cache`	6	Cache clear, invalidate, rebuild
`mcp_tools_cron`	5	Cron jobs and queues
`mcp_tools_ultimate_cron`	6	Ultimate Cron job management (requires `ultimate_cron`)
`mcp_tools_pathauto`	6	URL alias patterns (requires `pathauto`)
`mcp_tools_redirect`	7	URL redirects (requires `redirect`)
`mcp_tools_sitemap`	7	XML sitemap management (requires `simple_sitemap`)
`mcp_tools_search_api`	9	Search indexes and servers (requires `search_api`)
`mcp_tools_entity_clone`	4	Entity cloning (requires `entity_clone`)
`mcp_tools_analysis`	8	SEO, security, accessibility, performance audits
`mcp_tools_batch`	6	Bulk content operations (max 50 items/batch)
`mcp_tools_templates`	5	Site templates (blog, portfolio, business, docs)
`mcp_tools_migration`	7	CSV/JSON import and export (max 100 items)
`mcp_tools_jsonapi`	6	Generic entity CRUD via JSON:API (requires `jsonapi`)
`mcp_tools_remote_media`	1	Remote file fetch and media creation

Security

Built - in Protections

Modular by default: Enable only the submodules you need.
Three - layer access control: Modules, global toggle, connection scopes.
Permission - based: Each category has its own Drupal permission.
Audit logging: All write operations logged with user info.
Read operation throttling: Expensive read operations are rate - limited (broken links, content search).
Sensitive data redaction: Passwords and secrets never logged.
Protected entities: uid 1, administrator role, core views/menus protected.
Dangerous permissions blocked: Cannot grant site admin permissions via MCP.

Protected Entities

Entity	Protection
User ID 1	Cannot be modified or blocked
Administrator role	Cannot be assigned via MCP
System menus	admin, main, footer, tools, account protected
Core views	Cannot delete core - provided views
Active themes	Cannot disable current default/admin theme

Blocked Permissions

These permissions can never be granted via MCP:

administer permissions
administer users
administer site configuration
administer modules
administer software updates
administer themes
bypass node access
synchronize configuration
import configuration
export configuration

Security Considerations

Risk	Mitigation	Status
Prompt injection	Malicious content could instruct AI	⚠️ Use read - only in production
Privilege escalation	Blocked dangerous permissions	✅ Implemented
Content injection (XSS)	Relies on Drupal's text filtering	✅ Drupal handles
DoS via mass creation	Rate limiting	✅ Implemented
Data exfiltration	Read tools expose site info	⚠️ Use proper auth
Config drift	Changes not in Git	⚠️ Export after changes

Production Hardening

If you must use MCP Tools in production:

// settings.php - Enable read - only mode
$config['mcp_tools.settings']['access']['read_only_mode'] = TRUE;

// Or allow only read scope by default
$config['mcp_tools.settings']['access']['default_scopes'] = ['read'];

// Enable rate limiting
$config['mcp_tools.settings']['rate_limiting']['enabled'] = TRUE;
$config['mcp_tools.settings']['rate_limiting']['max_writes_per_minute'] = 10;
$config['mcp_tools.settings']['rate_limiting']['max_writes_per_hour'] = 100;

Additional recommendations:

Use IP allowlisting at the web server level.
Require authentication for MCP endpoints.
Monitor audit logs for unusual activity.
Keep write submodules disabled in production.
Use separate environments for AI - assisted development.

Configuration Management Warning

MCP Tools creates configuration directly in the database, which can cause config drift. Best practice: Always export config after using write tools:

# After using MCP to create structures
drush config:export
git add config/
git commit -m "Export MCP - created configuration"

📄 License

GPL - 2.0 - or - later

Gitlab MCP Server

Certified

The GitLab MCP server is a project based on the Model Context Protocol that provides a comprehensive toolset for interacting with GitLab accounts, including code review, merge request management, CI/CD configuration, and other functions.

A Python-based MCP Server that provides advanced to-do list management and content organization functions through the Notion API, enabling seamless integration between AI models and Notion.

Markdownify is a multi-functional file conversion service that supports converting multiple formats such as PDFs, images, audio, and web page content into Markdown format.

TypeScript

34.3K

5 points

Duckduckgo MCP Server

Certified

The DuckDuckGo Search MCP Server provides web search and content scraping services for LLMs such as Claude.

UnityMCP is a Unity editor plugin that implements the Model Context Protocol (MCP), providing seamless integration between Unity and AI assistants, including real - time state monitoring, remote command execution, and log functions.

31.1K

5 points

Figma Context MCP

Framelink Figma MCP Server is a server that provides access to Figma design data for AI programming tools (such as Cursor). By simplifying the Figma API response, it helps AI more accurately achieve one - click conversion from design to code.

A Gmail automatic authentication MCP server designed for Claude Desktop, supporting Gmail management through natural language interaction, including complete functions such as sending emails, label management, and batch operations.

The MiniMax Model Context Protocol (MCP) is an official server that supports interaction with powerful text-to-speech, video/image generation APIs, and is suitable for various client tools such as Claude Desktop and Cursor.

Python

48.6K

4.8 points

Zhiqi Future, Your AI Solution Think Tank

English 简体中文繁體中文にほんご

MCP Tools

Overview

Content Details

Alternatives

What is MCP Tools?

How to use MCP Tools?

Applicable scenarios

Main features

How to use

Usage examples

Frequently Asked Questions

Related resources

Installation

🚀 MCP Tools

🚀 Quick Start

✨ Features

📦 Installation

Local MCP (STDIO) setup (recommended)

Remote MCP (HTTP) setup (experimental)

💻 Usage Examples

Local (STDIO via Drush) — recommended

Remote (HTTP) — experimental

CLI Helpers

📚 Documentation

🔧 Technical Details

Version Compatibility

Architecture: Granular Submodules

Access Control

Server Profiles (YAML - only)

Read - Only Tools (25)

Site Health

Content

Configuration

Users

Structure

Discovery

Write Submodules (198 tools across 31 submodules)

Security

Built - in Protections

Protected Entities

Blocked Permissions

Security Considerations

Production Hardening

Configuration Management Warning

📄 License

Alternatives