Drupal-Modules-MCP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_command_infoB | Get detailed information about a specific Drush command |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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 and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb_noun pattern (get_command_info).
A single tool is too few for a server named 'Drupal-Modules-MCP', which suggests a broader scope related to Drupal modules. This feels thin and incomplete for the apparent domain.
The tool surface is severely incomplete for a Drupal modules server. It only provides information about Drush commands, lacking any tools for listing, installing, updating, or managing modules, which are core operations in this domain.