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

@cofoundy/docs

v0.1.0

Published

CLI for docs.cofoundy.dev — installs the MCP server config + publish skill into Claude Code / Cursor / Codex.

Downloads

27

Vulnerabilities

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

Links

Maintainers

styreepstyreep

Keywords

cofoundymcpdocscliclaude-codecursorcodex

Readme

@cofoundy/docs

CLI for docs.cofoundy.dev. One command installs the MCP server config + publish skill into Claude Code, Cursor, or Codex.

Install

npx @cofoundy/docs install

Auto-detects the editor by walking up the CWD for .claude/, .cursor/, or .codex/. Override with --target=claude|cursor|codex|all.

Idempotent — re-run safely. Existing MCP server entries in your config are preserved.

Commands

install [--target=auto|claude|cursor|codex|all]

Writes the cofoundy-docs MCP server entry into your editor's MCP config:

| Platform | Config path | |---|---| | Claude Code | .mcp.json (project) or ~/.claude.json | | Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json | | Codex | .codex/config.toml (project) or ~/.codex/config.toml |

For Claude Code, the publish skill is additionally copied to ~/.claude/plugins/cofoundy-docs/skills/publish/.

login [--scope=team/<proj>/] [--ttl-days=N] [--url=https://docs.cofoundy.dev]

Opens the browser to https://docs.cofoundy.dev/api/agent/login?scope=…&ttl_days=…. After Cloudflare Access SSO, you'll see a one-time token block. Paste it back when the CLI prompts.

The token is stored at ~/.cofoundy/token with mode 0600 (verified post-write).

For non-interactive use:

npx @cofoundy/docs login --token=ct_xxx

http:// URLs are refused (§9.7 — login tokens MUST travel over HTTPS).

whoami

Reads ~/.cofoundy/token, decodes the claims locally (no signature verify — that's docs-ai's job at request time), prints sub, scope, exp. Exits non-zero if the token is missing or expired.

Security

  • §9.4 — the published npm artifact never bundles a token. The files field in package.json whitelists only dist/, src/assets/, and docs.
  • §9.5 — ~/.cofoundy/token is created with mode 0600. Parent directory is 0700.
  • §9.6 — install MERGES into existing MCP config files (JSON or TOML). It never overwrites unrelated entries.
  • §9.7 — login rejects non-https:// URLs to prevent token interception.

Token environment variable

After login, your MCP client reads the token via the COFOUNDY_DOCS_TOKEN env var (the config entry contains Authorization: Bearer ${COFOUNDY_DOCS_TOKEN}). Either:

  1. Let the MCP client read it directly (some editors source ~/.cofoundy/token automatically), or
  2. Export it manually:
export COFOUNDY_DOCS_TOKEN="$(cat ~/.cofoundy/token)"

License

MIT