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

atel-mcp-openclaw

v0.1.12

Published

OpenClaw plugin that exposes ATEL Remote MCP tools through a single bridge tool

Readme

ATEL MCP OpenClaw Plugin

This plugin registers one OpenClaw tool, atel_mcp, that bridges OpenClaw to the ATEL Remote MCP server.

One-command Install

Recommended entry:

npx -y atel-mcp-openclaw

Fallback if you prefer a global install:

npm install -g atel-mcp-openclaw
atel-mcp-openclaw

Why npx is the default recommendation:

  • it starts the guided setup immediately in one command
  • it avoids relying on npm postinstall output, which some npm versions hide on successful global installs
  • it keeps the user path shorter and more predictable

From this repository:

./scripts/install-openclaw-plugin.sh

Defaults:

  • serverBaseUrl=https://atelai.xyz
  • platformBaseUrl=https://api.atelai.xyz

Default installer behavior is guided and low-intrusion:

  • copies the plugin into ~/.openclaw/extensions/atel-mcp
  • writes plugins.allow, plugins.entries.atel-mcp, plugins.installs.atel-mcp
  • confirms the ATEL identity, Telegram callback preference, and resident-runtime help
  • does not modify tools.profile, gateway.*, or tools.elevated.* unless you explicitly pass --align-openclaw

If you really want the installer to align OpenClaw runtime knobs too:

npx -y atel-mcp-openclaw --align-openclaw

Verify

openclaw plugins inspect atel-mcp --json

Expected:

status=loaded
toolNames=["atel_mcp"]

Then ask the Telegram bot:

使用 ATEL MCP 调用 atel_whoami,告诉我当前 DID、environment 和 scopes。

Supported actions

  • list: list remote ATEL MCP tools
  • call: call a remote ATEL MCP tool with JSON arguments

Without this OpenClaw-side installation and DID binding, Telegram messages can only use native OpenClaw or raw ATEL CLI paths; they cannot call ATEL MCP tools.