Skip to main content
Glama
enesjakozh
Cleversoft-IT

drupal-modules-mcp MCP Server

by Cleversoft-IT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

drupal-modules-mcp MCP 服务器

用于从 drupal.org 检索 Drupal 模块信息的模型上下文协议服务器。

这款基于 TypeScript 的 MCP 服务器提供了一些工具，可以直接从 drupal.org 获取 Drupal 模块的详细信息。它可以帮助 AI 助手和其他工具获取 Drupal 模块的准确、最新信息，包括版本兼容性、安装说明和文档。

特征

工具

  • get_module_info - 获取有关 Drupal 模块的综合信息

    • 需要模块的机器名称作为参数

    • 返回详细的模块信息包括：

      • 名称和描述

      • 最新推荐版本

      • 下载统计数据

      • 模块状态

      • Composer 安装命令

      • Drupal 版本兼容性

      • 项目网址

      • 模块文档/自述文件

Related MCP server: MCP Server

发展

安装依赖项：

npm install

构建服务器：

npm run build

对于使用自动重建的开发：

npm run watch

安装

克劳德桌面

将服务器配置添加到您的 Claude Desktop 配置中：

在 MacOS 上： ~/Library/Application Support/Claude/claude_desktop_config.json在 Windows 上： %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "drupal-modules-mcp": {
      "command": "/path/to/drupal-modules-mcp/build/index.js"
    }
  }
}

Cline、Roo-Cline 和 Windsurf

将服务器配置添加到 IDE 的设置中：

  1. 打开 IDE 设置

  2. 导航至 MCP 服务器部分

  3. 添加具有以下配置的新服务器：

    {
  "drupal-modules-mcp": {
    "command": "/path/to/drupal-modules-mcp/build/index.js"
  }
}

确保将/path/to/drupal-modules-mcp替换为您安装服务器的实际路径。

调试

由于 MCP 服务器通过 stdio 进行通信，调试起来可能比较困难。我们推荐使用MCP Inspector ，它以包脚本的形式提供：

npm run inspector

检查器将提供一个 URL 来访问浏览器中的调试工具。

Available Tools

1 tool
get_module_infoC

Get information about a Drupal module from drupal.org

ParametersJSON Schema
NameRequiredDescriptionDefault
module_nameYesMachine name of the Drupal module

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get information'), but doesn't mention potential rate limits, authentication requirements, error conditions, or what format the information is returned in. This leaves significant gaps for an agent to understand how to use it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple tool with one parameter and gets straight to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned, potential limitations, or error handling. While the purpose is clear, the behavioral context is too sparse for an agent to use this tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, clearly documenting the single required parameter. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get information') and the resource ('a Drupal module from drupal.org'), making the purpose immediately understandable. It doesn't need to differentiate from siblings since none exist, but it could be slightly more specific about what type of information is retrieved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It simply states what the tool does without context about appropriate use cases or constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedget_module_info
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches