Skip to main content
Glama
Sign In
Drupal MCP Server

Drupal MCP Server

by vloganathane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Drupal MCP Server

No user-submitted related servers found.

    Related Servers

    • Drupal MCP Server

      peximo
      A
      license
      B
      quality
      D
      maintenance
      Enables AI models to interact with Drupal 10+ sites via JSON:API for querying, searching, and retrieving content. It supports listing content types, searching by title across all types, and fetching detailed node information including relationships.
      4
      ISC

    • SAP-Commerce-MCP

      chriszhangrui
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to directly control, automate, orchestrate, and self-heal Hybris/CCv2 environments and headless Spartacus storefronts through 27 JSON-RPC tools. Covers greenfield site provisioning, CMS scaffolding, B2B organization governance, Drools promotion rules, Solr reindexing, catalog sync, FlexibleSearch/ImpEx/Groovy execution, Spartacus diagnostics with auto-fix, and a self-evolving script and knowledge library.
      27
      1
      MIT

    • magento-mcp-server

      keysersoft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Magento 2 / Adobe Commerce products, stock, orders, and customers through 12 read/write MCP tools with secure, audited access.
      AGPL 3.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2.1/5.0

    Scored across 414 tools

    Disambiguation2/5

    Many tools are distinct by resource, but there are multiple overlapping wrappers and near-duplicates: drush_command vs drush_cron/cron_run/cache_rebuild, security_scan vs security_audit vs code_audit_phpstan, ai_analyze_content_quality vs analyze_content_quality, and several media creation tools. With 414 tools, an agent will struggle to choose the right operation reliably.

    Naming Consistency2/5

    All names are snake_case, but conventions are mixed: verb-first tools like create_node and list_vocabularies coexist with resource-first tools like commerce_store_create and commerce_product_list, and test_run_phpunit vs run_migration adds further inconsistency. The prefixes are also overloaded across different domains, so there is no single predictable pattern.

    Tool Count1/5

    414 tools is far beyond an appropriate set for any coherent MCP server. Many tools are thin wrappers around Drush, duplicate existing operations, or cover very narrow subcases, making the surface extreme and hard to manage.

    Completeness3/5

    Core Drupal areas such as nodes, users, taxonomy, config, views, blocks, menus, fields, redirects, and paragraphs have strong coverage. However, several advertised subdomains are notably partial: commerce promotions/payment gateways/shipping methods lack full CRUD, media entities lack update/delete, webform submissions/elements lack create/update in places, and workflows/search API servers/facets have missing update or delete operations.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources