WordPress MCP Adapter: Turning Abilities into Agent-Friendly Tools
I can now treat a WordPress site like an MCP tool server -- abilities become callable tools, which turns admin tasks into agent-friendly workflows.
Drupal CMS and ecosystem
View All TagsI can now treat a WordPress site like an MCP tool server -- abilities become callable tools, which turns admin tasks into agent-friendly workflows.
I sketched a traffic forensics workflow around Pantheon's new "top IPs / user agents / paths" metrics and turned it into a small, shippable reference so teams can spot noisy traffic fast and stop guessing where spikes come from.
The Hook When one Drupal module depends on another, I want to iterate across both without publishing interim versions or wiring up a private Composer repo. Path repositories give me that speed while keeping dependency boundaries honest.
FlowDrop is a visual, drag-and-drop workflow editor for Drupal with AI integration hooks. The core project is moving quickly with Drupal 11 releases (0.5.1 shipped January 27, 2026), which makes it a good time to evaluate the AI-adjacent contrib pieces that plug into FlowDrop.
I looked at FlowDrop Agents and FlowDrop Node Session to see if they are ready for real editorial workflows.
I shipped a Drupal migrate mapping validator utility that catches broken mappings before they land in prod.
I outlined a practical stack for multilingual HTML email in Drupal using Mail Composer plus a dedicated HTML mailer, and packaged it as a small demo repo you can reference.
I distilled WordPress 6.9.1 RC1 into a compatibility checklist for plugins and themes before the maintenance release landed. I also packaged the checklist and notes into a small repo so teams can clone it and wire it into their own QA flow.
I turned my Drupal Canvas Full HTML notes into a clear rollout guide and backed it with a runnable repo so teams can ship rich editing without breaking permissions.