L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Développement · SKILL.md

drupal-mcp-connector

drupal-mcp-connector

MCP connector for Drupal CMS – enables AI-powered content management, module configuration, view building, and site administration through Claude

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: drupal-mcp-connector description: "MCP connector for Drupal CMS – enables AI-powered content management, module configuration, view building, and site administration through Claude" license: GPL tags: ["dev","cms","mcp","drupal","php"] difficulty: advanced time_to_master: "4-8 weeks" version: "1.0.0"

Drupal MCP Connector

Overview

This skill enables Claude to interact with Drupal through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Drupal's REST/JSON:API, allowing natural language control of Drupal operations, intelligent automation, and AI-powered assistance for Drupal workflows.

When to Use This Skill

  • Content type and field creation via natural language
  • View and display configuration with AI assistance
  • Module installation and configuration management
  • Taxonomy organization and content classification
  • Migration planning and execution assistance

Architecture

┌─────────────┐     ┌─────────────────┐     ┌──────────────────┐
│   Claude     │────▶│   MCP Server    │────▶│   Drupal           │
│   (Client)   │◀────│   (TypeScript)  │◀────│   (REST/JSON:API )│
└─────────────┘     └─────────────────┘     └──────────────────┘

Core Concepts

MCP Server Setup

The connector implements an MCP server that exposes Drupal operations as tools Claude can invoke. The server translates natural language intentions into REST/JSON:API calls.

Key Endpoints/Interfaces

/jsonapi/node/article, /jsonapi/taxonomy_term, /entity/node, /views, /admin/modules

Implementation

// Drupal MCP Server Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "drupal-mcp-connector",
  version: "1.0.0",
});

// Tool: List/Query Resources
server.tool(
  "list_resources",
  "List and query Drupal resources with optional filters",
  {
    query: z.string().optional().describe("Search query or filter"),
    limit: z.number().optional().describe("Max results to return"),
  },
  async ({ query, limit }) => {
    // Call Drupal REST/JSON:API
    const response = await fetch(`${BASE_URL}/jsonapi/node/article`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Tool: Create Resource
server.tool(
  "create_resource",
  "Create a new resource in Drupal",
  {
    name: z.string().describe("Resource name"),
    config: z.object({}).passthrough().optional().describe("Resource configuration"),
  },
  async ({ name, config }) => {
    const response = await fetch(`${BASE_URL}/jsonapi/node/article`, {
      method: "POST",
      headers: {
        "Authorization": `Bearer ${API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ name, ...config }),
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: `Created: ${JSON.stringify(data)}` }],
    };
  }
);

// Tool: Analyze/Report
server.tool(
  "analyze",
  "AI-powered analysis of Drupal data",
  {
    type: z.string().describe("Analysis type"),
    timeframe: z.string().optional().describe("Time range for analysis"),
  },
  async ({ type, timeframe }) => {
    // Fetch data and provide AI analysis
    const response = await fetch(`${BASE_URL}/jsonapi/node/article`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Start server
const transport = new StdioServerTransport();
await server.connect(transport);

Claude Desktop Configuration

{
  "mcpServers": {
    "drupal-mcp-connector": {
      "command": "node",
      "args": ["path/to/drupal-mcp-connector/index.js"],
      "env": {
        "DRUPAL_API_KEY": "your-api-key",
        "DRUPAL_BASE_URL": "https://your-instance-url"
      }
    }
  }
}

Best Practices

  1. Authentication: Store API keys securely using environment variables; never hardcode credentials
  2. Rate Limiting: Implement request throttling to respect Drupal API rate limits
  3. Error Handling: Provide clear, actionable error messages for common failure scenarios
  4. Pagination: Handle paginated responses for large datasets efficiently
  5. Caching: Cache frequently accessed read-only data to reduce API calls
  6. Security: Validate all inputs before passing to the Drupal API; sanitize outputs
  7. Logging: Log all API interactions for debugging and audit purposes

Example Prompts

"Create a content type for Events with fields for date, location, speaker, and registration link"

Security Considerations

  • All API credentials must be stored as environment variables
  • Implement input validation and sanitization for all tool parameters
  • Use HTTPS for all API communications
  • Follow the principle of least privilege for API token permissions
  • Audit log all write operations for compliance tracking

Resources

Changelog

VersionDateChanges
1.0.02026-04-01Initial MCP connector skill

Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.

Skills enregistrées