MCP Drupal
Related Servers
Alternatives to MCP Drupal
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI-powered YouTube content management using Claude Code to orchestrate research, scripting, and scheduling via Google Sheets, Docs, and Drive.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to read and write Google Sheets, including cell operations, row appending, sheet creation, formatting, and batch updates via the Google Sheets API.MIT
- AlicenseAqualityBmaintenanceEnables Claude to directly create and publish posts on Velog through reverse-engineered GraphQL APIs. Supports a human-in-the-loop workflow from draft to review to publication, maintaining user control while automating content creation.655 npm5MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing Google Drive files, Docs, and Sheets through natural language via Claude Code, with tools for listing, searching, editing, and formatting documents and spreadsheets.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to read Google Docs and their comment threads, then write corrections and replies back into the same document at the same URL.26 npmMIT
- FlicenseBqualityCmaintenanceConnects Claude.ai to Google Sheets, allowing read, append, and update operations on spreadsheets directly from chat.3-
TDQS
Scored across 8 tools
Each tool targets a clearly distinct resource and action: Drupal nodes, Drupal resource types, Google Sheet rows, and Google Doc extraction are all unambiguous. No two tools could reasonably be confused for the same operation.
All tool names follow a consistent snake_case verb-first pattern such as list_nodes, create_node, update_node, list_sheet_rows, and mark_sheet_row_done. The naming is predictable and easy to remember.
With 8 tools, the server is well scoped for its purpose: it covers Drupal node operations, content type discovery, and the Google Sheets/Docs content-import pipeline. Each tool earns its place.
The core ingestion workflow is well covered: read from Sheet and Doc, create/update Drupal nodes, list types, and mark rows done. The main gap is the lack of a delete_node operation, which would make full content lifecycle management more complete.