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

testray-mcp

v1.0.2

Published

MCP server for TestRay (Requirements and Test Management for Jira)

Readme

testray-mcp

MCP server for TestRay and Jira work-item retrieval.

What this server now supports

  • TestRay test case operations (existing tools).
  • TestRay test plan cycle listing (existing tool).
  • Jira account ID discovery (existing tool).
  • Generic work-item retrieval by key with automatic routing:
    • testray_get_issue
  • List available Jira work item types:
    • testray_list_work_item_types
  • Search Jira issues by work item type:
    • testray_search_work_items_by_type
  • Direct helpers for Jira Task and Epic:
    • testray_get_task
    • testray_get_epic

Required configuration

Set these environment variables in your MCP config for testray-mcp:

  • TESTRAY_API_TOKEN
  • TESTRAY_SHARED_SECRET
  • TESTRAY_JIRA_USER_ID
  • TESTRAY_BASE_URL (optional, default https://testray.goldfingerholdings.onl)
  • TESTRAY_JIRA_BASE_URL (optional, default https://igel-jira.atlassian.net)
  • TESTRAY_JIRA_EMAIL (optional; required only for Jira list/search/get fallback operations)
  • TESTRAY_JIRA_PAT (optional; required only for Jira list/search/get fallback operations)

Usage examples

1) List work item types

Tool: testray_list_work_item_types

Input:

{
  "projectKey": "QCL"
}

2) Search by work item type

Tool: testray_search_work_items_by_type

Input:

{
  "issueType": "testcase",
  "projectKey": "QCL",
  "maxResults": 25,
  "startAt": 0
}

3) Get any work item by key

Tool: testray_get_issue

Input:

{
  "issueKey": "QCL-123",
  "preferSource": "auto"
}

preferSource options:

  • auto: TestRay for testcase and test plan, Jira for others.
  • testray: force TestRay path (if mapped).
  • jira: force Jira retrieval.

4) Get task or epic directly

Tool: testray_get_task

{
  "issueKey": "QCL-456"
}

Tool: testray_get_epic

{
  "issueKey": "QCL-789"
}

Build and run

npm run build
npm start

Notes

  • If TESTRAY_JIRA_USER_ID is unknown, use testray_get_my_jira_account_id.
  • Jira list/search/get operations require TESTRAY_JIRA_EMAIL and TESTRAY_JIRA_PAT.
  • Core TestRay APIs (for example testray_get_test_steps) work with only:
    • TESTRAY_API_TOKEN
    • TESTRAY_SHARED_SECRET
    • TESTRAY_JIRA_USER_ID