How to connect Crowdin to OpenClaw
Connect Crowdin to OpenClaw with ClawLink in one click — 230 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.


Manage translations, localization projects, and language resources. Once connected, OpenClaw can read and act on Crowdin from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Crowdin 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 Crowdin setup: install one ClawHub skill, connect Crowdin in the browser, and OpenClaw can call real Crowdin actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Crowdin skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Crowdin" (hith3sh/crowdin) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/crowdin
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Crowdin.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Crowdin
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Crowdin?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Crowdin in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Crowdin to check bundle export status 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Crowdin is connected in the dashboard, that agent calls the same 230 Crowdin tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Crowdin MCP for OpenClaw
Looking for a Crowdin MCP server for OpenClaw? ClawLink connects Crowdin to OpenClaw and exposes 230 Crowdin tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Crowdin integration works the same way.
What the OpenClaw Crowdin integration can do
230 Crowdin 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 230.
30 of 230 Crowdin tools for OpenClaw
| Tool | What it does |
|---|---|
Check bundle export status crowdin_check_bundle_export_status | Check the status of a bundle export operation in Crowdin |
Check glossary export status crowdin_check_glossary_export_status | Check the status of a glossary export operation |
Check glossary import status crowdin_check_glossary_import_status | Check the status of a glossary import operation |
Check graphql rate limit crowdin_check_graphql_rate_limit | Check GraphQL API rate limit status for Crowdin |
Check project report crowdin_check_project_report | Check report generation status in a Crowdin project |
Check projects translations builds crowdin_check_projects_translations_builds | Check the status of a project translation build in Crowdin |
Check tm export status crowdin_check_tm_export_status | Check Translation Memory export status in Crowdin |
Check tm import status crowdin_check_tm_import_status | Check Translation Memory import status in Crowdin |
Check users AI reports crowdin_check_users_ai_reports | Check the generation status of an AI report for a Crowdin user |
Create mts translations crowdin_create_mts_translations | Translate strings using Crowdin's Machine Translation engine |
Download file crowdin_download_file | Download a file from a Crowdin project |
Download glossaries exports download crowdin_download_glossaries_exports_download | Download an exported glossary from Crowdin |
Download projects bundles exports download crowdin_download_projects_bundles_exports_download | Download an exported bundle from Crowdin |
Download projects reports download crowdin_download_projects_reports_download | Download a generated project report from Crowdin |
Download projects translations builds download crowdin_download_projects_translations_builds_download | Download a built project translation from Crowdin |
Download tms exports download crowdin_download_tms_exports_download | Download an exported Translation Memory from Crowdin |
Download users AI reports download crowdin_download_users_ai_reports_download | Download an AI report from Crowdin |
Execute graphql query crowdin_execute_graphql_query | Execute GraphQL queries against the Crowdin GraphQL API |
Export projects translations exports crowdin_export_projects_translations_exports | Export project translations from Crowdin |
Get branch crowdin_get_branch | Retrieve details of a specific branch in a Crowdin project by its ID |
Get file crowdin_get_file | Retrieve detailed information about a specific file in a Crowdin project |
Get glossary crowdin_get_glossary | Retrieve information about a specific glossary by its ID |
Get glossary concept crowdin_get_glossary_concept | Retrieve a specific concept from a Crowdin glossary |
Get glossary term crowdin_get_glossary_term | Retrieve a specific term from a Crowdin glossary |
Get label crowdin_get_label | Retrieve information about the label identified by the specified label ID in a project |
Get language crowdin_get_language | Retrieve details of a specific language |
Get member info crowdin_get_member_info | Retrieve information about a project member |
Get mt crowdin_get_mt | Retrieve details of a specific Machine Translation engine |
Get project crowdin_get_project | Retrieve details of a specific Crowdin project |
Get project task crowdin_get_project_task | Retrieve details of a specific task in a Crowdin project |
Try it: find the Crowdin tool you need
Browse the 30 Crowdin tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Crowdin to check bundle export status and walk me through the result in plain English.
Use Crowdin to check glossary export status and walk me through the result in plain English.
Use Crowdin to check glossary import status and walk me through the result in plain English.
Use Crowdin to check graphql rate limit and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Crowdin working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Crowdin app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Crowdin through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Crowdin. | 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 Crowdin actions to the runtime in a format your agent can reliably use. | 230 tools for Crowdin are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Crowdin 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 Crowdin in the browser, and the 230 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Crowdin skill but can't call the tools
The ClawHub skill teaches OpenClaw about Crowdin, but the calls run through the ClawLink plugin and your connected account. Make sure Crowdin 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 Crowdin 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 Crowdin tools
Crowdin 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 Crowdin 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.
Crowdin 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Crowdin and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Crowdin integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Crowdin: link your Crowdin account once in the browser and OpenClaw can call the Crowdin API through 230 ready-made tools — no custom code or token handling.
How do I add Crowdin to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Crowdin skill from ClawHub, then you click Connect in the dashboard to authorize Crowdin. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Crowdin to OpenClaw?
About two minutes. Sign in, click Connect next to Crowdin in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Crowdin up myself?
The alternative to ClawLink is usually manual OAuth app 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 Crowdin working from chat.
OpenClaw installed the Crowdin skill but can't call the tools
The ClawHub skill teaches OpenClaw about Crowdin, but the calls run through the ClawLink plugin and your connected account. Make sure Crowdin 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
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.