MCP Tools

Summary: MCP Tools lets AI assistants build and manage Drupal sites through the Model Context Protocol (MCP) using Drupal’s Tool API. Create content types, fields, views, roles, blocks, and more by describing what you want.

Example

You: "Create a blog with articles, categories, tags, and an editor role"
AI:  Creates the content type, taxonomies, fields, role, and permissions

Recommended Usage (Local-First)

MCP Tools is designed primarily for local development and prototyping. Remote exposure is supported, but intentionally optional.

Tooling Strategy (How We Keep It Safe)

• Modular by design: tools are split across submodules so you only enable what you need.
• Scopes: per-connection scopes (read/write/admin) gate what a client can do.
• Safe defaults: new installs default to read-only scopes; enable write/admin explicitly when needed.
• Global safety toggles: read-only mode and config-only mode prevent accidental damage.
• Production hardening: rate limiting, protected entities, and sensitive data redaction.
• Config-as-code workflow: keep changes reviewable by exporting config after write operations.

Config-as-Code Workflow

If you use write tools to create or change configuration, export your config and commit it to Git to avoid configuration drift.

• Recommended: enable config-only mode when you want write access limited to configuration changes.
• Export config: run drush cex -y after changes.
• Optional: enable mcp_tools_config to preview/export via tools (mcp_config_changes, mcp_config_preview, mcp_config_export).

Features

205 tools across 29 submodules covering site building, content, admin, and automation:

Site Building

• Create/manage content types and 18+ field types
• Taxonomy vocabularies and terms
• User roles and permissions
• Menus and navigation

Views & Display

• Create Views (page + block displays)
• Place/configure blocks
• Layout Builder sections and components
• Image styles and effects

Content & Media

• Create/update/publish/delete content
• Upload/manage media files
• Moderation workflows
• Bulk operations (up to 50 items)

Administration

• Site health + security update checks
• Cache/cron/queue management
• Audits and analysis tools (SEO/accessibility/broken links)

MCP Transports

• Recommended (local): mcp_tools_stdio — STDIO server via Drush.
• Experimental (remote): mcp_tools_remote — HTTP endpoint with API key authentication + optional IP allowlist and key TTL (intended for trusted networks; requires a dedicated execution user, not uid 1).
• Optional compatibility: mcp_tools_mcp_server — bridge to drupal/mcp_server when upstream is stable.

Security Built-In

• Three-layer access control (enabled modules, global toggles, per-connection scopes)
• Config-only mode (restrict writes to configuration changes)
• Rate limiting for write operations
• Audit logging with sensitive data redaction
• Protected entities and blocked dangerous permissions by default

Installation

drush en mcp_tools -y
drush en mcp_tools_content mcp_tools_structure mcp_tools_views -y

Configure MCP Tools at /admin/config/services/mcp-tools.

Starter Bundles

Enable only what you need. Common starting points:

• Core site builder (local dev): mcp_tools_structure, mcp_tools_views, mcp_tools_blocks, mcp_tools_menus, mcp_tools_users, mcp_tools_content, mcp_tools_media
• Ops (use with care): mcp_tools_cache, mcp_tools_cron, mcp_tools_batch, mcp_tools_analysis
• Contrib extras (only if installed): mcp_tools_webform, mcp_tools_paragraphs, mcp_tools_metatag, mcp_tools_pathauto, mcp_tools_redirect, mcp_tools_search_api, mcp_tools_sitemap

Requirements

• Drupal 10.3+ or Drupal 11
• Tool API module
• PHP 8.3+ (CI runs on PHP 8.3 and 8.4)

Maintainers / Support

Maintained by CodeWheel.

• Issue queue: drupal.org issues
• GitHub: code-wheel/mcp-tools

Tip: If you use write tools to create configuration, export config after changes (config-as-code workflow).