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

@calibress/curl-mcp-bridge

v0.1.1

Published

Local MCP stdio bridge that proxies to Calibress hosted /mcp over HTTP

Readme

curl-mcp-bridge

A local MCP stdio bridge that proxies MCP JSON-RPC to a Calibress hosted /mcp HTTP endpoint.

This lets any MCP client that supports stdio (Claude Desktop, Roo, etc.) talk to the hosted multi-tenant MCP gateway.

Requirements

  • Node.js >= 18

Usage

Set these env vars:

  • CALIBRESS_ENDPOINT (required) — Hosted MCP URL (e.g. https://enterprise-plan.dev.calibress.com/mcp)
  • CALIBRESS_API_KEY (required) — Tenant/project API key (Bearer). Prefer project-scoped keys so “project selection” is implicit.

Then run:

CALIBRESS_ENDPOINT="https://enterprise-plan.dev.calibress.com/mcp" \
CALIBRESS_API_KEY="cmcp_..." \
node ./bin/curl-mcp-bridge.js

CLI overrides are also available (--endpoint, --api-key, --session-id).

The bridge reads MCP messages from stdin and writes MCP responses to stdout (1 JSON object per line).

Run via npx (npm)

CALIBRESS_ENDPOINT="https://enterprise-plan.dev.calibress.com/mcp" \
CALIBRESS_API_KEY="cmcp_..." \
npx -y @calibress/curl-mcp-bridge@latest

If you need to run an unpublished build, you can still run from GitHub:

CALIBRESS_ENDPOINT="https://enterprise-plan.dev.calibress.com/mcp" \
CALIBRESS_API_KEY="cmcp_..." \
npx -y github:calibress/curl-mcp-bridge

MCP client configuration

Example (Roo / Claude Desktop style):

{
  "curl-mcp-bridge": {
    "transport": "stdio",
    "command": "npx",
    "args": ["-y", "@calibress/curl-mcp-bridge@latest"],
    "env": {
      "CALIBRESS_ENDPOINT": "https://YOUR-TENANT.dev.calibress.com/mcp",
      "CALIBRESS_API_KEY": "cmcp_REPLACE_ME"
    },
    "alwaysAllow": [
      "mcp_version",
      "getting_started",
      "list_surfaces",
      "list_connections",
      "list_operations",
      "get_operation_spec",
      "execute_operation",
      "curl_request"
    ]
  }
}

Session handling

  • The hosted MCP endpoint issues Mcp-Session-Id on initialize.
  • The bridge caches that session id in-process and automatically sends it on subsequent requests.
  • If a client sends a request before initialize, the bridge will bootstrap a session and retry once.

Extensibility

The bridge forwards all JSON-RPC methods as-is.

When the hosted MCP gateway adds new tools (e.g. list_connections), existing clients automatically see them via tools/list without changing the bridge.

Notes

  • To publish, bump package.json version and run npm publish (public access is configured).

License

MIT.