# How to connect Shortpixel to OpenClaw (paste one key, 12 tools)

> Connect Shortpixel to OpenClaw with ClawLink: paste your Shortpixel key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/shortpixel

The usual route to Shortpixel 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 Shortpixel setup: install one ClawHub skill, connect Shortpixel in the browser, and OpenClaw can call real Shortpixel 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 Shortpixel.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Shortpixel** — 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 shortpixel  # connect Shortpixel (browser OAuth)
npx -y @useclawlink/cli actions shortpixel  # list available actions
npx -y @useclawlink/cli run shortpixel <action> --input '<json>'  # 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 Shortpixel in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Shortpixel API key once.

Verify the connection by asking OpenClaw:

> Use Shortpixel to check image status and walk me through the result in plain English.

### 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 Shortpixel is connected in the dashboard, that agent calls the same 12 Shortpixel 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).

## Shortpixel MCP for OpenClaw

Looking for a Shortpixel MCP server for OpenClaw? ClawLink connects Shortpixel to OpenClaw and exposes 12 Shortpixel 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 Shortpixel integration](https://claw-link.dev/hermes/shortpixel) works the same way.

## What the OpenClaw Shortpixel integration can do

12 Shortpixel 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 Shortpixel tools for OpenClaw

| Tool | What it does |
|---|---|
| **Check image status** `shortpixel_check_image_status` | Check the optimization status of an image being processed by ShortPixel |
| **Get adaptive image cdn** `shortpixel_get_adaptive_image_cdn` | Optimize images on-the-fly via ShortPixel CDN |
| **Get API status** `shortpixel_get_api_status` | Retrieve the current status of your API key, including available credits |
| **Get cdn usage** `shortpixel_get_cdn_usage` | Retrieve detailed CDN usage statistics for a domain including traffic, API calls, monthly |
| **Read cdn domain** `shortpixel_read_cdn_domain` | Check the status of a domain and its CDN quota on ShortPixel |
| **Add cdn domain** `shortpixel_add_cdn_domain` | Add a new domain to the ShortPixel CDN system and associate it with your API key |
| **Optimize images by URL** `shortpixel_optimize_images_by_url` | Optimize images by providing their URLs |
| **Set cdn domain** `shortpixel_set_cdn_domain` | Associate an API key with an existing domain |
| **Upload and optimize images** `shortpixel_upload_and_optimize_images` | Upload and optimize images that are not accessible online |
| **Clean up image** `shortpixel_clean_up_image` | Remove images from the processing queue |
| **Revoke cdn domain** `shortpixel_revoke_cdn_domain` | Revoke a domain association from ShortPixel CDN |

## Example prompts

**Check Image Status**

> Use Shortpixel to check image status and walk me through the result in plain English.

**Get Adaptive Image Cdn**

> Pull the relevant data from Shortpixel, summarize it in plain English, and point out anything that needs attention.

**Get Api Status**

> Pull the relevant data from Shortpixel, summarize it in plain English, and point out anything that needs attention.

**Get Cdn Usage**

> Pull the relevant data from Shortpixel, 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 Shortpixel working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Shortpixel API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Shortpixel 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 Shortpixel. | 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 Shortpixel actions to the runtime in a format your agent can reliably use. | 12 tools for Shortpixel are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Shortpixel 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 Shortpixel in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Shortpixel 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 Shortpixel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Shortpixel, but the calls run through the ClawLink plugin and your connected account. Make sure Shortpixel 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 Shortpixel 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 Shortpixel tools
Shortpixel 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 Shortpixel 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.

### Shortpixel 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 Shortpixel has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Shortpixel integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Shortpixel: link your Shortpixel account once in the browser and OpenClaw can call the Shortpixel API through 12 ready-made tools — no custom code or token handling.

### How do I add Shortpixel to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Shortpixel skill from ClawHub, then you click Connect in the dashboard to authorize Shortpixel. OpenClaw calls the tools from the next message — no config files, and the Shortpixel key you paste is stored server-side instead of in your environment.

### How long does it take to connect Shortpixel to OpenClaw?
About two minutes. Sign in, click Connect next to Shortpixel in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Shortpixel 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 Shortpixel working from chat.

### OpenClaw installed the Shortpixel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Shortpixel, but the calls run through the ClawLink plugin and your connected account. Make sure Shortpixel 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
- [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services
- [OpenClaw SafetyCulture integration](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.
