# How to connect SimpleLocalize to OpenClaw (paste one key, 14 tools) > Connect SimpleLocalize to OpenClaw with ClawLink: paste your SimpleLocalize 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/simple-localize The usual route to SimpleLocalize 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 SimpleLocalize setup: install one ClawHub skill, connect SimpleLocalize in the browser, and OpenClaw can call real SimpleLocalize 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 SimpleLocalize. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect SimpleLocalize** — 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 simple-localize # connect SimpleLocalize (browser OAuth) npx -y @useclawlink/cli actions simple-localize # list available actions npx -y @useclawlink/cli run simple-localize --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 SimpleLocalize in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your SimpleLocalize API key once. Verify the connection by asking OpenClaw: > Use SimpleLocalize to export translations 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 SimpleLocalize is connected in the dashboard, that agent calls the same 14 SimpleLocalize 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). ## SimpleLocalize MCP for OpenClaw Looking for a SimpleLocalize MCP server for OpenClaw? ClawLink connects SimpleLocalize to OpenClaw and exposes 14 SimpleLocalize 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 SimpleLocalize integration](https://claw-link.dev/hermes/simple-localize) works the same way. ## What the OpenClaw SimpleLocalize integration can do 14 SimpleLocalize tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 14. ### 12 of 14 SimpleLocalize tools for OpenClaw | Tool | What it does | |---|---| | **Export translations** `simple_localize_export_translations` | Create downloadable snapshot URLs for project translations in a selected file format | | **Get project context** `simple_localize_get_project_context` | Return the connected project and its current languages, tags, and hosting environments so an | | **Get translation key** `simple_localize_get_translation_key` | Return full metadata for one translation key selected by key and namespace | | **List activity** `simple_localize_list_activity` | Return a manually selected page of recent project changes for operational visibility | | **List file formats** `simple_localize_list_file_formats` | Return the file formats currently accepted by SimpleLocalize exports, including multi-language | | **List translation keys** `simple_localize_list_translation_keys` | Search translation keys and return one controllable page of provider summary fields | | **List translations** `simple_localize_list_translations` | Search translations by key, language, text, review state, or namespace and return one page | | **Create tag** `simple_localize_create_tag` | Create a project tag for organizing translation keys | | **Create translation key** `simple_localize_create_translation_key` | Create one translation key and optional metadata in the connected project | | **Create translation keys** `simple_localize_create_translation_keys` | Create up to 100 translation keys and report every rejected entry; valid entries may still be | | **Set translation** `simple_localize_set_translation` | Set the text and optional review state for one existing translation key and language | | **Set translations** `simple_localize_set_translations` | Set 1 to 100 translations in one request | ## Example prompts **Export Translations** > Use SimpleLocalize to export translations and walk me through the result in plain English. **Get Project Context** > Pull the relevant data from SimpleLocalize, summarize it in plain English, and point out anything that needs attention. **Get Translation Key** > Pull the relevant data from SimpleLocalize, summarize it in plain English, and point out anything that needs attention. **List Activity** > List the relevant items in SimpleLocalize, 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 SimpleLocalize working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the SimpleLocalize API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SimpleLocalize 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 SimpleLocalize. | 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 SimpleLocalize actions to the runtime in a format your agent can reliably use. | 14 tools for SimpleLocalize are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes SimpleLocalize 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 SimpleLocalize in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the SimpleLocalize 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 SimpleLocalize skill but can't call the tools The ClawHub skill teaches OpenClaw about SimpleLocalize, but the calls run through the ClawLink plugin and your connected account. Make sure SimpleLocalize 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 SimpleLocalize 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 SimpleLocalize tools SimpleLocalize 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 SimpleLocalize 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. ### SimpleLocalize 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 SimpleLocalize has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw SimpleLocalize integration? Yes. ClawLink is the fastest way to connect OpenClaw to SimpleLocalize: link your SimpleLocalize account once in the browser and OpenClaw can call the SimpleLocalize API through 14 ready-made tools — no custom code or token handling. ### How do I add SimpleLocalize to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SimpleLocalize skill from ClawHub, then you click Connect in the dashboard to authorize SimpleLocalize. OpenClaw calls the tools from the next message — no config files, and the SimpleLocalize key you paste is stored server-side instead of in your environment. ### How long does it take to connect SimpleLocalize to OpenClaw? About two minutes. Sign in, click Connect next to SimpleLocalize in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring SimpleLocalize 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 SimpleLocalize working from chat. ### OpenClaw installed the SimpleLocalize skill but can't call the tools The ClawHub skill teaches OpenClaw about SimpleLocalize, but the calls run through the ClawLink plugin and your connected account. Make sure SimpleLocalize 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 tools](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 - [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.