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

borgmcp

v5.4.1

Published

Coordinate AI coding agents in shared cubes. Works with Claude Code, Codex, and OpenCode.

Vulnerabilities

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

Links

Git

Maintainers

byteventuresbyteventures

Keywords

mcpclaude-codecodexopencodemulti-agentcoordination

Readme

Borg MCP

Multi-agent coordination for Claude Code, Codex, and OpenCode. Borg runs the agent CLI you already installed and connects its sessions through a self-hosted coordination server on your computer or private LAN. A shared coordination space is a cube. Each connected agent session is a drone, and its role defines how it works.

Claude Code, Codex, and OpenCode drones coordinate through a local Borg cube and server while an operator directs the work; Git and npm reach their usual remotes.

Install

npm install -g borgmcp

Continue with the Get Started guide to check the requirements, configure Borg, start the local server, and add your first drone. Borg has no hosted account or subscription.

Choose A Command

  • borg clone <repository-url> checks out a new repository and delegates its complete cube, roster, and launch setup to borg quickstart. Use --checkout-only to stop after checkout; --no-launch remains an explicit compatibility alias. In a non-interactive terminal, full setup requires both --yes and --template <name>.
  • borg quickstart creates, staffs, and launches the full roster for the Git repository you are already in. Repeat --role <slug>[:<count>] to replace the template roster with an explicit selection. Rerunning it keeps existing drones and continues after cancellation or partial failure.
  • borg assimilate [role] adds or resumes one drone under one role. Use it when you need one more drone or want to reattach a saved worktree, not when you want the repository's complete initial roster.

Activity-Log Routing

Every borg_log call requires an explicit to audience: use "broadcast" for the whole cube or a non-empty selector array for direct delivery. Omission, message prose, and taxonomy classes never choose recipients. Direct recipients determine delivery and wakes, not read confidentiality; the cube remains the trust boundary. Use borg_read-log to drain unread entries and borg_read-entry to retrieve one known complete entry by entry_id without moving the unread cursor.

Pass refs with local Git refs when a log entry needs commit provenance. The client resolves each ref in the seat repository and appends <ref> = <40-hex> to the message; REVIEW-READY entries require this mechanism. Invalid refs and typed full SHAs whose seven-character prefix resolves to a different commit are refused. Full SHAs that cannot be checked locally remain allowed and are listed as unverified in the tool result for cross-repository citations.

Documentation

  • Core concepts defines cubes, drones, roles, and the activity log.
  • CLI commands covers launching, resuming, updating, and worktree maintenance. The installed client's borg --help and borg <command> --help are the exact reference for its version.
  • MCP tool reference lists the borg_... tools available inside agent sessions.
  • Cube documents explains immutable durable content, revisions, removal, and structured activity-log citations.
  • Server operations covers loopback and private-LAN operation.
  • Security explains invitations, client access, and network exposure.
  • Self-hosting covers data locations, backups, client administration, and upgrades.
  • FAQ answers common setup and workflow questions.

For client-specific recovery details, see docs/LOCAL_SERVER.md and docs/SEAT_LIFECYCLE.md.

Agent Permissions

Borg can remove repeated approval prompts for its own coordination tools. It does not approve shell commands, file operations, or web access.

Claude Code receives Borg's MCP tool allowlist at launch. For Codex and OpenCode, Borg checks the effective configuration and automatically applies a launch-only override when restrictive Borg approvals are found. It prints the affected tool count and discloses that approving borg_tool also approves any Borg operation invoked through it. Pass --no-borg-approval-override to skip the override and receive the warning plus repair snippet instead. The launch-only override does not modify the agent's configuration. borg setup can show the corresponding persistent configuration snippets.

Wake Recovery

If borg_regen or borg_stream-status reports a wake-up problem, follow the recovery command it prints. For Codex or OpenCode, relaunch through borg if the agent's local control connection is no longer available.

License

This client and borgmcp-shared are Apache-2.0; the self-hosted borgmcp-server is licensed separately under FSL-1.1 and converts to Apache-2.0 under its terms. See this client's LICENSE and NOTICE.

Links