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

furry-companion-mcp

v0.1.0

Published

AI Companion MCP Runtime for agent presence events over stdio.

Readme

Furry Companion MCP

AI Companion MCP Runtime for agent presence events over stdio MCP plus local IPC for UI consumers.

Runtime path:

AI Agent -> MCP Tool -> Event Bus -> local IPC -> VSCode Extension -> Webview

No websocket MCP transport is used.

Tool

set_state({ state: "thinking" })

Supported states:

  • idle
  • thinking
  • planning
  • coding
  • testing
  • debugging
  • success
  • error

The tool emits:

bus.emit("state", {
  type: "state",
  state
})

Install From npm

Use the package directly from npm in an MCP client:

{
  "mcpServers": {
    "furry-companion": {
      "command": "npx",
      "args": ["-y", "furry-companion-mcp"]
    }
  }
}

Or install it globally:

npm install -g furry-companion-mcp
furry-companion-mcp

VSCode Extension Bridge

The MCP server starts a local JSON Lines IPC bridge for non-MCP UI consumers. Multiple MCP processes can run at the same time: the first process owns the bridge, and later processes relay their state events into the existing bridge.

Default IPC path:

  • Windows: \\.\pipe\furry-companion-mcp
  • macOS/Linux: /tmp/furry-companion-mcp.sock

Override it when needed:

FURRY_COMPANION_IPC_PATH=/tmp/my-companion.sock furry-companion-mcp

Each IPC line is a state event:

{"type":"state","state":"thinking"}

The VSCode extension should connect to this IPC path with Node net, parse newline-delimited JSON, then call webview.postMessage({ command: "companion-state", ... }).

Agent Skills

Skill documents are included in the npm package under skills/:

  • skills/claude.md
  • skills/codex.md
  • skills/cursor.md

They are downloaded with the MCP package, but MCP clients do not automatically activate arbitrary skill files from npm packages. Copy or reference the matching file in the agent's own instruction/skill system. See skills/INSTALL.md for the available installation options.

Development

npm install
npm run build
npm run start

MCP CLI

After building, the package exposes:

{
  "bin": {
    "furry-companion-mcp": "./dist/index.js"
  }
}

Use it as a stdio MCP server. No websocket transport is used.