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

@robotyxx/robotyx-mcp

v0.1.1

Published

MCP server for Robotyx — read your test plans (TestSuites, TestCases, functional TestSteps) and recorded Workflows into Claude Code or any MCP client, e.g. to generate WebDriverIO/Playwright tests in your own repo. Bring your own rx_ API key.

Readme

robotyx-mcp

Stdio MCP server that wraps Robotyx's REST API. Lets Claude Code / Claude Desktop browse recorded workflows, refine their TestSteps into grouped functional steps ("clicks 1-7 → Log in as admin"), and push the result back — without leaving the chat.

No new business logic lives here. Every tool is a thin wrapper around an existing endpoint the Robotyx web UI also uses.

Tools

| Tool | Wraps | Notes | |------|-------|-------| | list_workflows | GET /api/workflows | Summary rows. | | get_workflow | GET /api/workflows/:id | Screenshots stripped by default. Pass include_screenshots: "all" or "indices" + screenshot_step_indices: [1,3,5] when you need visual context. | | list_testsuites | GET /api/testsuites | | | get_testsuite | GET /api/testsuites/:id | Includes cases + their steps. | | create_testsuite | POST /api/testsuites | | | add_test_case | POST /api/testsuites/:id/cases | Optionally links a Workflow id. | | set_test_steps | POST /api/testsuites/:id/cases/:caseId/import-mapping | The refine path. Body shape mirrors the UI's Excel import — pass workflow_step_ids (full ordered list from get_workflow) + mappings: [{description, expected_result, workflow_step_indices: [1,2,3]}]. | | merge_step | POST .../steps/:stepId/merge | | | split_step | POST .../steps/:stepId/split | | | create_defect | POST /api/defects | |

Wire-up — Claude Code

Drop a .mcp.json in your workspace root (already done for ai-automation-platform/ and footprint-platform/):

{
  "mcpServers": {
    "robotyx": {
      "command": "npx",
      "args": ["-y", "tsx", "C:\\Users\\…\\ai-automation-platform\\robotyx-mcp\\src\\index.ts"],
      "env": {
        "ROBOTYX_URL": "http://localhost:3001",
        "ROBOTYX_API_KEY": "${ROBOTYX_API_KEY}"
      }
    }
  }
}

Then in PowerShell (once per machine):

[Environment]::SetEnvironmentVariable("ROBOTYX_API_KEY", "rx_…", "User")

Restart Claude Code so it picks up the new MCP. Verify with /mcp — you should see robotyx: ✓ connected (10 tools).

Wire-up — Claude Desktop

Add the same mcpServers block to %APPDATA%\Claude\claude_desktop_config.json and restart the app.

Typical refine loop

  1. list_workflows → pick a workflow id.
  2. get_workflow (no screenshots) → AI proposes a grouping based on step descriptions + action types.
  3. get_workflow with include_screenshots: "indices" and the ambiguous step indices → AI disambiguates visually.
  4. Either add_test_case (linking the workflow) or pick an existing one from get_testsuite.
  5. set_test_steps with the proposed mapping → done.

Token budget

A 30-step browser recording with full-page PNGs is ~200-400k tokens with include_screenshots: "all". Always start with "none", then use "indices" to fetch only the screenshots you need. The server strips footprint_* bookkeeping keys (raw a11y dumps, console logs) unconditionally.