Solcast for AI agents
Solcast provides solar irradiance and PV power forecasts worldwide, used by solar developers and utilities to plan generation and grid balancing. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Solcast.
Pull a forecast for a solar site
Get the PV power forecast for a registered site to plan generation for the next day.
Check historical radiation for a location
Get historic radiation and weather data for a site to validate a forecast model's assumptions.
Register a new PV site
Create a PV power resource for a new site once its location and capacity are confirmed.
6 Solcast actions, graded by risk.
Every Solcast action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- solcast.get_resources_pv_power_siteGet PV Power Resource
- solcast.get_resources_pv_power_sitesGet Resources PV Power Sites
- solcast.get_data_historic_radiation_and_weatherGet Historic Radiation And Weather
write
3Create and change things. Allow, or ask the user first.
- solcast.post_resources_pv_power_siteCreate PV Power Resource
- solcast.put_resources_pv_power_siteUpdate PV Power Resource
- solcast.patch_resources_pv_power_sitePatch PV Power Resource
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Solcast in three steps.
- 01Your users connect SolcastThey add their Solcast api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create PV Power Resource” can wait for the user to approve.
- 03Any agent can actYour agent calls Solcast through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('solcast', { read: 'allow', write: 'ask', // post_resources_pv_power_site destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Solcast connects.
Users add their Solcast api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Solcast connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Solcast from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Solcast and Arc0, answered.
Can I use Solcast with Claude, ChatGPT or Cursor?
Yes. Connect Solcast to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Solcast actions you allow.
How do users connect Solcast?
Users add their Solcast api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Solcast actions can my agent take?
6 in total: 3 read, 3 write and 0 destructive, such as “create PV Power Resource”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Solcast?
Yes. Allow read actions and deny writes in the Solcast policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Solcast too?
Yes. The same Solcast connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Solcast into your agent.
Your users connect Solcast once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan