MCP server for git.drupalcode.org (Drupal's GitLab instance), based on zereight/gitlab-mcp in its MCP OAuth proxy mode: add it to claude.ai (or any remote MCP client) and log in with your own git.drupalcode.org account — no personal access token to hand out.
Add https://drupalcode.piasecki.dev/mcp as a custom connector
(claude.ai: Settings → Connectors → Add custom connector). The OAuth flow
takes you through the git.drupalcode.org login/consent screen on first
connect; nothing else to configure.
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, self-host (below).
Native MCP support in git.drupalcode.org itself is tracked in drupal.org infrastructure #3557469 — once that lands, this proxy becomes unnecessary.
This server covers git.drupalcode.org (GitLab: code, merge requests, CI — authenticated, you act as yourself). Its sibling drupalorg-mcp covers drupal.org itself (issue queues, projects, maintainers via the public api-d7 REST API — read-only, no authentication). They complement each other: issue metadata and credits live on drupal.org, the code and MRs live on git.drupalcode.org. Use both for full coverage of a drupal.org project.
This repo contains no application source — the image is built from a
patched fork
of gitlab-mcp (see DEPLOYMENT.md for why; falls back to the upstream
zereight050/gitlab-mcp image once the fix is merged). What lives here is the
Docker Compose file, .env template, and deployment notes to run it behind a
shared Traefik edge proxy, the same pattern as
drupalorg-mcp.
See DEPLOYMENT.md if you want to run your own instance.