Skip to main content
Glama
457,857 tools. Updated 2026-08-14 18:31

"Drupal" matching MCP tools:

Matching MCP Servers

  • 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
  • Fetches a public URL and fingerprints its tech stack, revealing frameworks, CMS, analytics, CDNs, and server-side details with confidence and evidence.
    MIT
  • Query Drupal's JSON:API with arbitrary path and raw query parameters for custom resources, filters, sorting, or pagination not covered by higher-level tools.
    MIT
  • Execute shell commands inside DDEV project services (web, db, redis, solr) for testing, dependency management, and database inspection.
    GPL 2.0
  • Retrieve repository page content by Drupal node ID to access metadata, descriptions, video embeds, and person links from Polish academic databases.
    MIT
  • Retrieve a paginated list of Drupal nodes filtered by content type (bundle), with optional filters, sorting, and field selection via JSON:API.
    MIT
  • Create Drupal nodes via JSON:API by specifying content type and field attributes, with optional relationships.
    MIT
  • Delete a Drupal node permanently using its bundle and UUID. Irreversible action for content removal via JSON:API.
    MIT
  • Fetch a single Drupal node by specifying its content bundle and UUID. Use to retrieve specific nodes from a Drupal site via JSON:API.
    MIT
  • Retrieve a list of taxonomy terms from a specified vocabulary, with options to filter by fields, sort by weight or other criteria, and limit results.
    MIT
  • Search Drupal content by title across all content types when you don't know the specific type. Find relevant content quickly with this cross-type search tool.
  • Fetches up to 32KB of the domain's HTML and response headers from the edge, then fingerprints the content for known CMS platforms, JavaScript frameworks, CDN providers, and analytics tools. Detection is based on meta generator tags, script src patterns, response headers, and cookie names. Use this tool when: - You need to know what CMS (WordPress, Drupal, Shopify) a site runs. - You are assessing a domain's infrastructure before a security review. - You want to identify analytics or marketing tools a site embeds. Do NOT use this tool when: - You want HTTP headers and security posture — use `intel_http` instead. - You want tracker database classification — use `get_domain` instead. - You need robots.txt AI policy — use `intel_robots` instead. Inputs: - `domain` (query, required): Domain to fingerprint. Returns: - `cms`: detected content management system, or null. - `frameworks`: JavaScript/backend frameworks detected. - `cdn`: CDN provider detected, or null. - `analytics`: analytics and tracking tools detected. - `meta_generators`: raw meta generator tag values. Cost: - Free. No API key required. Latency: - Typical: 2-4s (HTML fetch), p99: 7s.
    Connector
  • What is this website built with? Deterministic fingerprinting from one fetch — like the old meta generator tag, but it works even when sites strip it. Detects WordPress, Shopify, Squarespace, Wix, Webflow, GoDaddy, Drupal, Joomla, Ghost, Magento, Next.js/Nuxt/Gatsby/Astro and other frameworks, static HTML, custom PHP — with the evidence for the verdict, the raw generator tag when present, and the server/CDN stack. No AI. ($0.002 per call, paid via x402)
    Connector