# How to connect Codemagic to OpenClaw (paste one key, 22 tools) > Connect Codemagic to OpenClaw with ClawLink: paste your Codemagic key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/codemagic The usual route to Codemagic 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 Codemagic setup: install one ClawHub skill, connect Codemagic in the browser, and OpenClaw can call real Codemagic 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 Codemagic. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Codemagic** — 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 codemagic # connect Codemagic (browser OAuth) npx -y @useclawlink/cli actions codemagic # list available actions npx -y @useclawlink/cli run codemagic --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 Codemagic in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Codemagic API key once. Verify the connection by asking OpenClaw: > Use Codemagic to api v3 meta get meta 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 Codemagic is connected in the dashboard, that agent calls the same 22 Codemagic 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). ## Codemagic MCP for OpenClaw Looking for a Codemagic MCP server for OpenClaw? ClawLink connects Codemagic to OpenClaw and exposes 22 Codemagic 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 Codemagic integration](https://claw-link.dev/hermes/codemagic) works the same way. ## What the OpenClaw Codemagic integration can do 22 Codemagic tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 22. ### 20 of 22 Codemagic tools for OpenClaw | Tool | What it does | |---|---| | **API v3 meta get meta** `codemagic_api_v3_meta_get_meta` | Get metadata about Codemagic including public IP addresses in use (in CIDR notation) | | **API v3 variable groups variable group ID get group** `codemagic_api_v3_variable_groups_variable_group_id_get_group` | Retrieve information about a specific variable group including its name and configuration | | **Get all builds** `codemagic_get_all_builds` | List all builds with optional filters for appId, workflowId, and branch | | **Get API key** `codemagic_get_api_key` | Retrieve the API key for the authenticated user from the server | | **Get shorebird meta** `codemagic_get_shorebird_meta` | Retrieve information about Shorebird integration | | **Get user** `codemagic_get_user` | Retrieve information about the currently authenticated user | | **Get variable groups** `codemagic_get_variable_groups` | Retrieve paginated list of variable groups for an application | | **Get variables** `codemagic_get_variables` | Retrieve paginated list of variables for a specific variable group | | **Retrieve all applications** `codemagic_retrieve_all_applications` | Retrieve all applications added to Codemagic | | **Retrieve an application** `codemagic_retrieve_an_application` | Retrieve a single application by its unique identifier | | **Retrieve caches for application** `codemagic_retrieve_caches_for_application` | Retrieve a list of caches for a specific application | | **Add application from private repo** `codemagic_add_application_from_private_repo` | Create an application from a private repository using SSH key authentication | | **Add new application** `codemagic_add_new_application` | Add a Git repository to the applications list in Codemagic | | **API v3 variable groups variable group ID update** `codemagic_api_v3_variable_groups_variable_group_id_update` | Change a variable group's name and security settings | | **Invite team member** `codemagic_invite_team_member` | Invite a new team member to a Codemagic team | | **Receive webhook** `codemagic_receive_webhook` | Receive webhook payloads from Git providers to trigger builds automatically | | **Start new build** `codemagic_start_new_build` | Start a new build for an application with specified workflow and branch or tag | | **Update variable** `codemagic_update_variable` | Update an existing variable within a specified variable group in Codemagic | | **Remove team member** `codemagic_remove_team_member` | Remove a collaborator or revoke a pending invitation from a Codemagic team | | **Stop preview** `codemagic_stop_preview` | Stop an app preview | ## Example prompts **Api V3 Meta Get Meta** > Use Codemagic to api v3 meta get meta and walk me through the result in plain English. **Api V3 Variable Groups Variable Group Id Get Group** > Use Codemagic to api v3 variable groups variable group id get group and walk me through the result in plain English. **Get All Builds** > Pull the relevant data from Codemagic, summarize it in plain English, and point out anything that needs attention. **Get Api Key** > Pull the relevant data from Codemagic, 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 Codemagic working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Codemagic API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Codemagic 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 Codemagic. | 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 Codemagic actions to the runtime in a format your agent can reliably use. | 22 tools for Codemagic are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Codemagic 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 Codemagic in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Codemagic 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 Codemagic skill but can't call the tools The ClawHub skill teaches OpenClaw about Codemagic, but the calls run through the ClawLink plugin and your connected account. Make sure Codemagic 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 Codemagic 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 Codemagic tools Codemagic 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 Codemagic 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. ### Codemagic 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 Codemagic has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Codemagic integration? Yes. ClawLink is the fastest way to connect OpenClaw to Codemagic: link your Codemagic account once in the browser and OpenClaw can call the Codemagic API through 22 ready-made tools — no custom code or token handling. ### How do I add Codemagic to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Codemagic skill from ClawHub, then you click Connect in the dashboard to authorize Codemagic. OpenClaw calls the tools from the next message — no config files, and the Codemagic key you paste is stored server-side instead of in your environment. ### How long does it take to connect Codemagic to OpenClaw? About two minutes. Sign in, click Connect next to Codemagic in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Codemagic 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 Codemagic working from chat. ### OpenClaw installed the Codemagic skill but can't call the tools The ClawHub skill teaches OpenClaw about Codemagic, but the calls run through the ClawLink plugin and your connected account. Make sure Codemagic 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 - [Connect 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.