drupal-modules-mcp MCP Server
# drupal-modules-mcp MCP Server
A Model Context Protocol server for retrieving Drupal module information from drupal.org.
This TypeScript-based MCP server provides tools to fetch detailed information about Drupal modules directly from drupal.org. It helps AI assistants and other tools to get accurate, up-to-date information about Drupal modules including version compatibility, installation instructions, and documentation.
## Features
### Tools
- `get_module_info` - Fetch comprehensive information about a Drupal module
- Requires the module's machine name as parameter
- Returns detailed module information including:
- Name and description
- Latest recommended version
- Download statistics
- Module status
- Composer installation command
- Drupal version compatibility
- Project URL
- Module documentation/README
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## Installation
### Claude Desktop
Add the server config to your Claude Desktop configuration:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"drupal-modules-mcp": {
"command": "/path/to/drupal-modules-mcp/build/index.js"
}
}
}
```
### Cline, Roo-Cline, and Windsurf
Add the server configuration to your IDE's settings:
1. Open the IDE settings
2. Navigate to the MCP Servers section
3. Add a new server with the following configuration:
```json
{
"drupal-modules-mcp": {
"command": "/path/to/drupal-modules-mcp/build/index.js"
}
}
```
Make sure to replace `/path/to/drupal-modules-mcp` with the actual path where you installed the server.
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as retrieving module information from drupal.org, making it distinct by default.
A single tool inherently follows a consistent naming pattern, as there are no other tools to compare it against. The name 'get_module_info' uses a clear verb_noun format, which is appropriate and unambiguous.
A server named 'drupal-modules-mcp' suggests a broader scope related to Drupal modules, but it only provides one tool for getting module information. This is too few for the apparent domain, as it lacks basic operations like searching, installing, or managing modules, making it feel incomplete and thin.
The tool surface is severely incomplete for a Drupal modules server. It only offers retrieval of module information, missing essential operations such as searching for modules, installing or updating them, or handling dependencies. This creates significant gaps that will limit agent functionality.