solar-mcp
MCP server for space weather and HF propagation conditions — live solar flux, Kp index, DSCOVR solar wind, X-ray flux, alerts, 27-day forecast, and band-by-band outlook through any MCP-compatible AI assistant.
Part of the qso-graph project. No authentication required — all data from NOAA SWPC public endpoints.
Install
pip install solar-mcp
Tools
| Tool | Description |
|---|---|
solar_conditions |
Current SFI, Kp, and NOAA R/S/G space weather scales |
solar_forecast |
27-day SFI and Kp forecast from NOAA |
solar_alerts |
Active space weather alerts and warnings |
solar_wind |
Real-time DSCOVR L1 solar wind (Bz, speed, density) |
solar_xray |
GOES X-ray flux and solar flare classification |
solar_band_outlook |
HF band-by-band propagation assessment (160m-6m) |
get_version_info |
Service version + upstream spec version (fleet identity attestation) |
Quick Start
No credentials needed — just install and configure your MCP client.
Configure your MCP client
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"solar": {
"command": "solar-mcp"
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"solar": {
"command": "solar-mcp"
}
}
}
ChatGPT Desktop
{
"mcpServers": {
"solar": {
"command": "solar-mcp"
}
}
}
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"solar": {
"command": "solar-mcp"
}
}
}
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"solar": {
"command": "solar-mcp"
}
}
}
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"solar": {
"command": "solar-mcp"
}
}
}
Ask questions
"What are the current solar conditions?"
"Is the solar wind causing any geomagnetic disturbance?"
"What's the 27-day solar forecast look like?"
"Are any bands open right now on HF?"
"Are there any active space weather alerts?"
"What class solar flare is happening?"
Testing Without Network
SOLAR_MCP_MOCK=1 solar-mcp
MCP Inspector
solar-mcp --transport streamable-http --port 8008
Development
git clone https://github.com/qso-graph/solar-mcp.git
cd solar-mcp
pip install -e .
License
GPL-3.0-or-later
Metadata
Release files for solar-mcp 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| solar_mcp-0.2.4.tar.gz | 21.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| solar_mcp-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.1 kB
Release files / solar_mcp-0.2.4.tar.gz
| Download URL | solar_mcp-0.2.4.tar.gz |
|---|---|
| Size | 21.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c94301a4e2b20f3a5fbe7d127c2c88ab601b979eed4a6a1a8632e3832d43279b
|
|
BLAKE2b-256 checksum How to use checksums |
c328871f69fd96b3e1a6ed3889fa90152d76d67b931a287cd779e06a4b5f8cd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 28, 2026.
Transparency logRelease files / solar_mcp-0.2.4-py3-none-any.whl
| Download URL | solar_mcp-0.2.4-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6765978be3fbf9aadd7af5a65fa1bbf3aff1acd6198472f13208fccd7102d275
|
|
BLAKE2b-256 checksum How to use checksums |
320506b94f8746c25b7773dd54da89c587fe2632722a66f01c613a0927e281c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 28, 2026.
Transparency log