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

techdoc-search-mcp

v0.1.0

Published

MCP server that searches up-to-date technical documentation and API references (BYOK — bring your own Tavily API key)

Readme

TechDoc-Search-MCP

An MCP (Model Context Protocol) server that lets AI coding assistants (Claude Code, Cursor, Claude Desktop, …) search up-to-date official documentation and trusted articles for any technology, right from your editor.

  • 🔍 One tool: search_tech_docs — search by technology + topic, get LLM-ready Markdown back
  • 🔑 BYOK (Bring Your Own Key): uses your own free Tavily API key — zero server cost
  • 🛡️ Built-in timeout, retry, and rate-limit handling with actionable error messages

Quick start

1. Get a free Tavily API key

Sign up at app.tavily.com — the free tier includes 1,000 credits/month, no credit card required. Copy your key (starts with tvly-).

2. Add the server to your MCP client

Claude Code

claude mcp add techdoc-search --env TAVILY_API_KEY=tvly-xxxx -- npx -y techdoc-search-mcp

Cursor (.cursor/mcp.json) / Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "techdoc-search": {
      "command": "npx",
      "args": ["-y", "techdoc-search-mcp"],
      "env": { "TAVILY_API_KEY": "tvly-xxxx" }
    }
  }
}

3. Use it

Ask your AI assistant something like:

"Search the latest Next.js 14 docs about Server Actions error handling"

Tool reference

search_tech_docs

| Argument | Type | Required | Description | |---|---|---|---| | technology | string | ✅ | Technology/library name, including version. e.g. "Next.js 14" | | topic | string | ✅ | Topic, API name, or error message. e.g. "Server Actions error handling" | | max_results | number (1–10) | — | Number of results (default: 5) | | include_domains | string[] | — | Restrict to specific domains, e.g. ["nextjs.org"] | | recency_days | number | — | Only results published within this many days |

Returns a single Markdown document: ranked results with source domain, publish date, relevance score, and extracted page content.

Configuration (environment variables)

| Variable | Default | Description | |---|---|---| | TAVILY_API_KEY | — | Required. Your Tavily API key | | SEARCH_PROVIDER | tavily | Search backend (exa support planned) | | TECHDOC_TIMEOUT_MS | 10000 | Per-request timeout in milliseconds |

Your API key is only sent to the search provider and never logged.

Development

npm install
npm test          # unit tests (vitest)
npm run build     # compile to dist/
npm run dev       # run from source (tsx)

# Interactive testing with MCP Inspector
npx @modelcontextprotocol/inspector npx tsx src/index.ts

License

MIT