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

jmeter-docs-mcp

v0.1.0

Published

MCP server and CLI that gives AI agents access to the official Apache JMeter user manual, component and function reference, and .jmx test plan inspection.

Readme

jmeter-docs-mcp

MCP server and CLI that gives AI agents access to the official Apache JMeter user manual and inspects .jmx test plans.

Community project, not affiliated with the Apache Software Foundation.

Run as an MCP server

With no command, the binary starts an MCP server over stdio:

npx -y jmeter-docs-mcp@latest

Tools: jmeter_docs_search, jmeter_reference_lookup, jmeter_docs_fetch, jmeter_inspect_test_plan. See the repository README for client setup.

CLI

The package installs two equivalent binaries, jmeter-docs-mcp and jmeter-docs.

| Command | Description | |---------|-------------| | serve | Start the MCP server over stdio (default) | | search <query...> [-n, --limit <n>] [--json] | Search the user manual | | lookup <name...> [-k, --kind component\|function\|property] [--max-chars <n>] [--json] | Show the reference entry for a component, function, or property | | fetch <url> [-s, --section <heading>] [--max-chars <n>] [--json] | Fetch a jmeter.apache.org page, or one section, as markdown. Accepts page names such as functions.html#__time. | | sections [page] | List indexed sections, optionally for one page | | inspect <file.jmx> [--json] | Outline a test plan and report best-practice findings | | clear-cache | Delete cached documentation pages |

Examples:

jmeter-docs search "distributed testing firewall ports"
jmeter-docs lookup "JSON Extractor"
jmeter-docs lookup jmeter.save.saveservice.output_format --kind property
jmeter-docs fetch component_reference.html#HTTP_Request_Defaults
jmeter-docs inspect ./load-test.jmx --json

How it works

  • Fetches the 27 user manual pages from jmeter.apache.org, 6 at a time, the first time a search or lookup runs. Pages are cached on disk (see JMETER_DOCS_CACHE_DIR) and refreshed after JMETER_DOCS_CACHE_TTL_HOURS (default 168). A stale copy is used if the site is unreachable.
  • Converts each page to markdown and splits it at h1/h2, so every component and function is its own section with a deep link.
  • Ranks sections with BM25, weighting titles and breadcrumbs above body text.
  • jmeter_docs_fetch only fetches from jmeter.apache.org.
  • inspect parses the JMX locally and never executes anything.

Development

npm install
npm run build
npm test

Requires Node.js 22+.