How to connect NPM to OpenClaw
Connect NPM to OpenClaw with ClawLink: paste your NPM key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.
NPMAPI KEYMCPSearch packages, get download stats, and check security advisories. Once connected, OpenClaw can read and act on NPM from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to NPM access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical NPM setup: install one ClawHub skill, connect NPM in the browser, and OpenClaw can call real NPM actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the NPM skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "NPM" (hith3sh/npm-registry) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/npm-registry
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to NPM.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect NPM
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with NPM?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect NPM in the ClawLink dashboard — paste your NPM API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from NPM, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once NPM is connected in the dashboard, that agent calls the same 12 NPM tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
NPM MCP for OpenClaw
Looking for a NPM MCP server for OpenClaw? ClawLink connects NPM to OpenClaw and exposes 12 NPM tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes NPM integration works the same way.
What the OpenClaw NPM integration can do
12 NPM tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12.
11 of 12 NPM tools for OpenClaw
| Tool | What it does |
|---|---|
Get all packages download point npm_get_all_packages_download_point | Get total registry download stats |
Get download counts point npm_get_download_counts_point | Get package download counts |
Get download counts range package npm_get_download_counts_range_package | Get downloads over a date range |
Get registry changes npm_get_registry_changes | Get registry changes feed |
Get registry meta npm_get_registry_meta | Get registry metadata and ping status |
Get version downloads npm_get_version_downloads | Get version-specific downloads |
Query bulk security advisories npm_query_bulk_security_advisories | Check security vulnerabilities for packages |
Registry get package npm_registry_get_package | Get package metadata and versions |
Registry search packages npm_registry_search_packages | Search for packages in the npm registry |
Get download range all npm_get_download_range_all | Get daily download counts for all npm packages over a specified period |
Registry get root npm_registry_get_root | Fetches npm registry root metadata including total package count and update sequence |
Try it: find the NPM tool you need
Browse the 11 NPM tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from NPM, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from NPM, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from NPM, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from NPM, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want NPM working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the NPM API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected NPM account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for NPM. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right NPM actions to the runtime in a format your agent can reliably use. | 12 tools for NPM are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes NPM to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect NPM in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the NPM key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the NPM skill but can't call the tools
The ClawHub skill teaches OpenClaw about NPM, but the calls run through the ClawLink plugin and your connected account. Make sure NPM is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect NPM from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling NPM tools
NPM tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every NPM call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
NPM returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for NPM has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw NPM integration?
Yes. ClawLink is the fastest way to connect OpenClaw to NPM: link your NPM account once in the browser and OpenClaw can call the NPM API through 12 ready-made tools — no custom code or token handling.
How do I add NPM to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink NPM skill from ClawHub, then you click Connect in the dashboard to authorize NPM. OpenClaw calls the tools from the next message — no config files, and the NPM key you paste is stored server-side instead of in your environment.
How long does it take to connect NPM to OpenClaw?
About two minutes. Sign in, click Connect next to NPM in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring NPM up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want NPM working from chat.
OpenClaw installed the NPM skill but can't call the tools
The ClawHub skill teaches OpenClaw about NPM, but the calls run through the ClawLink plugin and your connected account. Make sure NPM is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Connect GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.