# How to connect Codacy to OpenClaw (paste one key, 18 tools) > Connect Codacy to OpenClaw with ClawLink: paste your Codacy key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/codacy The usual route to Codacy 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 Codacy setup: install one ClawHub skill, connect Codacy in the browser, and OpenClaw can call real Codacy 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 Codacy. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Codacy** — 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 codacy # connect Codacy (browser OAuth) npx -y @useclawlink/cli actions codacy # list available actions npx -y @useclawlink/cli run codacy --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 Codacy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Codacy API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Codacy, summarize it in plain English, and point out anything that needs attention. ### 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 Codacy is connected in the dashboard, that agent calls the same 18 Codacy 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). ## Codacy MCP for OpenClaw Looking for a Codacy MCP server for OpenClaw? ClawLink connects Codacy to OpenClaw and exposes 18 Codacy 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 Codacy integration](https://claw-link.dev/hermes/codacy) works the same way. ## What the OpenClaw Codacy integration can do 18 Codacy tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 18. ### 17 of 18 Codacy tools for OpenClaw | Tool | What it does | |---|---| | **Get account details** `codacy_get_account_details` | Retrieve details of the authenticated user's account | | **Get configuration status** `codacy_get_configuration_status` | Retrieve the current configuration status of the Codacy system | | **Get health** `codacy_get_health` | Check the health status of the Codacy API | | **Get organizations repositories settings languages** `codacy_get_organizations_repositories_settings_languages` | Get the list of all languages with their extensions and enabled status for a repository | | **Get tool pattern** `codacy_get_tool_pattern` | Retrieve the definition of a specific pattern for a given tool | | **Get user organizations** `codacy_get_user_organizations` | Retrieves all organizations the authenticated user belongs to for a specific Git provider | | **Get version** `codacy_get_version` | Retrieve the version of the Codacy installation | | **List analysis organizations repositories** `codacy_list_analysis_organizations_repositories` | List organization repositories with analysis information for the authenticated user | | **List duplication tools** `codacy_list_duplication_tools` | Retrieve the list of duplication detection tools available in Codacy | | **List languages tools** `codacy_list_languages_tools` | Retrieve the list of languages supported by available tools | | **List login integrations** `codacy_list_login_integrations` | List configured login providers on Codacy's platform | | **List metrics tools** `codacy_list_metrics_tools` | Retrieve the list of metrics tools available in Codacy | | **List projects** `codacy_list_projects` | List all projects accessible to the authenticated user | | **List provider integrations** `codacy_list_provider_integrations` | List provider integrations existing on Codacy's platform | | **List tools** `codacy_list_tools` | Retrieve the list of analysis tools available in Codacy | | **List tools patterns** `codacy_list_tools_patterns` | Retrieve the list of patterns for a specific tool | | **Create API token** `codacy_create_api_token` | Creates a new account API token for the authenticated user | ## Example prompts **Get Account Details** > Pull the relevant data from Codacy, summarize it in plain English, and point out anything that needs attention. **Get Configuration Status** > Pull the relevant data from Codacy, summarize it in plain English, and point out anything that needs attention. **Get Health** > Pull the relevant data from Codacy, summarize it in plain English, and point out anything that needs attention. **Get Organizations Repositories Settings Languages** > Pull the relevant data from Codacy, 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 Codacy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Codacy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Codacy 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 Codacy. | 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 Codacy actions to the runtime in a format your agent can reliably use. | 18 tools for Codacy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Codacy 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 Codacy in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Codacy 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 Codacy skill but can't call the tools The ClawHub skill teaches OpenClaw about Codacy, but the calls run through the ClawLink plugin and your connected account. Make sure Codacy 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 Codacy 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 Codacy tools Codacy 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 Codacy 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. ### Codacy 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 Codacy has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Codacy integration? Yes. ClawLink is the fastest way to connect OpenClaw to Codacy: link your Codacy account once in the browser and OpenClaw can call the Codacy API through 18 ready-made tools — no custom code or token handling. ### How do I add Codacy to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Codacy skill from ClawHub, then you click Connect in the dashboard to authorize Codacy. OpenClaw calls the tools from the next message — no config files, and the Codacy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Codacy to OpenClaw? About two minutes. Sign in, click Connect next to Codacy in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Codacy 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 Codacy working from chat. ### OpenClaw installed the Codacy skill but can't call the tools The ClawHub skill teaches OpenClaw about Codacy, but the calls run through the ClawLink plugin and your connected account. Make sure Codacy 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 - [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.