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

@protoline/protoline

v0.1.7

Published

Protoline agent setup CLI.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

protolineprotoline

Keywords

Readme

@protoline/protoline

Protoline agent setup CLI for the hosted Protoline MCP server.

npx -y @protoline/protoline bootstrap
npx -y @protoline/protoline bootstrap --client codex
npx -y @protoline/protoline bootstrap --client claude
npx -y @protoline/protoline bootstrap --client all
npx -y @protoline/protoline login --client codex

The hosted MCP server remains the product contract:

https://app.protoline.ai/api/mcp

This package is a setup helper. It does not run a local MCP server and it does not make skills or slash commands mandatory.

Commands

Run commands through npx -y @protoline/protoline <command>.

  • bootstrap: configure the hosted MCP server and start OAuth where the client exposes a login command.
  • bootstrap --client codex: configure Codex and start Codex OAuth.
  • bootstrap --client claude: configure Claude Code; Claude Code starts OAuth inside Claude Code.
  • bootstrap --no-login: configure the MCP server without starting OAuth.
  • bootstrap --no-skills: skip installing local agent skills.
  • bootstrap --dry-run: print the client-specific setup commands without running them.
  • login: re-run OAuth for an already-configured MCP client.
  • login --client codex: re-run Codex OAuth without changing MCP server config.
  • login --client claude: print the Claude Code re-authentication path.
  • doctor: check common local setup state.

For Codex and Claude, bootstrap also writes a small local skill:

$CODEX_HOME/skills/protoline/SKILL.md
$CLAUDE_HOME/skills/protoline/SKILL.md

When the home variables are not set, the defaults are ~/.codex and ~/.claude. Restart Codex after installing or updating Codex skills. Restart Claude Code if the new skill does not appear.

Codex skills are model-invoked context, not / commands. In Codex, use $protoline or natural language such as "Show Protoline help." Claude Code may expose installed skills through /protoline.

Skills and client slash commands are optional shortcuts. Protoline still works through MCP tools when no companion skill is installed.

OAuth is the supported authorization path for hosted HTTP MCP.

License

Apache-2.0.

Release checks

Before publishing:

npm test
npm audit --omit=dev
npm pack --dry-run

Releases should be published from the trusted publishing workflow once the npm package has a trusted publisher configured.