How to connect Opencage to OpenClaw
Connect Opencage to OpenClaw with ClawLink: paste your Opencage key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
OpencageAPI KEYMCPOpenCage Geocoder provides a simple API for forward and reverse geocoding using open data sources.. Once connected, OpenClaw can read and act on Opencage from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Opencage 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 Opencage setup: install one ClawHub skill, connect Opencage in the browser, and OpenClaw can call real Opencage 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 Opencage.
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 Opencage
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Opencage?"
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 Opencage in the ClawLink dashboard — paste your Opencage API key once.
Verify the connection by asking OpenClaw:
Use Opencage to geocode forward 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 Opencage is connected in the dashboard, that agent calls the same 7 Opencage tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Opencage MCP for OpenClaw
Looking for a Opencage MCP server for OpenClaw? ClawLink connects Opencage to OpenClaw and exposes 7 Opencage tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Opencage integration works the same way.
What the OpenClaw Opencage integration can do
7 Opencage tools are ready for OpenClaw once the account is connected.
All 7 Opencage tools for OpenClaw
| Tool | What it does |
|---|---|
Geocode forward opencage_geocode_forward | Convert a human-readable address into geographic coordinates |
Geocode geojson opencage_geocode_geojson | Geocode addresses or coordinates and return results in GeoJSON FeatureCollection format |
Geocode geojsonp opencage_geocode_geojsonp | Geocode an address and return results wrapped in a JavaScript callback function (JSONP format) |
Geocode google v3 json opencage_geocode_google_v3_json | Perform forward geocoding and return results in Google Geocoding API v3 compatible JSON format |
Geocode reverse opencage_geocode_reverse | Convert coordinates to a human-readable address |
Geocode xml opencage_geocode_xml | Geocode a location query and return results in XML format |
Ping opencage opencage_ping_opencage | Check API health and connectivity |
Try it: find the Opencage tool you need
Browse the 7 Opencage tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Opencage to geocode forward and walk me through the result in plain English.
Use Opencage to geocode geojson and walk me through the result in plain English.
Use Opencage to geocode geojsonp and walk me through the result in plain English.
Use Opencage to geocode google v3 json and walk me through the result in plain English.
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 Opencage working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Opencage API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Opencage 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 Opencage. | 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 Opencage actions to the runtime in a format your agent can reliably use. | 7 tools for Opencage are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Opencage 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 Opencage in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Opencage key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Opencage skill but can't call the tools
The ClawHub skill teaches OpenClaw about Opencage, but the calls run through the ClawLink plugin and your connected account. Make sure Opencage 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 Opencage 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 Opencage tools
Opencage 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 Opencage 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.
Opencage 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 Opencage has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Opencage integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Opencage: link your Opencage account once in the browser and OpenClaw can call the Opencage API through 7 ready-made tools — no custom code or token handling.
How do I add Opencage to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Opencage skill from ClawHub, then you click Connect in the dashboard to authorize Opencage. OpenClaw calls the tools from the next message — no config files, and the Opencage key you paste is stored server-side instead of in your environment.
How long does it take to connect Opencage to OpenClaw?
About two minutes. Sign in, click Connect next to Opencage in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Opencage 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 Opencage working from chat.
OpenClaw installed the Opencage skill but can't call the tools
The ClawHub skill teaches OpenClaw about Opencage, but the calls run through the ClawLink plugin and your connected account. Make sure Opencage 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
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
Connect 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.