4,500+ servers built on MCP Fusion
Vinkius

Solcast Solar MCP. Predict PV output using precise site data.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Solcast Solar MCP on Cursor AI Code Editor MCP Client Solcast Solar MCP on Claude Desktop App MCP Integration Solcast Solar MCP on OpenAI Agents SDK MCP Compatible Solcast Solar MCP on Visual Studio Code MCP Extension Client Solcast Solar MCP on GitHub Copilot AI Agent MCP Integration Solcast Solar MCP on Google Gemini AI MCP Integration Solcast Solar MCP on Lovable AI Development MCP Client Solcast Solar MCP on Mistral AI Agents MCP Compatible Solcast Solar MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Solcast Solar MCP Server predicts PV energy yield by connecting directly to high-resolution solar forecasting data. It gives you detailed, location-specific forecasts for rooftop solar systems, including power output (kW), Global Horizontal Irradiance (GHI), Direct Normal Irradiance (DNI), and local weather conditions.

What your AI agents can do

Get detailed pv forecast

Calculates highly accurate PV power output using exact system geometry (tilt, azimuth) parameters.

Get historical radiation

Retrieves past solar irradiance values (GHI, DNI, etc.) for a specific location and time range.

Get pv power forecasts

Generates expected power output forecasts using satellite cloud tracking data for a given site capacity.

+ 8 more capabilities included
Calculate Detailed PV Power Output

You ask your agent to predict power output using specific angles (tilt/azimuth) and system size for maximum accuracy.

Model System Performance with Site IDs

The agent pulls forecasts or estimated actuals for a known, registered rooftop site ID.

Assess Raw Solar Resource Potential

You get the core sunlight metrics (GHI, DNI, DHI) needed to judge if a location is viable for solar power.

Estimate Quick Power Yields

The agent runs a fast forecast using only basic inputs like latitude, longitude, and system capacity. Good for initial scoping calls.

Track System History & Weather Impacts

You get data on measured production or concurrent weather forecasts (temperature, cloud opacity) to audit performance.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Solcast Solar: 11 Tools for PV Energy Forecasting

These tools allow your agent to calculate power output estimates and retrieve detailed solar resource data across various systems.

get019d760a

get detailed pv forecast

Calculates highly accurate PV power output using exact system geometry (tilt, azimuth) parameters.

get019d760a

get historical radiation

Retrieves past solar irradiance values (GHI, DNI, etc.) for a specific location and time range.

get019d760a

get pv power forecasts

Generates expected power output forecasts using satellite cloud tracking data for a given site capacity.

get019d760a

get radiation forecasts

Predicts raw solar irradiance metrics (GHI, DNI, DHI) needed for general solar resource assessment in an area.

get019d760a

get simple pv forecast

Provides a fast PV power forecast using minimal inputs—just latitude, longitude, and system capacity.

get019d760a

get site estimated actuals

Retrieves estimated recent PV output for a specific registered site ID when measured data isn't available.

get019d760a

get site forecasts

Predicts power output specifically for a known, registered rooftop site ID using its stored parameters.

get019d760a

get site measured actuals

Pulls the exact measured PV power output from a registered, telemetry-enabled site over time.

get019d760a

get solar summary

Combines irradiance, weather, and PV data into one overview for a complete solar resource assessment.

get019d760a

get weather forecasts

Predicts environmental factors like air temperature, cloud opacity, and snow depth that affect solar output.

list019d760a

list rooftop sites

Lists all unique site IDs, capacities, and locations configured in your Solcast account.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Solcast Solar, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Solcast gives your agent deep solar forecasting intel. You're connecting directly to high-resolution data that tracks everything affecting a PV system, from satellite cloud movement to historical radiation records.

Site Management and Quick Scopes

Need to know what you're working with? Start by running list_rooftop_sites. This tool pulls all unique site IDs, capacities, and locations configured in your Solcast account. If you just need a quick estimate for an initial scoping call, use get_simple_pv_forecast. You only have to feed it latitude, longitude, and system capacity; that's all it needs.

Modeling Known Sites (The Deep Dive)

When you know the site, you get precise results. To model a known, registered rooftop array, use get_site_forecasts. This tool pulls power output predictions specifically tied to that site ID and its stored parameters. If you're trying to audit performance or predict yields when measured data isn't available, run get_site_estimated_actuals using the specific site ID.

For maximum accuracy—the kind of detailed modeling that matters—you’ll want to use get_detailed_pv_forecast. This function requires you to input exact system geometry parameters like tilt and azimuth angle. That gives you the most accurate possible power output prediction.

Assessing Raw Resource Potential

Sometimes, you don't know the site yet; you just need to judge if a location is viable for solar. For that, you look at raw sunlight metrics using get_radiation_forecasts. This predicts core irradiance values: GHI, DNI, and DHI. You also get general resource assessment data with get_solar_summary, which combines irradiance, weather, and PV data into one full picture.

