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バージョンの互換性

      • プロジェクトURL

      • モジュールドキュメント/README

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"
    }
  }
}

クライン、ルークライン、ウィンドサーフィン

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