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

@cool-ai/beach-channel-mcp

v0.1.2

Published

Beach MCP channel — expose a Beach agent as an MCP tool over stdio or streamable HTTP. Implements core's ChannelAdaptor.

Downloads

181

Readme

@cool-ai/beach-channel-mcp

The MCP channel adaptor: it exposes a Beach agent as an MCP tool. A caller invokes the tool, the call is routed, and the reply comes back as the tool's result. It implements core's ChannelAdaptor, and like A2A it is a way for one agent to reach another — here over the Model Context Protocol.

An MCP tool call is synchronous, so the adaptor is a blocking channel: the tool handler holds its result open — keyed on a correlation id carried on the reply destination — until the routed reply arrives, then resolves with the reply text. A call whose reply never comes returns an error result after replyTimeoutMs.

The package imports no MCP SDK at runtime. You wire the tool onto your own McpServer (stdio or streamable HTTP) with registerOn; the routing engine here is transport-agnostic.

Use

import { MCPChannelAdaptor } from '@cool-ai/beach-channel-mcp';
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';

const mcp = new MCPChannelAdaptor({
  inbound: (req) => channelRouter.inbound(req),
  render: (parts) => toText(parts),   // optional; defaults to string-or-JSON
});

const server = new McpServer({ name: 'baxter', version: '1.0.0' });
mcp.registerOn(server, { toolName: 'ask_baxter' });
// Connect `server` over stdio or streamable HTTP, and register `mcp` as a
// channel-router adaptor so replies resolve the tool call.

The caller's tool arguments are handed through channel-blind as the inbound message's data; your request handler interprets them.