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

mcp-sonarqube-launcher

v1.1.0

Published

Node.js MCP stdio launcher with optional bundled SonarQube MCP JAR—publish with vendor/ for npx-only installs.

Readme

mcp-sonarqube-launcher

Node.js stdio launcher for a SonarQube MCP server shipped as a .jar (runs java -jar …). Publish it to npm so teams can run npx mcp-sonarqube-launcher with env only, or ship the JAR under vendor/ so consumers do not need a separate path.


See also (sibling projects)

| Project | Purpose | |---------|---------| | GitHub Enterprise MCP launcher | mcp-github-enterprise-launcher — same pattern for a github-mcp-server binary. | | Jira MCP | npm @svasimahmed283/jira-mcp-oauth — full MCP server for Jira. | | Confluence MCP | npm @svasimahmed283/confluence-sso-mcp — full MCP server for Confluence. |


Prerequisites

| Requirement | Notes | |-------------|--------| | Node.js 18+ | Runs this launcher. | | Java | java on PATH or JAVA_HOME set—the launcher does not embed a JRE. | | SonarQube MCP JAR | Built separately. This package spawns java -jar unless you rely on vendor/. | | SONARQUBE_URL, SONARQUBE_TOKEN, STORAGE_PATH | Usually required by the upstream JAR—set in MCP env. |


Quick start (end users)

A — JAR bundled in npm (vendor/)

After publish includes vendor/sonarqube-mcp-server.jar:

"sonarqube": {
  "command": "npx",
  "args": ["--yes", "mcp-sonarqube-launcher"],
  "env": {
    "SONARQUBE_URL": "https://sonar.mycompany.com/",
    "SONARQUBE_TOKEN": "<secret>",
    "STORAGE_PATH": "C:\\\\path\\\\to\\\\storage"
  }
}

No SONARQUBE_MCP_JAR when the bundled file is present.

B — JAR only on disk

"env": {
  "SONARQUBE_MCP_JAR": "C:\\\\tools\\\\sonarqube-mcp-server\\\\build\\\\libs\\\\sonarqube-mcp-server.jar",
  "SONARQUBE_URL": "https://sonar.mycompany.com/",
  "SONARQUBE_TOKEN": "<secret>",
  "STORAGE_PATH": "C:\\\\path\\\\to\\\\storage"
}

Maintainer workflow

| Step | Command | |------|---------| | Copy JAR into vendor/ | node scripts/bundle-sonarqube.mjs C:\path\to\sonarqube-mcp-server.jar | | Verify | node scripts/verify-bundle.mjs (part of prepublishOnly) | | Dry pack without JAR | set SKIP_BUNDLE_CHECK=1 then npm pack | | Smoke test | Set SONARQUBE_TOKEN (and URL/storage as needed), then npm run smoke-test | | Publish | npm publish --access public |

Git: vendor/*.jar is gitignored; npm publish still includes it if the file exists when you run npm pack / npm publish.


Environment

| Variable | Description | |----------|-------------| | SONARQUBE_MCP_JAR | Overrides bundled vendor/sonarqube-mcp-server.jar. | | JAVA_BIN | Java executable (defaults to java or JAVA_HOME/bin/java). | | SONARQUBE_JAVA_OPTS | Space-separated JVM flags before -jar (e.g. -Xmx512m). | | SONARQUBE_URL, SONARQUBE_TOKEN, STORAGE_PATH | Passed through to the JVM process (as required by your Sonar MCP build). |


npm scripts

| Script | Purpose | |--------|---------| | npm run bundle | Runs bundle-sonarqube.mjs (argv or SONARQUBE_MCP_JAR_SRC). | | npm run smoke-test | Short-lived spawn test; set SONARQUBE_TOKEN first. |


Troubleshooting

| Symptom | What to do | |---------|------------| | No JAR found | Run npm run bundle or set SONARQUBE_MCP_JAR. | | java not found | Install a JRE/JDK and ensure JAVA_HOME or PATH is set. | | prepublishOnly fails | Add vendor/sonarqube-mcp-server.jar, or use SKIP_BUNDLE_CHECK=1 for dry runs only. |


License

MIT