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-issue-creator-mcp

v1.0.8

Published

MCP server for creating GitLab issues (self-hosted compatible).

Downloads

724

Readme

GitLab Issue Creator (MCP Server)

An MCP server that creates GitLab issues, compatible with self-hosted instances (default: https://gitlab.com).

Tools

  • create_gitlab_issue
    • Required: title, projectId
    • Optional: description, labels, assigneeIds, milestoneId, dueDate, confidential
    • Optional overrides: gitlabUrl (token must come from env)

Configuration

Set env vars (recommended):

  • GITLAB_URL (defaults to https://gitlab.com)
  • GITLAB_TOKEN (required)

See .env.example.

Install (from npm)

Prerequisites:

  • Node.js >= 18

Install into an existing project:

npm install gitlab-issue-creator-mcp -D

VS Code MCP setup (npm install)

VS Code MCP servers are typically configured in .vscode/mcp.json. If you installed this package into a project, point VS Code at the installed dist/index.js and use envFile to load secrets from a local .env file:

{
  "servers": {
    "gitlab-issue-creator-mcp": {
      "type": "stdio",
      "command": "node",
      "args": ["./node_modules/gitlab-issue-creator-mcp/dist/index.js"],
      "envFile": "${workspaceFolder}/.env"
    }
  }
}

Notes:

  • Some clients require an absolute path for args[0]. In that case, replace the relative ./node_modules/... path with an absolute path on your machine.
  • GITLAB_TOKEN is required; GITLAB_URL defaults to https://gitlab.com.
  • Keep .env out of source control (this repo’s .gitignore already ignores it). Start from the template: cp .env.example .env.

Develop (from source)

Recommended flow for teammates:

  1. Clone this repo
  2. Install + build: npm install && npm run build
  3. Open the repo folder in VS Code
  4. Start the MCP server (Chat tool picker or MCP: List Servers)

Develop / Build

  • Install: npm install
  • Build: npm run build
  • Run: GITLAB_TOKEN=... npm start

If you want to run the server from a local clone (instead of installing from npm), build it and point your MCP client at dist/index.js.

Notes

  • Prefer a Project Access Token or a PAT scoped as narrowly as possible.
  • This server prints no secrets, but your MCP client should keep tokens out of logs.

License

MIT. See LICENSE.