npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gitlab-http-api-mcp

v0.2.1

Published

MCP server for GitLab over HTTP API (projects, issues, MRs, CI pipelines, jobs)

Readme

gitlab-http-api-mcp

MCP (Model Context Protocol) server for GitLab that talks directly to the GitLab HTTP API using GITLAB_API_URL and GITLAB_PERSONAL_ACCESS_TOKEN. Tools cover projects, issues (including notes), merge requests (create/update/merge/diffs), and CI pipelines & jobs.

Requirements

  • Node.js 18+
  • Accessible GitLab HTTP API and a personal access token with sufficient permissions.

Install

From source (GitHub)

git clone https://github.com/rkorablin/gitlab-http-api-mcp.git
cd gitlab-http-api-mcp
npm install

From npm

As a local dependency:

npm install gitlab-http-api-mcp

Or globally (for npx / CLI usage):

npm install -g gitlab-http-api-mcp

Configuration

Environment variables:

  • GITLAB_API_URL — base API URL, for example https://gitlab.example.com/api/v4
  • GITLAB_PERSONAL_ACCESS_TOKEN — GitLab personal access token

Usage

Standalone (stdio)

export GITLAB_API_URL="https://gitlab.example.com/api/v4"
export GITLAB_PERSONAL_ACCESS_TOKEN="glpat-..."
node server.mjs

Cursor / MCP host

Add the server to your MCP config (for example .cursor/mcp.jsonmcpServers).

Option 1: Local clone

"gitlab": {
  "command": "node",
  "args": ["/absolute/path/to/gitlab-http-api-mcp/server.mjs"],
  "env": {
    "GITLAB_API_URL": "https://gitlab.example.com/api/v4",
    "GITLAB_PERSONAL_ACCESS_TOKEN": "glpat-..."
  }
}

Option 2: npm / npx

If installed globally:

"gitlab": {
  "command": "gitlab-http-api-mcp",
  "env": {
    "GITLAB_API_URL": "https://gitlab.example.com/api/v4",
    "GITLAB_PERSONAL_ACCESS_TOKEN": "glpat-..."
  }
}

Or via npx (рекомендуется для автоподтягивания новых версий):

"gitlab": {
  "command": "npx",
  "args": ["--yes", "--prefer-online", "gitlab-http-api-mcp@latest"],
  "env": {
    "GITLAB_API_URL": "https://gitlab.example.com/api/v4",
    "GITLAB_PERSONAL_ACCESS_TOKEN": "glpat-..."
  }
}

Почему @latest и --prefer-online: без тега версии npx может долго использовать старый кэш. Явный @latest + опрос registry при старте даёт актуальный патч после публикации в npm. Флаги нужно передавать до имени пакета (см. npm help npx).

Tools (summary)

| Area | Tools | |------|--------| | User | gitlab_get_current_user | | Projects | gitlab_list_projects, gitlab_get_project | | Issues | gitlab_list_issues, gitlab_get_issue, gitlab_create_issue, gitlab_update_issue, gitlab_list_issue_notes, gitlab_create_issue_note | | Merge requests | gitlab_list_merge_requests, gitlab_get_merge_request, gitlab_create_merge_request, gitlab_update_merge_request, gitlab_merge_merge_request, gitlab_get_merge_request_changes | | Pipelines | gitlab_list_pipelines, gitlab_get_pipeline, gitlab_create_pipeline, gitlab_retry_pipeline, gitlab_cancel_pipeline | | Jobs | gitlab_list_pipeline_jobs, gitlab_get_job_trace, gitlab_retry_job, gitlab_play_job |

Pipeline and job IDs are numeric (from the API). MR and issue identifiers are IID (per-project internal id).