How to connect Solcast to OpenClaw
Connect Solcast to OpenClaw with ClawLink: paste your Solcast key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
SolcastAPI KEYMCPSolar resource assessment and forecasting data for irradiance and PV power, globally.. Once connected, OpenClaw can read and act on Solcast from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Solcast 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 Solcast setup: install one ClawHub skill, connect Solcast in the browser, and OpenClaw can call real Solcast 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 Solcast.
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 Solcast
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Solcast?"
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 Solcast in the ClawLink dashboard — paste your Solcast API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Solcast, summarize it in plain English, and point out anything that needs attention.
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 Solcast is connected in the dashboard, that agent calls the same 6 Solcast tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Solcast MCP for OpenClaw
Looking for a Solcast MCP server for OpenClaw? ClawLink connects Solcast to OpenClaw and exposes 6 Solcast tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Solcast integration works the same way.
What the OpenClaw Solcast integration can do
6 Solcast tools are ready for OpenClaw once the account is connected.
All 6 Solcast tools for OpenClaw
| Tool | What it does |
|---|---|
Get data historic radiation and weather solcast_get_data_historic_radiation_and_weather | Get historical irradiance and weather estimated actuals for a requested location |
Get resources pv power site solcast_get_resources_pv_power_site | Retrieve a specific PV power resource by its unique identifier |
Get resources pv power sites solcast_get_resources_pv_power_sites | List PV power resources available to authenticated user |
Patch resources pv power site solcast_patch_resources_pv_power_site | Partially update an existing PV power resource's technical specifications |
Post resources pv power site solcast_post_resources_pv_power_site | Create a new PV power resource for Advanced PV Power forecasting |
Put resources pv power site solcast_put_resources_pv_power_site | Update an existing PV power resource with comprehensive technical specifications for solar |
Try it: find the Solcast tool you need
Browse the 6 Solcast tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Solcast, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Solcast, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Solcast, summarize it in plain English, and point out anything that needs attention.
Use Solcast to patch resources pv power site 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 Solcast working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Solcast API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Solcast 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 Solcast. | 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 Solcast actions to the runtime in a format your agent can reliably use. | 6 tools for Solcast are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Solcast 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 Solcast in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Solcast 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 Solcast skill but can't call the tools
The ClawHub skill teaches OpenClaw about Solcast, but the calls run through the ClawLink plugin and your connected account. Make sure Solcast 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 Solcast 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 Solcast tools
Solcast 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 Solcast 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.
Solcast 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 Solcast 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 Solcast integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Solcast: link your Solcast account once in the browser and OpenClaw can call the Solcast API through 6 ready-made tools — no custom code or token handling.
How do I add Solcast to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Solcast skill from ClawHub, then you click Connect in the dashboard to authorize Solcast. OpenClaw calls the tools from the next message — no config files, and the Solcast key you paste is stored server-side instead of in your environment.
How long does it take to connect Solcast to OpenClaw?
About two minutes. Sign in, click Connect next to Solcast in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Solcast 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 Solcast working from chat.
OpenClaw installed the Solcast skill but can't call the tools
The ClawHub skill teaches OpenClaw about Solcast, but the calls run through the ClawLink plugin and your connected account. Make sure Solcast 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.
