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

@toolbeltai/mcp-config

v0.1.3

Published

Shared MCP client config descriptors used by @toolbeltai/cli and toolbelt atlas. Plug-in schema: one descriptor per client (Claude Code, Claude Desktop, OpenClaw, Cursor, Windsurf, Codex CLI, Gemini CLI).

Readme

@toolbeltai/mcp-config

Shared MCP client config descriptors used across the Toolbelt stack — @toolbeltai/cli (install flow) and toolbelt atlas (Connect picker UI).

Each descriptor is a plain object describing one MCP client:

  • Where the client's config file lives (per OS)
  • What format it uses (JSON or TOML)
  • How to render a copy-pasteable snippet
  • How to upsert an entry into an existing parsed config

Supported clients

| Client | Config path (macOS) | Format | |---|---|---| | Claude Code | ~/.claude.json | JSON | | Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json | JSON | | OpenClaw | ~/.openclaw/openclaw.json | JSON (nested mcp.servers) | | Cursor | ~/.cursor/mcp.json | JSON | | Windsurf | ~/.codeium/windsurf/mcp_config.json | JSON | | Gemini CLI | ~/.gemini/settings.json | JSON (uses httpUrl) | | Codex CLI | ~/.codex/config.toml | TOML (uses http_headers) |

Usage

import { allClients, getClient, renderSnippet } from '@toolbeltai/mcp-config';

const entry = {
  name: 'toolbelt',
  url: 'https://mcp.toolbelt.ai/mcp',
  token: 'tb_xxx',
};

// Render a snippet for a specific client
console.log(renderSnippet('claude-code', entry));

// Enumerate all supported clients
for (const c of allClients) {
  console.log(c.displayName, c.configPaths.darwin);
}

// Upsert into a parsed JSON config (for CLI install flow)
const c = getClient('claude-code');
const updated = c.upsertInto!(existingConfig, entry);

Design

  • One descriptor per client. New client = one new file in src/clients/.
  • Pure functions. No IO, no side effects — renderers and upserts take data in and return data out. File reads/writes live in the CLI.
  • Golden-file tests. Every client has a byte-for-byte expected snippet locked in tests so format drift shows up in the diff, not at runtime.

License

MIT