# How to connect 0CodeKit to OpenClaw (paste one key, 8 tools)

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

Web version: https://claw-link.dev/openclaw/0codekit

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

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

Verify the connection by asking OpenClaw:

> Use 0CodeKit to calculate bmi 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 0CodeKit is connected in the dashboard, that agent calls the same 8 0CodeKit 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).

## 0CodeKit MCP for OpenClaw

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

## What the OpenClaw 0CodeKit integration can do

8 0CodeKit tools are ready for OpenClaw once the account is connected.

### All 8 0CodeKit tools for OpenClaw

| Tool | What it does |
|---|---|
| **Calculate bmi** `0codekit_calculate_bmi` | Calculate body mass index and the provider's related desirable-weight, daily-energy, and |
| **Check weekend** `0codekit_check_weekend` | Determine whether a date is a weekend and return its weekday name and day number |
| **Convert nation iso** `0codekit_convert_nation_iso` | Convert either an English country name to its ISO code or an ISO code to its English country |
| **Find keywords** `0codekit_find_keywords` | Search text for one or more keywords and report whether each occurs and the zero-based |
| **Get remaining credits** `0codekit_get_remaining_credits` | Return the number of 0CodeKit credits remaining for the connected API key |
| **Hash message** `0codekit_hash_message` | Generate a cryptographic digest or HMAC for a text message using a supported algorithm |
| **Parse utm parameters** `0codekit_parse_utm_parameters` | Extract standard UTM campaign parameters from a URL |
| **Validate email** `0codekit_validate_email` | Check an email address using 0CodeKit and return whether it is valid plus the provider's |

## Example prompts

**Calculate Bmi**

> Use 0CodeKit to calculate bmi and walk me through the result in plain English.

**Check Weekend**

> Use 0CodeKit to check weekend and walk me through the result in plain English.

**Convert Nation Iso**

> Use 0CodeKit to convert nation iso and walk me through the result in plain English.

**Find Keywords**

> Use 0CodeKit to find keywords and walk me through the result in plain English.

## 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 0CodeKit working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

### OpenClaw installed the 0CodeKit skill but can't call the tools
The ClawHub skill teaches OpenClaw about 0CodeKit, but the calls run through the ClawLink plugin and your connected account. Make sure 0CodeKit 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 tools](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.
