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

@jcyamacho/agent-bridge

v0.0.7

Published

A filesystem-based MCP server that enables room-first collaboration between local AI agents across repositories.

Readme

agent-bridge

A filesystem-based MCP server that enables room-first collaboration between local AI agents across repositories.

Each local MCP client session runs its own stdio MCP server instance. All instances read/write to a shared directory (~/.agent-bridge/). No central process - the filesystem is the message bus.

Development Setup

bun install
bun run build

Usage

Register the MCP server in each local agent session with a unique --peer-id.

The examples below use Claude Code CLI, but the same server works with other local MCP-capable agents (for example, Codex) using their MCP server registration flow.

# Frontend session
claude mcp add agent-bridge -- npx -y @jcyamacho/agent-bridge \
  --peer-id frontend --name "Frontend"

# Backend session
claude mcp add agent-bridge -- npx -y @jcyamacho/agent-bridge \
  --peer-id backend --name "Backend API"

CLI Arguments

| Argument | Required | Description | | --- | --- | --- | | --peer-id | Yes | Unique identifier for this peer | | --name | No | Display name (defaults to peer-id) | | --project | No | Project path (defaults to cwd) | | --bridge-dir | No | Shared directory (defaults to ~/.agent-bridge) |

Tools

| Tool | Description | | --- | --- | | list_peers | List other registered peers | | open_feature_room | Create a feature room | | close_feature_room | Close a feature room (read-only) | | list_feature_rooms | List open feature rooms (or include closed) | | post_feature_message | Post a typed feature message (update, question, decision, blocker) | | read_feature_messages | Read feature room messages | | put_feature_context | Write a context document in a feature room | | get_feature_context | Read a context document from a feature room | | list_feature_context_keys | List context keys in a feature room |

Feature-room tools use room_id as the stable room identifier in their input payloads. Closed rooms are read-only.

Peer registration is automatic on startup and heartbeat; there is no manual peer-upsert tool.

Development

bun test          # Run tests
bun run build     # Build for Node.js