Skip to main content
Glama
vloganathane

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
      F
      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
      -

    • 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
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.3/5.0

    Scored across 414 tools

    Disambiguation2/5

    With 414 tools, many overlap heavily: cron_run vs drush_cron, cache_rebuild vs cache_clear, security_audit vs security_scan vs code_security_scan, and ai_analyze_content_quality vs analyze_content_quality are just a few examples. The CRUD families for each Drupal entity are distinct, but the sheer number of near-duplicates makes selection error-prone.

    Naming Consistency3/5

    Most names are snake_case and readable, but the verb/noun ordering is inconsistent: create_node uses verb_noun, while commerce_store_list and webform_submission_list use noun_verb. Mixed prefixed families and occasional abbreviations keep this from being fully predictable.

    Tool Count1/5

    414 tools is an extreme mismatch for a Drupal MCP server. Even a comprehensive site-management surface should be far smaller; this count guarantees heavy redundancy and makes tool discovery impractical for an agent.

    Completeness4/5

    The surface covers an enormous range of Drupal domains: content, taxonomy, users, config, migrations, testing, accessibility, performance, commerce, webforms, search, and translation. Some lifecycle gaps exist (e.g. no delete for several commerce entities), but most major workflows have some supporting tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources