# How to connect AppDrag to OpenClaw (paste one key, 11 tools) > Connect AppDrag to OpenClaw with ClawLink: paste your AppDrag key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/appdrag The usual route to AppDrag 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 AppDrag setup: install one ClawHub skill, connect AppDrag in the browser, and OpenClaw can call real AppDrag 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 AppDrag. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect AppDrag** — 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 appdrag # connect AppDrag (browser OAuth) npx -y @useclawlink/cli actions appdrag # list available actions npx -y @useclawlink/cli run appdrag --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 AppDrag in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your AppDrag API key once. Verify the connection by asking OpenClaw: > Use AppDrag to execute function get prod 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 AppDrag is connected in the dashboard, that agent calls the same 11 AppDrag 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). ## AppDrag MCP for OpenClaw Looking for a AppDrag MCP server for OpenClaw? ClawLink connects AppDrag to OpenClaw and exposes 11 AppDrag 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 AppDrag integration](https://claw-link.dev/hermes/appdrag) works the same way. ## What the OpenClaw AppDrag integration can do 11 AppDrag tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 11. ### 8 of 11 AppDrag tools for OpenClaw | Tool | What it does | |---|---| | **Execute function get prod** `appdrag_execute_function_get_prod` | Execute a production Cloud Backend API function via GET | | **Visual SQL select** `appdrag_visual_sql_select` | Execute a Visual SELECT Cloud Backend function | | **Execute function patch dev** `appdrag_execute_function_patch_dev` | Execute the development version of a Cloud Backend API function via PATCH | | **Execute function post default** `appdrag_execute_function_post_default` | Execute a Cloud Backend API function via POST on the default environment | | **Execute function post preprod** `appdrag_execute_function_post_preprod` | Execute a Cloud Backend API function via POST on the preprod environment | | **Execute function put default** `appdrag_execute_function_put_default` | Execute a Cloud Backend API function via PUT on the default environment | | **Execute function put preprod** `appdrag_execute_function_put_preprod` | Execute a Cloud Backend API function via PUT on the preprod environment | | **Visual SQL update** `appdrag_visual_sql_update` | Execute a Visual SQL UPDATE via an AppDrag Visual UPDATE function | ## Example prompts **Execute Function Get Prod** > Use AppDrag to execute function get prod and walk me through the result in plain English. **Visual Sql Select** > Use AppDrag to visual sql select and walk me through the result in plain English. **Execute Function Patch Dev** > Use AppDrag to execute function patch dev and walk me through the result in plain English. **Execute Function Post Default** > Use AppDrag to execute function post default 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 AppDrag working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the AppDrag API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected AppDrag 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 AppDrag. | 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 AppDrag actions to the runtime in a format your agent can reliably use. | 11 tools for AppDrag are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes AppDrag 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 AppDrag in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the AppDrag 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 AppDrag skill but can't call the tools The ClawHub skill teaches OpenClaw about AppDrag, but the calls run through the ClawLink plugin and your connected account. Make sure AppDrag 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 AppDrag 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 AppDrag tools AppDrag 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 AppDrag 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. ### AppDrag 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 AppDrag has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw AppDrag integration? Yes. ClawLink is the fastest way to connect OpenClaw to AppDrag: link your AppDrag account once in the browser and OpenClaw can call the AppDrag API through 11 ready-made tools — no custom code or token handling. ### How do I add AppDrag to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink AppDrag skill from ClawHub, then you click Connect in the dashboard to authorize AppDrag. OpenClaw calls the tools from the next message — no config files, and the AppDrag key you paste is stored server-side instead of in your environment. ### How long does it take to connect AppDrag to OpenClaw? About two minutes. Sign in, click Connect next to AppDrag in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring AppDrag 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 AppDrag working from chat. ### OpenClaw installed the AppDrag skill but can't call the tools The ClawHub skill teaches OpenClaw about AppDrag, but the calls run through the ClawLink plugin and your connected account. Make sure AppDrag 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 - [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.