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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@marianarocha/zephyr-scale-mcp

v0.2.3

Published

Internal MCP server for Zephyr Scale test management (Cloud & Data Center)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

hmaldonadovillahmaldonadovillamarianarochamarianarocha

Keywords

mcpmodel-context-protocolzephyrzephyr-scalejiraqatest-management

Readme

Internal Zephyr Scale MCP Server

This is an internal forked MCP server for Zephyr Scale (Jira Cloud & Data Center) used by the BCS platform. It provides tools for test case management, test runs, and folder operations with robust, ID-based folder filtering and is now published as the npm package @marianarocha/zephyr-scale-mcp.

Key differences vs upstream:

  • Published as a lightweight npm package that can be executed via npx (no need to bundle the source inside consumers)
  • Folder utilities with exact folder matching by folder ID
  • include_subfolders flag for folder queries

Build

  • npm install
  • npm run build

Publish

Use the following steps to build and publish a new version to npm (requires access to the @marianarocha scope):

npm login
npm version <patch|minor|major>
npm run build
npm publish --access public

Run

  • npx -y @marianarocha/zephyr-scale-mcp (stdio transport)
  • or node build/index.js when running from a cloned repository

Environment

  • ZEPHYR_BASE_URL (required)
  • ZEPHYR_API_KEY (required)
  • Optional advanced tuning:
    • ZEPHYR_METADATA_CACHE_TTL_MS – cache TTL for status/priority catalogs (default 5 minutes)
    • ZEPHYR_AUTOMATED_STATUS_KEYWORDS – comma-separated keywords that should count as automated (default: automated,automation in progress,automatizado,em automação)
    • ZEPHYR_MANUAL_STATUS_KEYWORDS – comma-separated keywords that should count as manual (default keeps legacy values such as manual,deploy,aprovado,rascunho)

Metadata-driven automation

  • The MCP now loads Zephyr status/priority catalogs at runtime and exposes them as resources:
    • zephyr://metadata/statuses
    • zephyr://metadata/priorities
    • zephyr://metadata/automation_rules
  • get_test_case and search_test_cases_by_folder responses are enriched with:
    • statusName, priorityName, and automationLabel
    • automationSummary aggregates identical to the previous Python-side enhancement
  • Python consumers no longer need ZephyrStatusMappingUseCase; automation logic lives inside the MCP so downstream services can just forward the enriched payloads.