If the area is broader and you just need to predict raw power output using satellite cloud tracking for a given site capacity, use get_pv_power_forecasts.

Analyzing System Performance and History

To check how things really are going, your agent can pull measured data. Running get_site_measured_actuals pulls the exact PV power output from any registered, telemetry-enabled site over time. For validating models or analyzing past performance trends, use get_historical_radiation. This retrieves years of actual solar irradiance readings (GHI, DNI, etc.) for a specific location and time range.

You'll also need to factor in the environment. Use get_weather_forecasts to predict environmental factors like air temperature, cloud opacity, and snow depth—these things drastically affect your final output. For general resource assessment that combines everything into one view, run get_solar_summary. You can also get raw predictions for key irradiance metrics by calling get_radiation_forecasts.

This toolkit lets you go from a quick estimate to a full-blown performance audit in minutes.

How Solcast Solar MCP Works

  1. 1 First, subscribe to the server and provide your Solcast API key. This connects the necessary solar resource models to your AI client.
  2. 2 Next, prompt your agent with a specific requirement: 'I need an estimate for X kW at Y coordinates' or 'What was the historical GHI data for Z?'
  3. 3 Your agent selects the right tool (e.g., get_detailed_pv_forecast) and runs the query, returning raw power estimates, irradiance values, or weather metrics.

The bottom line is: you tell your AI client what solar data you need—whether it's a quick estimate or historical proof—and it executes the necessary API calls to get the numbers.

Who Is Solcast Solar MCP For?

Solar installers, grid operators, and energy traders rely on this daily. They hate guessing potential yield based on general weather reports; they need site-specific power models that account for panel orientation and historical data to guarantee bids or maintain the grid.

Solar Installer

Calculates accurate PV production estimates for clients, using get_detailed_pv_forecast when they know the exact tilt and azimuth. They use this to size systems correctly before the bid.

Grid Operator

Predicts distributed solar generation forecasts across multiple sites. They use list_rooftop_sites to track all connected assets and predict output for grid balancing.

Energy Trader

Integrates solar forecast data into energy trading models. They rely on get_solar_summary and get_weather_forecasts to predict supply peaks and manage dispatch planning.

Research Scientist

Validates academic models by retrieving historical solar irradiance data (get_historical_radiation) for specific time periods and locations.

What Changes When You Connect

  • Accurate System Sizing: Use get_detailed_pv_forecast when you know the panel tilt and azimuth. This is how you guarantee a bid—it accounts for geometry, not just location.
  • Audit Performance: Compare what should have happened versus reality by calling get_site_estimated_actuals or get_site_measured_actuals. It shows if your system hit its targets.
  • Quick Scoping: Need a rough number fast? Use get_simple_pv_forecast. You only need to pass the latitude, longitude, and capacity. No geometry required.
  • Full Resource Picture: The get_solar_summary tool bundles irradiance, weather predictions, and PV estimates into one call. It’s better than running four different queries.
  • Understanding Limitations: Use get_weather_forecasts to check for cloud opacity or temperature drops before you even run the forecast. This lets you warn clients about expected reductions.

Real-World Use Cases

01

Sizing a New Commercial Rooftop

A client has a building at 34.05, -118.24 and wants to know the maximum power output from a 10kW array. The agent calls get_detailed_pv_forecast, inputting the known tilt (e.g., 25°) and azimuth (e.g., 180°). The result gives them the precise, guaranteed kW estimate needed for the proposal.

02

Auditing a Flailing Site

The site owner suspects their system is underperforming. First, they call list_rooftop_sites to get the ID. Then, they run get_site_measured_actuals for that ID over 168 hours (one week) to see if the actual production matches historical expectations.

03

Market Feasibility Study

A developer is looking at a whole new area and needs to assess its solar potential before buying land. They use get_radiation_forecasts or get_solar_summary for the coordinates, confirming that GHI/DNI are high enough to justify the investment.

04

Optimizing Charging Schedules

An EV owner wants to charge their car using solar power. They ask for a forecast and the agent calls get_pv_power_forecasts. The resulting hourly kW output tells them exactly when they need to plug in to maximize green energy usage.

The Tradeoffs

Guessing Site ID

Trying to guess the correct site ID for a client's installation and running get_site_forecasts with a random string like 'xyz-123'. This will fail because the server needs an exact, registered ID.

Always start by calling list_rooftop_sites. Once you have the official site ID from that list, then run any specific query using tools like get_site_forecasts or get_site_estimated_actuals.

Using General Weather for Output

Simply calling get_weather_forecasts and assuming the temperature or cloud opacity is enough to calculate power. This ignores the physical geometry of the panels.

Use get_solar_summary. It takes weather data and location/capacity, combining it with PV physics calculations for a much more accurate output estimate.

Ignoring System Geometry

Running get_pv_power_forecasts when the system is known to be non-standard (e.g., tilted at 45°). This assumes default settings, leading to inaccurate numbers.

