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

@mulmobridge/google-chat

v0.1.1

Published

Google Chat bridge for MulmoBridge — connect Google Chat to MulmoClaude

Downloads

36

Vulnerabilities

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

Links

Maintainers

isamuisamusnakajimasnakajima

Keywords

Readme

@mulmobridge/google-chat

Experimental — please test and report issues.

Google Chat bridge for MulmoClaude. Uses HTTP endpoint mode (synchronous responses).

Setup

1. Create a Google Chat App

  1. Go to Google Cloud Console → create or select a project
  2. Enable the Google Chat API
  3. Go to APIs & Services → Credentials and note your Project Number
  4. Configure the Chat app:
    • App name: MulmoClaude
    • App URL: your public endpoint (ngrok for dev)
    • Functionality: receive 1:1 messages and join spaces

2. Set up ngrok

ngrok http 3005

3. Run the bridge

# Testing with mock server
npx @mulmobridge/mock-server &
GOOGLE_CHAT_PROJECT_NUMBER=123456 \
MULMOCLAUDE_AUTH_TOKEN=mock-test-token \
npx @mulmobridge/google-chat

# With real MulmoClaude
GOOGLE_CHAT_PROJECT_NUMBER=123456 \
npx @mulmobridge/google-chat

4. Message the bot

In Google Chat, find your app and send it a direct message.

Environment Variables

| Variable | Required | Description | |---|---|---| | GOOGLE_CHAT_PROJECT_NUMBER | Yes | Google Cloud project number | | GOOGLE_CHAT_BRIDGE_PORT | No | Webhook port (default: 3005) | | MULMOCLAUDE_API_URL | No | Default http://localhost:3001 | | MULMOCLAUDE_AUTH_TOKEN | No | Bearer token | | GOOGLE_CHAT_BRIDGE_DEFAULT_ROLE | No | Role id to seed new bridge sessions with (e.g. coder, general). Applied ONLY when a google-chat session first appears — once the user switches role via /role <id> the session's own role wins. Unknown role ids silently fall back to the server's default with a warn log. | | BRIDGE_DEFAULT_ROLE | No | Same as above but shared across every bridge. Transport-specific GOOGLE_CHAT_BRIDGE_DEFAULT_ROLE wins when both are set. |

Security — Request Verification

Every incoming webhook request is verified using Google's OIDC JWT mechanism:

  1. The Authorization: Bearer <token> header is extracted
  2. The JWT signature is verified against Google's JWKS endpoint (https://www.googleapis.com/service_accounts/v1/jwk/[email protected])
  3. The following claims are checked:
    • iss must be [email protected]
    • aud must match GOOGLE_CHAT_PROJECT_NUMBER
    • exp must not be in the past
  4. Requests that fail verification receive 401 Unauthorized

This prevents spoofed requests from arbitrary third parties.

Limitations

  • Synchronous mode only: Google Chat expects a response within 30 seconds. Agent responses that take longer will time out. For async responses, a service account with the Chat API is needed (future enhancement).
  • No push delivery: server→bridge push requires the async Chat API with a service account. Currently pushes are logged but not delivered.

Ecosystem

Part of the @mulmobridge/* package family.

Shared libraries:

Bridges (one npm package per platform):

License

MIT