# How to connect CircleCI to OpenClaw (paste one key, 65 tools) > Connect CircleCI to OpenClaw with ClawLink: paste your CircleCI key once and 65 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/circleci The usual route to CircleCI 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 CircleCI setup: install one ClawHub skill, connect CircleCI in the browser, and OpenClaw can call real CircleCI 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 CircleCI. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect CircleCI** — 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 circleci # connect CircleCI (browser OAuth) npx -y @useclawlink/cli actions circleci # list available actions npx -y @useclawlink/cli run circleci --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 CircleCI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CircleCI API key once. Verify the connection by asking OpenClaw: > Create it in CircleCI for me, then confirm the important fields before you finish. ### 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 CircleCI is connected in the dashboard, that agent calls the same 65 CircleCI 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). ## CircleCI MCP for OpenClaw Looking for a CircleCI MCP server for OpenClaw? ClawLink connects CircleCI to OpenClaw and exposes 65 CircleCI 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 CircleCI integration](https://claw-link.dev/hermes/circleci) works the same way. ## What the OpenClaw CircleCI integration can do 65 CircleCI tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 65. ### 30 of 65 CircleCI tools for OpenClaw | Tool | What it does | |---|---| | **Create usage export job** `circleci_create_usage_export_job` | Create a usage export job for a CircleCI organization | | **Get context** `circleci_get_context` | Retrieve a context by its unique ID | | **Get current user** `circleci_get_current_user` | Retrieve information about the currently authenticated user | | **Get flaky tests** `circleci_get_flaky_tests` | Get flaky tests for a project | | **Get job artifacts** `circleci_get_job_artifacts` | Retrieves artifacts (output files like test results, logs, build binaries, reports) produced by | | **Get job details** `circleci_get_job_details` | Fetch details of a specific job within a project | | **Get orb details** `circleci_get_orb_details` | Query detailed information about a CircleCI orb using the GraphQL API | | **Get orb version** `circleci_get_orb_version` | Retrieve detailed information about a specific CircleCI orb version via GraphQL | | **Get organization** `circleci_get_organization` | Retrieve organization details from CircleCI using GraphQL query | | **Get organization group** `circleci_get_organization_group` | Retrieve a group in an organization | | **Get pipeline config** `circleci_get_pipeline_config` | Fetch pipeline configuration by ID | | **Get pipeline definition** `circleci_get_pipeline_definition` | Retrieve a pipeline definition by project and definition ID | | **Get project** `circleci_get_project` | Retrieve a CircleCI project by its slug | | **Get project workflows** `circleci_get_project_workflows` | Get summary metrics for all workflows of a project | | **Get test metadata** `circleci_get_test_metadata` | Fetch test metadata for a specific job | | **Get usage export job** `circleci_get_usage_export_job` | Retrieve a usage export job by organization ID and job ID | | **Get user information** `circleci_get_user_information` | Retrieve information about a CircleCI user by their unique ID | | **Get workflow summary** `circleci_get_workflow_summary` | Get metrics and trends for a workflow | | **List context env vars** `circleci_list_context_env_vars` | List all environment variables for a specific context | | **List insights branches** `circleci_list_insights_branches` | Get all branches for a project from CircleCI Insights | | **List insights summary** `circleci_list_insights_summary` | Get summary metrics with trends for the entire organization and for each project | | **List namespace orbs** `circleci_list_namespace_orbs` | List orbs in a CircleCI registry namespace with pagination support | | **List orb categories** `circleci_list_orb_categories` | Retrieve all CircleCI orb categories with pagination support | | **List orbs** `circleci_list_orbs` | List CircleCI orbs with pagination support via GraphQL API | | **List organization groups** `circleci_list_organization_groups` | List all groups in a CircleCI organization | | **List pages summary** `circleci_list_pages_summary` | Get summary metrics and trends for a project across its workflows and branches | | **List pipeline definitions** `circleci_list_pipeline_definitions` | List all pipeline definitions for a specific project | | **List pipelines** `circleci_list_pipelines` | Get a list of pipelines for an organization | | **List pipelines for project** `circleci_list_pipelines_for_project` | List all pipelines for a specific project | | **List project env vars** `circleci_list_project_env_vars` | List all environment variables for a CircleCI project | ## Example prompts **Create Usage Export Job** > Create it in CircleCI for me, then confirm the important fields before you finish. **Get Context** > Pull the relevant data from CircleCI, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from CircleCI, summarize it in plain English, and point out anything that needs attention. **Get Flaky Tests** > Pull the relevant data from CircleCI, 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 CircleCI working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CircleCI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CircleCI 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 CircleCI. | 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 CircleCI actions to the runtime in a format your agent can reliably use. | 65 tools for CircleCI are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CircleCI 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 CircleCI in the browser, and the 65 tools above work from chat. There is no SDK and no config file, and the CircleCI 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 CircleCI skill but can't call the tools The ClawHub skill teaches OpenClaw about CircleCI, but the calls run through the ClawLink plugin and your connected account. Make sure CircleCI 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 CircleCI 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 CircleCI tools CircleCI 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 CircleCI 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. ### CircleCI 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 CircleCI has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw CircleCI integration? Yes. ClawLink is the fastest way to connect OpenClaw to CircleCI: link your CircleCI account once in the browser and OpenClaw can call the CircleCI API through 65 ready-made tools — no custom code or token handling. ### How do I add CircleCI to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink CircleCI skill from ClawHub, then you click Connect in the dashboard to authorize CircleCI. OpenClaw calls the tools from the next message — no config files, and the CircleCI key you paste is stored server-side instead of in your environment. ### How long does it take to connect CircleCI to OpenClaw? About two minutes. Sign in, click Connect next to CircleCI in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring CircleCI 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 CircleCI working from chat. ### OpenClaw installed the CircleCI skill but can't call the tools The ClawHub skill teaches OpenClaw about CircleCI, but the calls run through the ClawLink plugin and your connected account. Make sure CircleCI 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 - [PagerDuty](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.