How to connect Corrently to OpenClaw
Connect Corrently to OpenClaw with ClawLink: paste your Corrently key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine.
CorrentlyAPI KEYMCPCorrently provides a suite of APIs offering real-time and forecasted data on renewable energy availability, CO₂ emissions, and electricity pricing, enabling users to optimize energy consumption and reduce carbon footprints.. Once connected, OpenClaw can read and act on Corrently from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Corrently 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 Corrently setup: install one ClawHub skill, connect Corrently in the browser, and OpenClaw can call real Corrently 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 Corrently.
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 Corrently
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Corrently?"
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 Corrently in the ClawLink dashboard — paste your Corrently API key once.
Verify the connection by asking OpenClaw:
Use Corrently to geocode location 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 Corrently is connected in the dashboard, that agent calls the same 23 Corrently tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Corrently MCP for OpenClaw
Looking for a Corrently MCP server for OpenClaw? ClawLink connects Corrently to OpenClaw and exposes 23 Corrently tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Corrently integration works the same way.
What the OpenClaw Corrently integration can do
23 Corrently tools are ready for OpenClaw once the account is connected.
All 23 Corrently tools for OpenClaw
| Tool | What it does |
|---|---|
Geocode location corrently_geocode_location | Geocode a free-text location into coordinates |
Get metering reading corrently_get_metering_reading | Retrieve metered electricity reading with green/grey energy split and CO2 emissions data |
Get stromkonto balances corrently_get_stromkonto_balances | Retrieve Stromkonto account balances from the energy blockchain ledger |
Get stromkonto choices corrently_get_stromkonto_choices | Get selectable contract choices for a Stromkonto customer |
Get wim process status corrently_get_wim_process_status | Retrieve status information for WiM (Wechselprozesse im Messwesen) metering change processes |
Grunstrom index forecast corrently_grunstrom_index_forecast | Retrieve hourly green power forecast and CO2 data |
Gsi best hour corrently_gsi_best_hour | Determines if now is the best time to turn on a device based on regional green energy |
Market data corrently_market_data | Retrieve real-time and forecast electricity pricing data for Germany by postal code |
Phev navigator corrently_phev_navigator | Get PHEV charge-or-fuel recommendation for German locations |
Pv generation get forecast corrently_pv_generation_get_forecast | Get hourly solar PV generation forecasts for a German location |
Renewable energy dispatch corrently_renewable_energy_dispatch | Get renewable energy flow and mix for a German ZIP code |
Strommix corrently_strommix | Retrieve real-time electricity generation mix in Germany |
Tariff components corrently_tariff_components | Retrieve detailed German electricity tariff cost breakdown by postal code |
Tariff slph0 corrently_tariff_slph0 | Retrieve standard load profile H0 tariff information |
Weather forecast corrently_weather_forecast | Retrieve hourly weather forecasts (wind speed and UV index) by geographic coordinates |
Wim status corrently_wim_status | Check TyDID consent/grant status for an SSI (Self-Sovereign Identity) |
Co2 meter update reading corrently_co2_meter_update_reading | Create or update a CO₂ meter reading for emissions tracking |
Commit quittung corrently_commit_quittung | Finalize a Strom-Quittung (electricity receipt) after collecting transaction data |
Get energy schedule corrently_get_energy_schedule | Create an optimized operation schedule for energy-consuming devices based on the GrünstromIndex |
Login stromkonto corrently_login_stromkonto | Initiate login to Stromkonto via email |
Post metering reading corrently_post_metering_reading | Post a meter reading and get it decorated with green/grey energy split |
Prepare receipt data corrently_prepare_receipt_data | Collect data for a receipt before finalizing |
Register stromkonto corrently_register_stromkonto | Register a new Stromkonto energy account in the Corrently system |
Try it: find the Corrently tool you need
Browse the 23 Corrently tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Corrently to geocode location and walk me through the result in plain English.
Pull the relevant data from Corrently, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Corrently, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Corrently, 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 Corrently working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Corrently API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Corrently 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 Corrently. | 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 Corrently actions to the runtime in a format your agent can reliably use. | 23 tools for Corrently are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Corrently 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 Corrently in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Corrently 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 Corrently skill but can't call the tools
The ClawHub skill teaches OpenClaw about Corrently, but the calls run through the ClawLink plugin and your connected account. Make sure Corrently 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 Corrently 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 Corrently tools
Corrently 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 Corrently 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.
Corrently 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 Corrently 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 Corrently integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Corrently: link your Corrently account once in the browser and OpenClaw can call the Corrently API through 23 ready-made tools — no custom code or token handling.
How do I add Corrently to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Corrently skill from ClawHub, then you click Connect in the dashboard to authorize Corrently. OpenClaw calls the tools from the next message — no config files, and the Corrently key you paste is stored server-side instead of in your environment.
How long does it take to connect Corrently to OpenClaw?
About two minutes. Sign in, click Connect next to Corrently in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Corrently 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 Corrently working from chat.
OpenClaw installed the Corrently skill but can't call the tools
The ClawHub skill teaches OpenClaw about Corrently, but the calls run through the ClawLink plugin and your connected account. Make sure Corrently 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.
