(Really hoping this doesn't break self-promotion rules; someone joined today who only heard about this initiative through a Reddit comment, so I figured it was good to post it here to a wider audience.)

At DrupalCon Chicago, the "vibes" I caught around Drupal + AI were that folks were roughly divided into three camps:

1. There's a vocal minority of folks who are absolutely ecstatic about AI, and are adopting it wholesale for absolutely everything, up to and including orchestrating fleets of agents to write and review code while they sleep.
2. There's a vocal minority folks who absolutely despise AI, refuse to engage with it from foundational moral / ethical principles, and are trying desperately to halt these tools' proliferation.
3. And then, there's the vast majority who are somewhere in the middle. Maybe they've played around with these tools some, but seen them make bone-headed errors when pointed at Drupal and so dismissed them as hype. Maybe they were too busy shipping for the past ~year and only recently popped their heads up to look at the developer landscape around them and are now feeling fearful that they're being left hopelessly behind. Maybe they're "AI curious," but have absolutely no idea how/where to get started.

We created the Drupal AI Learners Club for group #3. We hold ~weekly informal sessions where we get together as a group and just... talk about AI. This includes "show and tell" demos on what's working (and also what's not ;-)), sharing links to interesting AI-related tools and bits of news, and answering questions so that we collectively help each other level up on AI. Think Drupal Dojo (if you were around back then), but for Drupal + AI.

Our Club Ground Rules are very simple:

1. We follow the Drupal Code of Conduct
2. There are no “stupid questions” — we are all here to learn 💙
3. Pragmatic advice, not hype / pitches
4. Please speak slowly and clearly to help non-native English speakers
5. Your participation is key!

We've done two of these sessions so far (see Session Recordings and Session Recaps):

• Kickoff Meeting: Show Your Setup! with demos from Jürgen Haas, Mike Herchel, and Scott Falconer on how they're each using AI tools to assist with Drupal contribution.
• From Autocomplete to Autopilot where Scott Falconer did a presentation that covers the evolution of AI coding tools and demonstrated using agents to research and fix an open Drupal.org issue.

Our third session is coming up April 27 https://luma.com/552bhxpx where Jim Birch and Eduardo Telaya will be demoing their Skills (as in Agent Skills) setups. These are extra bits of context that can teach "vanilla" AI coding tools how to be much smarter about Drupal.

If this sounds like your jam, join us in #ai-learners on Drupal Slack! There are folks sharing links to things they're playing with and finding useful to them, there are questions from folks who are hitting weird AI problems, and there's a tab there where you can suggest + vote on future topics. This is also the place to offer to be on a session to talk about one of these topics (just please bear in mind our presenter guidelines — this is a learning community, not a marketing channel ;-))

Whew! If you made it this far, thanks so much for reading, and hope to catch you on a future one of these, either in the audience or on the mic. :)

Hey,

Curious what kind of test assignments you'd recommend for Drupal backend devs at different levels. What would you suggest for each?

I know most candidates use AI now anyway, not really worried about that, I'm more curious about tasks that actually reveal how someone structures code and thinks through decisions.

Any favorites? Anything you'd avoid?

A month ago I posted about AI Connect (webmcp_connect) — an OAuth 2.0 WebMCP bridge that lets AI agents interact with Drupal sites securely.

Since then I've been using it in production and found some real issues that are now fixed. Here's what changed.

Critical fix: Bearer tokens returning 403

The OAuth flow worked, tokens were issued, but when an AI agent actually tried to call a tool — 403 every time. Turned out Drupal's auth provider was registered with global: FALSE but the tools route had no _auth declaration. So Drupal never applied the Bearer auth and every request stayed anonymous.

One-line fix in ai_connect.routing.yml. If you installed v1.0, just update and run drush cr.

New: One-click token generator

The full OAuth + PKCE flow is the right way for production, but a lot of AI tools (Kiro CLI, Cursor, anything without a browser redirect) can't do it. The /ai-connect page now has a "Generate Token" button for logged-in users.

Click it → get a ready-to-paste prompt that works two ways:

• Option A — for MCP clients (Claude Desktop, OpenCode): calls webmcp_addSite with manifest URL + token
• Option B — for any agent that can make HTTP requests: direct POST /api/ai-connect/v1/tools/{tool} with Authorization: Bearer

The prompt auto-lists every registered tool with its exact name, so the agent can call them immediately without searching.

Permission-aware UI

• Users with access → see the Generate Token button
• Logged-in without permission → see "You do not have permission"
• Anonymous → see "Log in to generate a token"

No more confusing 403 pages.

11 languages

ar, de, es, fr, he, it, ja, nl, pt-BR, ru, zh-CN — all validated with msgfmt --check.

Links

• Drupal.org: https://www.drupal.org/project/webmcp_connect
• Source: https://git.drupalcode.org/project/webmcp_connect
• Project page: https://webmcp-connect-drupal.gold-t.co.il/
• Live demo: https://webmcp-connect-drupal.gold-t.co.il/ai-connect

Previous post: https://www.reddit.com/r/drupal/comments/1rlj6gu/

What tools would be most useful for your Drupal site? I'm thinking about adding content creation (createNode) and user management next.

A while back I wrote an article explaining how I was working with AI on my Drupal projects using DDEV containers with Drupal-specific agents and skills. Several people asked me to share it but I couldn't, because it had client data in it. I've cleaned it up and published everything as open source DDEV add-ons: a meta add-on that installs Claude Code, OpenCode, specialized agents and skills for Drupal 10/11, and several supporting pieces with a single command.

I explain it in detail in the article:
https://menetray.com/en/blog/ddev-ai-workspace-ive-published-my-full-drupal-ai-development-setup

If you work with Drupal, I'd love to hear what you think: whether you try it, if you find it useful, if you'd actually use it. If you run into any issues, let me know here or open an issue on the matching repo and I'll fix it as soon as I can.

https://github.com/trebormc/ddev-ai-workspace

Every time I come back to a Drupal project after working on other stacks,
there’s a short phase where everything feels… heavier than expected.

not necessarily bad just different:

• configuration layers
• content types + fields + views
• hooks / services / structure

but after spending some time with it, things start to click again and the flexibility becomes clear.

it made me wonder

is Drupal actually complex by nature,
or does it just feel that way because you need to stay “in its ecosystem” consistently to be comfortable with it?

especially compared to tools where you can jump in quickly after a break.

curious how others feel
does Drupal complexity go away with regular use,
or is it just part of the system regardless?

Drupal 7 EOL hit in January and I've seen a lot of teams scrambling. Put together a step-by-step guide covering:

- Content type and node mapping
- Field migration with TypeScript
- Media and file handling
- Taxonomy migration
- Go-live checklist

Hope it helps someone: cosmicjs.com/blog/migrate-from-drupal-to-cosmic

Building an AI-assisted module with open-source AI-Task-Manager.