# How to connect Cloudsmith to OpenClaw (paste one key, 10 tools) > Connect Cloudsmith to OpenClaw with ClawLink: paste your Cloudsmith key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/cloudsmith The usual route to Cloudsmith 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 Cloudsmith setup: install one ClawHub skill, connect Cloudsmith in the browser, and OpenClaw can call real Cloudsmith actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Cloudsmith. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Cloudsmith** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect cloudsmith # connect Cloudsmith (browser OAuth) npx -y @useclawlink/cli actions cloudsmith # list available actions npx -y @useclawlink/cli run cloudsmith --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Cloudsmith in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudsmith API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Cloudsmith, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Cloudsmith is connected in the dashboard, that agent calls the same 10 Cloudsmith tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Cloudsmith MCP for OpenClaw Looking for a Cloudsmith MCP server for OpenClaw? ClawLink connects Cloudsmith to OpenClaw and exposes 10 Cloudsmith tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Cloudsmith integration](https://claw-link.dev/hermes/cloudsmith) works the same way. ## What the OpenClaw Cloudsmith integration can do 10 Cloudsmith tools are ready for OpenClaw once the account is connected. ### All 10 Cloudsmith tools for OpenClaw | Tool | What it does | |---|---| | **Get current user** `cloudsmith_get_current_user` | Return the identity authenticated by the connected Cloudsmith API key | | **Get package** `cloudsmith_get_package` | Get metadata, status, checksums, licensing, and security state for one package in a Cloudsmith | | **Get quota** `cloudsmith_get_quota` | Return current storage and bandwidth usage and allowances for a Cloudsmith namespace without | | **Get rate limits** `cloudsmith_get_rate_limits` | Return Cloudsmith's current per-resource request limits, remaining counts, intervals, and | | **Get repository** `cloudsmith_get_repository` | Get configuration, visibility, usage, and capability details for one Cloudsmith repository | | **List organizations** `cloudsmith_list_organizations` | List Cloudsmith organizations associated with the authenticated principal so an agent can | | **List repository vulnerabilities** `cloudsmith_list_repository_vulnerabilities` | List vulnerability scan summaries for packages in a Cloudsmith repository | | **Search audit log** `cloudsmith_search_audit_log` | Search paginated audit events for a Cloudsmith namespace by event, actor, or timestamp text | | **Search packages** `cloudsmith_search_packages` | Search packages in a Cloudsmith repository by name, filename, version, distribution | | **Search repositories** `cloudsmith_search_repositories` | Search and list repositories within a Cloudsmith namespace, returning identifiers and summary | ## Example prompts **Get Current User** > Pull the relevant data from Cloudsmith, summarize it in plain English, and point out anything that needs attention. **Get Package** > Pull the relevant data from Cloudsmith, summarize it in plain English, and point out anything that needs attention. **Get Quota** > Pull the relevant data from Cloudsmith, summarize it in plain English, and point out anything that needs attention. **Get Rate Limits** > Pull the relevant data from Cloudsmith, 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 Cloudsmith working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cloudsmith API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cloudsmith 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 Cloudsmith. | 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 Cloudsmith actions to the runtime in a format your agent can reliably use. | 10 tools for Cloudsmith are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cloudsmith 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 Cloudsmith in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Cloudsmith key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Cloudsmith skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudsmith, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudsmith 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 Cloudsmith 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 Cloudsmith tools Cloudsmith 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 Cloudsmith 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. ### Cloudsmith 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 Cloudsmith has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Cloudsmith integration? Yes. ClawLink is the fastest way to connect OpenClaw to Cloudsmith: link your Cloudsmith account once in the browser and OpenClaw can call the Cloudsmith API through 10 ready-made tools — no custom code or token handling. ### How do I add Cloudsmith to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cloudsmith skill from ClawHub, then you click Connect in the dashboard to authorize Cloudsmith. OpenClaw calls the tools from the next message — no config files, and the Cloudsmith key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cloudsmith to OpenClaw? About two minutes. Sign in, click Connect next to Cloudsmith in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Cloudsmith 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 Cloudsmith working from chat. ### OpenClaw installed the Cloudsmith skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudsmith, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudsmith 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/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.