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

common-qa-mcp

v0.10.1

Published

Common QA MCP — one product-neutral MCP that routes test-case lifecycle requests to Walnut or SimplifyQA for any AI client. Launch over stdio via npx; install the Walnut QA agent with `init-agents`.

Readme

Common QA MCP

One product-neutral MCP that any AI client (Claude Code, Cursor, Windsurf, VS Code, Codex, Devin) connects to with a URL + token to drive the whole test-case lifecycle — discover · author · record · run · triage — against Walnut or SimplifyQA. The client sees one tool vocabulary regardless of the product behind it.

Install

Nothing to clone or build — clients launch it over stdio with npx. Requires Node ≥ 20.

Add it to your client's MCP config (.mcp.json for Claude Code / Cursor / Windsurf):

{
  "mcpServers": {
    "common-qa-mcp": {
      "command": "npx",
      "args": ["-y", "common-qa-mcp"],
      "env": {
        "QA_MCP_PROVIDER": "walnut",
        "QA_BASE_URL": "https://<your-backend>",
        "QA_MCP_URL": "http://127.0.0.1:4050/mcp",
        "QA_MCP_TOKEN": "<your-token>",
        "QA_MCP_PROJECT_ID": "<optional-project-id>"
      }
    }
  }
}

| Env var | Required | Purpose | |---|:---:|---| | QA_MCP_PROVIDER | — | walnut (default) or simplifyqa. | | QA_BASE_URL | ✓* | Product backend REST — drives discover / author / run / triage (no agent needed). | | QA_MCP_URL | ✓* | Your local agent's /mcp — adds recording + journal editing (browser / mainframe). | | QA_MCP_TOKEN | ✓ | Raw auth token (JWT — no Bearer prefix). | | QA_MCP_PROJECT_ID | — | Pin a default project; omit and you'll be asked (change anytime with qa_switch_project). |

* Set QA_BASE_URL for the lifecycle over direct REST, and QA_MCP_URL to add recording. Set both for the full experience, or only QA_BASE_URL for a zero-agent setup (no recording). With neither set it starts offline — draft authoring only — and you connect later from chat with qa_connect.

Recording (web / mainframe/ mobile) runs on the local agent, so QA_MCP_URL must point at a running agent.

Install the QA agent (optional)

Drops a QA persona + tool guidance into your project so the client knows how to drive these tools:

npx common-qa-mcp init-agents --loop=claude   # claude | cursor | windsurf | vscode | codex | devin | all
#   --server-name <name>   # must match your MCP server name (default: common-qa-mcp)

Use it

Reload your client, then drive it in plain language:

  • "List my projects" → "switch to project X"
  • "Record a login test on web" → answer the setup questions → review the draft → "save it"
  • "Run TC_123 on cloud" · "show me the login stories" · "add a loop around steps 3–5 of TC_42"