Drupal MCP Server
Related Servers
Alternatives to Drupal MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI models to manage a Drupal-shaped content store over MCP, including nodes, vocabularies, terms, tag filtering, and trigram/semantic search, while logging every tool call for observability.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to read and query content from a Progress Sitefinity CMS instance via its OData API. Tools are dynamically generated from the live service metadata, supporting filtering, searching, and navigation across content types.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Axolot CMS for content, design tokens, media, and module management with site context awareness.21 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to Drupal content through MCP tools for listing content types, retrieving content type schemas, fetching content, and searching content.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact directly with Strapi v5 CMS content through full CRUD operations, media uploads, and content type exploration using Strapi's Document Service API.232 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for Drupal sites via JSON:API, enabling CRUD operations on nodes, taxonomy terms, and users using natural language.8MIT
TDQS
Scored across 4 tools
There is some overlap between query_content and search_content, as both involve searching for content, though their descriptions clarify that query_content filters by type while search_content searches by title across all types. get_node and list_content_types are distinct, but the two search tools could cause confusion without careful reading of descriptions.
Tool names follow a consistent verb_noun pattern (get_node, list_content_types, query_content, search_content), with clear and readable conventions. There are no deviations in style, making them predictable and easy to understand.
With only 4 tools, the set feels thin for a Drupal content management server, lacking essential CRUD operations like create, update, or delete nodes. While the tools cover basic retrieval and listing, the scope seems incomplete for typical content management workflows.
The tool surface is significantly incomplete for a Drupal content management domain. It includes retrieval and search functions but lacks any create, update, or delete operations, which are core to content lifecycle management. This gap will likely cause agent failures when trying to perform full content management tasks.