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

document-search-tool

v1.0.0

Published

Document search tool for parsing documents and performing web searches

Readme

Document Search Tool

A standalone document search tool that can be used as a subprocess for document parsing and web search functionality.

Features

  • parseDocumentLink: Parse documents from URLs using LlamaParse
  • googleSearch: Perform web searches using Perplexity AI API

Installation

npm install

Build

npm run build

Usage

As a Subprocess

The tool can be executed as a subprocess with command line arguments:

node dist/index.js <command> <args_json>

Examples

Parse a document:

node dist/index.js parseDocumentLink '{"document_link": "https://example.com/document.pdf"}'

Perform a web search:

node dist/index.js googleSearch '{"query": "latest shipping regulations"}'

As a Module

import { DocumentSearchSubprocess } from './dist/index.js';

const subprocess = new DocumentSearchSubprocess();
const result = await subprocess.testCommand('googleSearch', { query: 'test query' });
console.log(result);

Environment Variables

Create a .env file in the root directory with the following variables:

LLAMA_PARSE_URL=https://api.llamaparse.com/parse
LLAMA_API_KEY=your_llama_api_key
VENDOR_MODEL=your_vendor_model
S3_API_TOKEN=your_s3_api_token
S3_GENERATE_HTML_URL=your_s3_generate_html_url
PERPLEXITY_API_KEY=your_perplexity_api_key

Development

# Build and run in development mode
npm run dev

# Clean build artifacts
npm run clean

Integration with Main MCP Server

To use this tool as a subprocess from the main MCP server, you can spawn it as a child process:

import { spawn } from 'child_process';
import { promisify } from 'util';

async function callDocumentSearchTool(command: string, args: any): Promise<any> {
    return new Promise((resolve, reject) => {
        const child = spawn('node', [
            'path/to/document-search-tool/dist/index.js',
            command,
            JSON.stringify(args)
        ]);

        let stdout = '';
        let stderr = '';

        child.stdout.on('data', (data) => {
            stdout += data.toString();
        });

        child.stderr.on('data', (data) => {
            stderr += data.toString();
        });

        child.on('close', (code) => {
            if (code === 0) {
                try {
                    const result = JSON.parse(stdout);
                    resolve(result);
                } catch (error) {
                    reject(new Error(`Failed to parse result: ${error}`));
                }
            } else {
                reject(new Error(`Subprocess failed with code ${code}: ${stderr}`));
            }
        });

        child.on('error', (error) => {
            reject(error);
        });
    });
}