Skip to main content
Glama
Sign In
peximo

Drupal MCP Server

by peximo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Drupal MCP Server

No user-submitted related servers found.

    Related Servers

    • trace-node

      nat-build-with-oracle
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • Drupal MCP Server

      vloganathane
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to perform Drupal site operations across 37 tool modules, covering JSON:API and GraphQL access, Drush commands, content and configuration management, migration assistance, commerce, security audits, and headless development. Supports local and cloud environments with flexible authentication and multiple AI providers.
      414
      MIT

    • SitefinityMCP

      jaysanderson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources