# How to connect Codereadr to OpenClaw (paste one key, 16 tools) > Connect Codereadr to OpenClaw with ClawLink: paste your Codereadr key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/codereadr The usual route to Codereadr 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 Codereadr setup: install one ClawHub skill, connect Codereadr in the browser, and OpenClaw can call real Codereadr 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 Codereadr. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Codereadr** — 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 codereadr # connect Codereadr (browser OAuth) npx -y @useclawlink/cli actions codereadr # list available actions npx -y @useclawlink/cli run codereadr --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 Codereadr in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Codereadr API key once. Verify the connection by asking OpenClaw: > Use Codereadr to configure connector 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 Codereadr is connected in the dashboard, that agent calls the same 16 Codereadr 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). ## Codereadr MCP for OpenClaw Looking for a Codereadr MCP server for OpenClaw? ClawLink connects Codereadr to OpenClaw and exposes 16 Codereadr 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 Codereadr integration](https://claw-link.dev/hermes/codereadr) works the same way. ## What the OpenClaw Codereadr integration can do 16 Codereadr tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 16. ### 11 of 16 Codereadr tools for OpenClaw | Tool | What it does | |---|---| | **Configure connector** `codereadr_configure_connector` | Helper to guide configuring the CodeREADr Connector for Google Sheets | | **Generate scan link** `codereadr_generate_scan_link` | Generates a CodeREADr scan link URI that opens the CodeREADr mobile app with a pre-filled scan | | **List supported barcode types** `codereadr_list_supported_barcode_types` | Lists barcode symbologies supported by CodeREADr for scanning | | **Retrieve databases** `codereadr_retrieve_databases` | Retrieves all validation databases configured in your CodeREADr account | | **Retrieve devices** `codereadr_retrieve_devices` | Retrieve a list of devices registered to your CodeREADr account | | **Retrieve scans** `codereadr_retrieve_scans` | Retrieve scan records from your CodeREADr account | | **Retrieve services** `codereadr_retrieve_services` | Retrieve configured services from your CodeREADr account | | **Collect data with questions** `codereadr_collect_data_with_questions` | Create and attach custom questions to a CodeREADr service for data collection after scans | | **Create service** `codereadr_create_service` | Creates a new CodeREADr service (barcode scanning workflow configuration) | | **Update question** `codereadr_update_question` | Add answer options to an existing CodeREADr question | | **Update service** `codereadr_update_service` | Update an existing CodeREADr service configuration | ## Example prompts **Configure Connector** > Use Codereadr to configure connector and walk me through the result in plain English. **Generate Scan Link** > Use Codereadr to generate scan link and walk me through the result in plain English. **List Supported Barcode Types** > List the relevant items in Codereadr, group them by priority, and recommend what OpenClaw should do next. **Retrieve Databases** > Pull the relevant data from Codereadr, 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 Codereadr working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Codereadr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Codereadr 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 Codereadr. | 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 Codereadr actions to the runtime in a format your agent can reliably use. | 16 tools for Codereadr are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Codereadr 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 Codereadr in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Codereadr 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 Codereadr skill but can't call the tools The ClawHub skill teaches OpenClaw about Codereadr, but the calls run through the ClawLink plugin and your connected account. Make sure Codereadr 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 Codereadr 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 Codereadr tools Codereadr 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 Codereadr 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. ### Codereadr 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 Codereadr has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Codereadr integration? Yes. ClawLink is the fastest way to connect OpenClaw to Codereadr: link your Codereadr account once in the browser and OpenClaw can call the Codereadr API through 16 ready-made tools — no custom code or token handling. ### How do I add Codereadr to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Codereadr skill from ClawHub, then you click Connect in the dashboard to authorize Codereadr. OpenClaw calls the tools from the next message — no config files, and the Codereadr key you paste is stored server-side instead of in your environment. ### How long does it take to connect Codereadr to OpenClaw? About two minutes. Sign in, click Connect next to Codereadr in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Codereadr 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 Codereadr working from chat. ### OpenClaw installed the Codereadr skill but can't call the tools The ClawHub skill teaches OpenClaw about Codereadr, but the calls run through the ClawLink plugin and your connected account. Make sure Codereadr 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.