solar-data-mcp-forecast
MCP server wrapping the open Quartz Solar Forecast model (Open Climate Fix) — the forecast domain of solar-data-mcp. No API key needed.
| Tool | Answers |
|---|---|
forecast_generation |
"What will my array generate tomorrow?" (hourly, ≤48 h) |
compare_forecast_to_model |
"Is today unusually sunny?" (forecast vs PVWatts typical-year) |
Run standalone: uvx --from solar-data-mcp-forecast solar-forecast-mcp — but see the
model-install note below; most users want the combined
solar-data-mcp
server, which adds the other three domains plus the skill and report layer.
Installing the model
quartz-solar-forecast pins pydantic==2.6.2, which conflicts with the MCP SDK,
so it is not a declared dependency. Install it alongside (it runs fine on newer
pydantic; the pin is conservative). Python 3.11 is required —
pv-site-prediction does not support 3.12+:
$ uv venv --python 3.11 --seed .venv && source .venv/bin/activate
$ pip install solar-data-mcp-forecast
$ pip install --no-deps quartz-solar-forecast
$ pip install pv-site-prediction xarray xgboost openmeteo-requests requests-cache retry-requests huggingface_hub async_timeout
On macOS, xgboost also needs the OpenMP runtime: brew install libomp.
Without the model installed, the server still starts and its tools return an error containing these instructions.
Model note: Quartz is trained on sites ≤ 4 kWp; larger arrays are modeled at 4 kWp and linearly scaled (the library prints a notice when it does this).
Using forecasts with the combined solar-data-mcp server
An ephemeral uvx environment cannot hold the side-install above. Use a
persistent venv and point your agent at its entry point:
$ uv venv --python 3.11 --seed ~/.venvs/solar-data-mcp
$ ~/.venvs/solar-data-mcp/bin/pip install solar-data-mcp
$ ~/.venvs/solar-data-mcp/bin/pip install --no-deps quartz-solar-forecast
$ ~/.venvs/solar-data-mcp/bin/pip install pv-site-prediction xarray xgboost openmeteo-requests requests-cache retry-requests huggingface_hub async_timeout
Then in the agent config, replace "command": "uvx", "args": ["solar-data-mcp"]
with "command": "~/.venvs/solar-data-mcp/bin/solar-data-mcp".
1 maintainer
Metadata
1 maintainer
Release files for solar-data-mcp-forecast 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| solar_data_mcp_forecast-0.1.1.tar.gz | 10.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| solar_data_mcp_forecast-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.8 kB
Release files / solar_data_mcp_forecast-0.1.1.tar.gz
| Download URL | solar_data_mcp_forecast-0.1.1.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48cab722b8c02ceba4c6f5306a682c74017930e8ef94972ce955eac05b2e3dc7
|
|
BLAKE2b-256 checksum How to use checksums |
9683c213437720349d9051c38bb523743b831352b518e78dd5fef999dbf23a0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 6, 2026.
Transparency logRelease files / solar_data_mcp_forecast-0.1.1-py3-none-any.whl
| Download URL | solar_data_mcp_forecast-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2453542d5813d866270cb129e1f757f6058739fefe9d74e82a51806537624856
|
|
BLAKE2b-256 checksum How to use checksums |
ac416a81817dba34b526684e0220f19c9f7dd16183b8e2c57e2d504312a9c83b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 6, 2026.
Transparency logSecurity for solar-data-mcp-forecast 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for solar_data_mcp_forecast-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
