# How to connect Appcircle to OpenClaw (paste one key, 14 tools) > Connect Appcircle to OpenClaw with ClawLink: paste your Appcircle key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/appcircle The usual route to Appcircle 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 Appcircle setup: install one ClawHub skill, connect Appcircle in the browser, and OpenClaw can call real Appcircle 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 Appcircle. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Appcircle** — 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 appcircle # connect Appcircle (browser OAuth) npx -y @useclawlink/cli actions appcircle # list available actions npx -y @useclawlink/cli run appcircle --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 Appcircle in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Appcircle API key once. Verify the connection by asking OpenClaw: > Use Appcircle to distribution list profiles 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 Appcircle is connected in the dashboard, that agent calls the same 14 Appcircle 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). ## Appcircle MCP for OpenClaw Looking for a Appcircle MCP server for OpenClaw? ClawLink connects Appcircle to OpenClaw and exposes 14 Appcircle 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 Appcircle integration](https://claw-link.dev/hermes/appcircle) works the same way. ## What the OpenClaw Appcircle integration can do 14 Appcircle tools are ready for OpenClaw once the account is connected. ### All 14 Appcircle tools for OpenClaw | Tool | What it does | |---|---| | **Distribution list profiles** `appcircle_distribution_list_profiles` | List all distribution profiles for the authenticated organization | | **Get distribute sent profiles** `appcircle_get_distribute_sent_profiles` | Get distinct profile names for App Sharing Report filter | | **Get publish activity report** `appcircle_get_publish_activity_report` | Retrieve the publish activity report for your organization | | **List build profiles** `appcircle_list_build_profiles` | List all build profiles for the authenticated organization | | **List bundle identifiers** `appcircle_list_bundle_identifiers` | List all bundle identifiers in Appcircle | | **List organizations** `appcircle_list_organizations` | List organizations accessible to the authenticated user | | **List store profiles** `appcircle_list_store_profiles` | List all Enterprise App Store profiles for the authenticated organization | | **Store inapp list app versions** `appcircle_store_inapp_list_app_versions` | List available app versions for the Enterprise App Store profile | | **Store list profile app versions v2** `appcircle_store_list_profile_app_versions_v2` | List app versions under a given store profile | | **Build repo webhook callback standard** `appcircle_build_repo_webhook_callback_standard` | Trigger Appcircle builds via Git provider webhook callbacks | | **Build webhook custom integration** `appcircle_build_webhook_custom_integration` | Triggers Appcircle builds via custom integration webhook endpoint by forwarding Git provider | | **Rename variable group** `appcircle_rename_variable_group` | Rename an environment group (variable group) in Appcircle | | **Store in app auth token** `appcircle_store_in_app_auth_token` | Fetch an access token for Enterprise App Store in-app updates | | **Store in app download version with user** `appcircle_store_in_app_download_version_with_user` | Download a specific in-app store version and attribute the download to a user for reporting | ## Example prompts **Distribution List Profiles** > Use Appcircle to distribution list profiles and walk me through the result in plain English. **Get Distribute Sent Profiles** > Pull the relevant data from Appcircle, summarize it in plain English, and point out anything that needs attention. **Get Publish Activity Report** > Pull the relevant data from Appcircle, summarize it in plain English, and point out anything that needs attention. **List Build Profiles** > List the relevant items in Appcircle, group them by priority, and recommend what OpenClaw should do next. ## 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 Appcircle working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Appcircle API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Appcircle 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 Appcircle. | 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 Appcircle actions to the runtime in a format your agent can reliably use. | 14 tools for Appcircle are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Appcircle 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 Appcircle in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Appcircle 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 Appcircle skill but can't call the tools The ClawHub skill teaches OpenClaw about Appcircle, but the calls run through the ClawLink plugin and your connected account. Make sure Appcircle 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 Appcircle 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 Appcircle tools Appcircle 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 Appcircle 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. ### Appcircle 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 Appcircle has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Appcircle integration? Yes. ClawLink is the fastest way to connect OpenClaw to Appcircle: link your Appcircle account once in the browser and OpenClaw can call the Appcircle API through 14 ready-made tools — no custom code or token handling. ### How do I add Appcircle to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Appcircle skill from ClawHub, then you click Connect in the dashboard to authorize Appcircle. OpenClaw calls the tools from the next message — no config files, and the Appcircle key you paste is stored server-side instead of in your environment. ### How long does it take to connect Appcircle to OpenClaw? About two minutes. Sign in, click Connect next to Appcircle in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Appcircle 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 Appcircle working from chat. ### OpenClaw installed the Appcircle skill but can't call the tools The ClawHub skill teaches OpenClaw about Appcircle, but the calls run through the ClawLink plugin and your connected account. Make sure Appcircle 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 - [OpenClaw GitHub integration](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.