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

@oss-autopilot/mcp

v5.2.0

Published

MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools

Readme

@oss-autopilot/mcp

MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools for any MCP-compatible client.

npm Node License

What It Provides

| Feature | Count | Description | |---------|-------|-------------| | Tools | 28 | daily, status, search, vet, vet-list, track, compliance-score, repo-vet, comments, post, claim, config, init, setup, check-setup, startup, shelve, unshelve, dismiss, undismiss, move, state-show, state-sync, state-unlink, guidelines-get, guidelines-store, guidelines-reset, guidelines-fetch-corpus | | Resources | 6 | oss://status, oss://config, oss://prs, oss://prs/shelved, oss://pr/{owner}/{repo}/{number}, oss://repo/{owner}/{repo}/guidelines | | Prompts | 4 | triage (PR prioritization), respond-to-pr (draft response), find-issues (discover issues), extract-learnings (distill per-repo guidance from past PR feedback) |

Supports stdio (default) and Streamable HTTP transports.

Prerequisites

  • Node.js 22+
  • GitHub CLI authenticated (gh auth login)

Quick Start

# 1. Add the server to your MCP client (see config examples below)

# 2. From your MCP client, call the `init` tool once with your GitHub username
#    (this writes ~/.oss-autopilot/state.json).

# 3. Use the other tools — e.g. `daily` to check your PRs, `search` to find issues.

Client Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "oss-autopilot": {
      "command": "npx",
      "args": ["@oss-autopilot/mcp@latest"]
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project or global config:

{
  "mcpServers": {
    "oss-autopilot": {
      "command": "npx",
      "args": ["@oss-autopilot/mcp@latest"]
    }
  }
}

Codex CLI

codex mcp add oss -- npx @oss-autopilot/mcp@latest

Windsurf

Add to your Windsurf MCP config:

{
  "mcpServers": {
    "oss-autopilot": {
      "command": "npx",
      "args": ["@oss-autopilot/mcp@latest"]
    }
  }
}

Streamable HTTP (any client)

Run the server in HTTP mode instead of stdio:

npx @oss-autopilot/mcp@latest --http --port 3001

The server listens at http://127.0.0.1:3001/mcp and accepts POST requests.

Authentication

HTTP mode requires a bearer token on every request (stdio mode does not — it inherits the parent process identity). On first --http startup, the server generates a random 32-byte token and writes it to ~/.oss-autopilot/mcp.token with 0600 permissions. The path and "newly generated" marker are logged to stderr at startup.

Every HTTP client must send:

Authorization: Bearer <contents of ~/.oss-autopilot/mcp.token>

Requests without a valid Authorization header return 401. The Bearer scheme is case-insensitive per RFC 7235; the token value itself is compared byte-for-byte in constant time. Requests with a non-loopback Host header return 403 (DNS-rebinding defense). Requests must declare a numeric Content-Length ≤ 1 MiB — missing, non-numeric, or oversize Content-Length values return 413.

The token persists across restarts. To rotate, delete the file and restart — a new token will be generated. To relocate the token (e.g. for multi-user or CI setups), set OSS_AUTOPILOT_MCP_TOKEN_PATH to the desired absolute path before starting the server.

Tools Reference

| Tool | Description | Read-only | |------|-------------|-----------| | daily | Run daily PR monitoring check with prioritized summary | No | | status | Show current PR tracking status | Yes | | search | Search GitHub for contributable issues | Yes | | vet | Analyze an issue for contribution suitability | Yes | | vet-list | Re-vet all available issues in the curated issue list | No | | track | Fetch metadata for a pull request (informational; nothing persists) | No | | compliance-score | Score a PR against opensource.guide best practices (#1245) | Yes | | repo-vet | Compute the repo health rubric (1–10 + verdict) for owner/repo (#1271) | Yes | | comments | Fetch and display PR comments | Yes | | post | Post a comment on an issue or PR | No | | claim | Claim an issue by posting a comment | No | | config | Get or set configuration values | No | | init | Initialize with a GitHub username | No | | setup | Configure preferences (languages, interests) | No | | check-setup | Check if setup is complete | Yes | | startup | Run startup checks (auth, state, config) | No | | shelve | Temporarily hide a PR from daily checks | No | | unshelve | Return a shelved PR to active monitoring | No | | dismiss | Dismiss an issue from notifications | No | | undismiss | Re-enable notifications for a dismissed issue | No | | move | Move a PR between states (attention, waiting, shelved, auto) | No | | state-show | Show current state persistence mode (local or Gist) and sync status | Yes | | state-sync | Force push current state to the backing Gist | No | | state-unlink | Disconnect from Gist persistence and switch to local-only mode | No | | guidelines-get | Read per-repo learning guidelines extracted from past PR feedback | Yes | | guidelines-store | Persist per-repo guidelines (8 KB cap; requires Gist mode) | No | | guidelines-reset | Tombstone the guidelines file for a repo | No | | guidelines-fetch-corpus | Fetch raw PR comment bundles for the host's extract-learnings prompt to consume | No |

Resources Reference

| Resource URI | Description | |-------------|-------------| | oss://status | PR tracking status (cached local state) | | oss://config | Current configuration | | oss://prs | Active open PRs from last daily digest | | oss://prs/shelved | Shelved PRs | | oss://pr/{owner}/{repo}/{number} | Detail for a specific PR | | oss://repo/{owner}/{repo}/guidelines | Per-repo learning guidelines (markdown) |

Prompts Reference

| Prompt | Args | Description | |--------|------|-------------| | triage | none | Fetches daily digest and builds a prioritized triage list | | respond-to-pr | prUrl | Fetches PR comments and context for drafting a response | | find-issues | maxResults? | Searches for issues ranked by viability score | | extract-learnings | repo, corpus, existingGuidelines? | Distills durable per-repo guidance from raw PR comment bundles (#867) |

Programmatic Usage

The server can also be imported and used as a library:

import { createServer } from '@oss-autopilot/mcp';

const server = createServer();
// Connect to your own transport

More Information

See the main repository README for the full documentation, including the Claude Code plugin, CLI usage, dashboard, and contributing guide.

License

MIT