When precision matters, use get_detailed_pv_forecast. It forces you to include the tilt and azimuth parameters for accurate modeling.

When It Fits, When It Doesn't

Use this server if your goal is to calculate a numerical estimate of electrical power (kW or kWh) based on solar physics. This includes project sizing, performance auditing, or resource assessment.

Don't use it if you just need general environmental data—for example, if you only want the average temperature for the week without knowing how panels react. For that, basic weather APIs might suffice. Also, if your primary goal is market trend analysis (e.g., predicting carbon prices), this solar tool won't help.

The key decision point is precision: If you have the panel tilt and azimuth angles, use get_detailed_pv_forecast. If you are only doing a quick feasibility check with minimal data, use get_simple_pv_forecast. Always cross-reference forecasts against measured actuals using get_site_measured_actuals if they exist—that's your ground truth.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Solcast. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_detailed_pv_forecast get_historical_radiation get_pv_power_forecasts get_radiation_forecasts get_simple_pv_forecast get_site_estimated_actuals get_site_forecasts get_site_measured_actuals get_solar_summary get_weather_forecasts list_rooftop_sites

Figuring out solar output shouldn't require 15 clicks and three different logins.

Today, estimating a site’s power potential is painful. You jump between the climate modeling platform for general weather data; then you log into the asset management system to get the registered site ID; finally, you open an energy spreadsheet and manually input assumed tilt angles. It's slow, prone to copy-paste errors, and always requires manual validation against multiple dashboards.

With this MCP server, your agent handles the whole flow. You just ask it: 'What is the predicted output for my 5kW array?' The system runs `get_solar_summary` or `get_detailed_pv_forecast`, pulls in the weather context (`get_weather_forecasts`), and returns a single, validated number that accounts for everything.

Solcast Solar MCP Server: Get accurate power predictions.

Before this server, getting performance data required manually comparing the forecast model's output against the site inventory record. If you missed a single parameter—like whether the measurement was 'estimated' or 'measured'—the numbers were useless for auditing.

Now, your agent handles that nuance. You can call `get_site_estimated_actuals` versus `get_site_measured_actuals`. It instantly tells you if the number is a projection or hard data from the site’s telemetry feed. That difference matters.

Common Questions About Solcast Solar MCP

What parameters do I need to get a rooftop PV forecast? +

At minimum, you need: latitude, longitude, and system capacity (kW). For more accurate forecasts, also provide tilt (panel angle 0-90°), azimuth (panel direction 0°=north, 180°=south), and loss_factor (system efficiency 0-1, default ~0.9). If you don't know tilt/azimuth, Solcast will auto-estimate reasonable defaults based on your location.

How far ahead can Solcast forecast solar power? +

Solcast provides forecasts from the present time up to 14 days ahead (336 hours). Short-term forecasts (next 24-48 hours) are the most accurate, with accuracy gradually decreasing for longer horizons. Forecast data is available in 5-minute, 10-minute, 15-minute, 30-minute, or 60-minute intervals depending on your plan tier.

How do I get a Solcast API key and what does the free tier include? +

Visit https://solcast.com/ and sign up for a free Developer API account. The free tier includes rooftop PV power forecasts with limited daily API calls. For production use with higher call volumes, historical data access, and advanced features, upgrade to Pro or Enterprise plans. Register at https://solcast.com/ to get your API key instantly.

What is the difference between GHI, DNI, and DHI? +

GHI (Global Horizontal Irradiance) is the total solar radiation received on a horizontal surface. DNI (Direct Normal Irradiance) is the direct beam radiation received on a surface perpendicular to the sun. DHI (Diffuse Horizontal Irradiance) is the scattered radiation from the sky (not direct sunlight). GHI = DNI × cos(zenith angle) + DHI. For flat panels, GHI is most relevant. For tracking systems, DNI matters more. Cloudy conditions increase DHI proportion.

What is the difference between `get_site_measured_actuals` and estimated production? +

Use get_site_measured_actuals when you need the exact physical output. This tool requires a site with real telemetry integration, giving you actual measured data instead of an estimate based on models.

How do I get a complete solar resource overview using `get_solar_summary`? +

This tool combines irradiance forecasts (GHI/DNI/DHI), weather predictions, and PV output estimates into one call. It’s the best way to perform a full solar resource assessment for any location.

What's the difference between `get_simple_pv_forecast` and `get_detailed_pv_forecast`? +

The simple forecast gives you a quick estimate using only latitude, longitude, and capacity. Use get_detailed_pv_forecast when you know specific system parameters like tilt, azimuth, or loss factor for higher accuracy.

What are the requirements for running `get_historical_radiation`? +

You need a Pro or Enterprise plan to access full historical data. When calling this tool, ensure that your start and end dates are provided in ISO 8601 format.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 11 tools

We've already built the connector for Solcast Solar. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.