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

개발

종속성 설치:

지엑스피1

서버를 빌드하세요:

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