drupalorg-mcp

MCP server for drupal.org's public api-d7 REST API. Read-only, no authentication required.

Usage

Add https://drupalorg.piasecki.dev/mcp as a custom connector (claude.ai: Settings → Connectors → Add custom connector), or point any remote MCP client at it. No login, no token — it's read-only.

The hosted instance comes with no guarantees — no SLA, no uptime promise. The maintainer keeps it running and up to date on a best-effort basis for the time being. If you need reliability, run it yourself (below).

Related MCP server: ls-apis-mcp

Tools

• resolve_project — resolve a project machine name (e.g. commerce) to its numeric project ID.

• resolve_user — resolve a drupal.org username to its numeric uid.

• list_issues — list issues, optionally filtered by project, status, priority, category, and/or author. Omit the project to search across all of drupal.org (e.g. "issues I created"). Paginated (50/page).

• get_issue — full details for a single issue by node ID, including related merge requests and credit metadata.

• get_issue_comments — all comments for an issue by node ID.

• list_my_projects — list projects (modules/themes/distributions/core/recipes) owned by a given user. Useful before listing "open issues on my project".

• get_project_maintainers — list a project's maintainers and their permissions, by machine name.

• find_maintained_projects — reverse maintainer lookup, scoped to one owner: given a user and an owner (e.g. centarro), returns which of the owner's projects that user maintains. drupal.org has no global user→projects maintainer endpoint, so this scans maintainers.json for every project authored by owner — not usable unscoped across all of drupal.org.

Tools that take an author/username/owner argument accept a username, a numeric uid, or the literal "me" (requires DRUPALORG_USERNAME env var, see below — local/stdio use only, not the hosted connector).

Related: drupalcode-mcp

• This server (drupalorg-mcp) covers drupal.org itself — issue queues, projects, maintainers — via the public api-d7 REST API; read-only, no authentication.

• Its sibling, drupalcode-mcp, covers git.drupalcode.org (Drupal's GitLab): code, merge requests, CI. It is authenticated — OAuth against git.drupalcode.org, each user acts as themselves.

• A hosted instance of drupalcode-mcp is available at https://drupalcode.piasecki.dev/mcp — add it as a custom connector in claude.ai or any remote MCP client. Best-effort, no SLA.

• The two complement each other: issue metadata and credits live on drupal.org, code and MRs live on git.drupalcode.org — use both for full coverage of a drupal.org project.

Running it yourself

Requirements

• Node.js 18+ (uses global fetch)

Quick start (Claude Code, stdio)

claude mcp add drupalorg -s user -e DRUPALORG_USERNAME=your-username -- npx -y drupalorg-mcp

-e DRUPALORG_USERNAME=... is optional — set it to enable author: "me" in tool calls instead of passing your username every time. Verify with claude mcp list.

Add to other MCP clients

E.g. Claude Desktop's config:

{
  "mcpServers": {
    "drupalorg": {
      "command": "npx",
      "args": ["-y", "drupalorg-mcp"],
      "env": { "DRUPALORG_USERNAME": "your-username" }
    }
  }
}

DRUPALORG_USERNAME is optional — set it to enable author: "me" in tool calls instead of passing your username every time.

Running from a local checkout

For development, or if you'd rather not fetch from npm on every launch:

npm install
node index.js

See CONTRIBUTING.md for the development workflow.

Hosting your own remote instance

The stdio server above only works with local MCP clients. To run your own https://.../mcp endpoint for claude.ai custom connectors or other remote MCP clients, see DEPLOYMENT.md for the Docker + reverse-proxy setup.

Notes

• The UA header in server-core.js identifies this tool to drupal.org's API — update it if you fork/republish under a different repo.

• All status/priority/category values are translated from drupal.org's internal numeric IDs to readable labels.

Contributing

See CONTRIBUTING.md for development setup, code structure, and publishing steps.

Built with Claude Code — code, docs, CI workflow, and npm packaging were written by Claude in collaboration with the repo owner.