LocalGov MCP

LocalGov MCP connects Drupal to AI assistants and MCP-compatible clients by exposing content editing, media management, search, taxonomy, redirects, site administration, and workflow actions as secure MCP tools. It allows AI systems to work with Drupal content while respecting Drupal permissions, access controls, and editorial workflows.

Features

LocalGov MCP extends the MCP Server module by exposing common LocalGov Drupal editorial and administration tasks as MCP tools that can be accessed by AI assistants and automation platforms.

• Create, update, search, publish, unpublish, and manage Drupal content.
• Create new content drafts and revisions while respecting editorial workflows.
• Manage media assets including file uploads and updates.
• Search site content using Search API with automatic fallback when indexes are unavailable.
• Create and manage taxonomy terms.
• Create, update, schedule, publish, and unpublish alert banners.
• Manage redirects and Fix 404 records.
• View and update metatags.
• Create and update location records.
• Schedule future workflow transitions.
• Perform selected site administration tasks including cache rebuilding, cron execution, maintenance mode management, and watchdog access.
• Provides granular tool enablement through a central configuration screen.

Unlike a traditional Drupal API integration, LocalGov MCP enables AI assistants to interact with Drupal content using MCP tools while enforcing Drupal's existing permissions, content moderation workflows, field access rules, and entity access controls.

Typical use cases include:

• AI-assisted content creation and editing.
• Editorial workflow automation.
• Automated content audits and search.
• Managing media libraries through AI agents.
• Assisting content designers and editors with LocalGov Drupal maintenance.
• Building secure AI-powered administrative tools for council websites.

Post-Installation

After enabling the module and rebuilding caches, navigate to:

Configuration → Web services → LocalGov MCP tools

/admin/config/services/localgov-mcp

This administration page allows site administrators to select which MCP tools should be exposed to connected MCP clients. All tools are enabled by default.

You must also configure an MCP transport and authentication method using the MCP Server module. The Drupal account associated with an MCP session determines what actions can be performed. MCP authentication alone does not grant additional permissions.

Recommended setup process:

1. Install and enable LocalGov MCP and its dependencies.
2. Configure MCP Server transport and authentication.
3. Select which tools should be available to MCP clients.
4. Create or assign a dedicated Drupal user account for MCP access.
5. Grant only the minimum permissions required.
6. Test read-only and draft operations before allowing publishing or administration actions.

The module does not create new content types. Instead, it works with supported LocalGov Drupal content types, media entities, taxonomy vocabularies, workflows, redirects, and administration features already present on the site.

Additional Requirements

This module is designed for LocalGov Drupal environments and requires:

• MCP Server
• Drupal Content Moderation workflows
• Search API
• Scheduled Transitions
• Content Lock
• Alert Banner
• Geo Entity
• Metatag
• Redirect
• Fix 404

The module is tailored to LocalGov Drupal content types, workflows, and field structures.

Recommended Modules/Libraries

The following projects enhance the capabilities of LocalGov MCP:

• MCP Server – Required foundation that exposes Drupal functionality through the Model Context Protocol.
• Search API – Improves site search capabilities available to AI assistants.
• Scheduled Transitions – Enables automated publishing and workflow scheduling.
• Content Lock – Prevents editorial conflicts when multiple users are working on content.
• Metatag – Allows AI-assisted SEO metadata management.
• Redirect and Fix 404 – Support redirect management and broken-link resolution.

Similar Projects

LocalGov MCP differs from generic Drupal MCP integrations by providing opinionated tooling specifically for LocalGov Drupal sites.

While the MCP Server module supplies the core MCP framework, LocalGov MCP adds ready-to-use tools for common LocalGov Drupal editorial and administrative tasks, including support for LocalGov content types, workflows, alert banners, redirects, scheduled publishing, content moderation, and governance requirements.

The module focuses on safe, permission-aware operations and allows organisations to expose Drupal functionality to AI systems without bypassing existing editorial controls.

Supporting this Module

If your organisation benefits from this module, consider contributing through:

• Bug reports and feature requests.
• Code contributions and reviews.
• Documentation improvements.
• Testing across different LocalGov Drupal implementations.
• Sponsorship of new MCP tools and integrations.

Community Documentation

Additional documentation is available in the project's feature guides:

• Content management
• Media management
• Alert banners
• Locations
• Scheduling
• Taxonomy
• Administration
• Site search
• Metatags
• Redirects and Fix 404

Video walkthroughs, example MCP client implementations, tutorials, and demonstration sites can be added here as they become available.

Security and Permissions

Security is a core design principle of this module. Every operation respects Drupal's entity access, field access, permission system, and workflow transition rules. MCP clients can only perform actions that the authenticated Drupal account is already permitted to perform.

For production deployments, it is strongly recommended that MCP connections use dedicated service accounts with carefully scoped permissions following the principle of least privilege.