The useful part is that the answer arrives assembled: compatibility, the recommended release and the Composer line in a single response, so an assistant planning an upgrade does not have to be told which Drupal version a module supports. It reads drupal.org live, so the version it reports is the one published now.
A small TypeScript MCP server that fetches Drupal module information straight from drupal.org. Give it a module's machine name and it returns what you would otherwise open three browser tabs to find.
- Everything about one module from its machine name — `get_module_info`
- Name, description and current project status
- The latest recommended version and the Drupal versions it is compatible with
- The Composer command to install it, so the answer ends in something you can paste
- Download statistics, the project URL, and the module's own documentation or README
Node with `npm install` and `npm run build`; the client is pointed at the built `build/index.js` by absolute path. Nothing to authorize — the data comes from drupal.org. Documented for Claude Desktop and for Cline, Roo-Cline and Windsurf, and `npm run inspector` launches the MCP Inspector against the local build. The package is `drupal-modules-mcp` 0.1.0.
