xhelio-cdaweb
NASA CDAWeb data access for heliophysics — browse observatories, inspect parameters, fetch CDF data.
README
xhelio-cdaweb
NASA CDAWeb data access for heliophysics — browse observatories, inspect parameters, fetch CDF data.
Works as a standalone Python library or as an MCP server for any MCP-compatible LLM client (Claude Desktop, Cursor, custom agents).
What's included
- 65 observatory catalogs with 2900+ datasets — ACE, Parker Solar Probe, Solar Orbiter, Wind, MMS, THEMIS, GOES, Voyager, and more
- 2880 pre-built parameter metadata files from Master CDF skeletons —
browse_parametersworks instantly, no network required - Automatic data validation — fetched CDF files are compared against Master CDF metadata to detect phantom (documented but missing) and undocumented (present but undocumented) parameters
- Structured system prompts per observatory — give an LLM full context about available instruments, datasets, and time coverage
Observatory catalogs are built directly from the CDAWeb REST API observatory groups — no hand-curated mappings.
Installation
# Library only
pip install xhelio-cdaweb
# With MCP server
pip install xhelio-cdaweb[mcp]
MCP Server
Configuration (Claude Desktop, Cursor, etc.)
{
"mcpServers": {
"cdaweb": {
"command": "xhelio-cdaweb-mcp"
}
}
}
With custom cache directory:
{
"mcpServers": {
"cdaweb": {
"command": "xhelio-cdaweb-mcp",
"args": ["--cache-dir", "/path/to/cache"]
}
}
}
Or run directly:
xhelio-cdaweb-mcp
xhelio-cdaweb-mcp --cache-dir /path/to/cache
python -m cdawebmcp
Cache directory
All runtime data is stored under a single root directory. Defaults to ~/.cdawebmcp/.
On first use, bundled data (observatory catalogs and parameter metadata) is copied into the cache directory. This ensures all reads and writes happen in one writable location, even for non-editable installs from PyPI.
Configure via --cache-dir (MCP server), the XHELIO_CDAWEB_CACHE_DIR environment variable, or cdawebmcp.configure() (library):
XHELIO_CDAWEB_CACHE_DIR=/path/to/cache xhelio-cdaweb-mcp
import cdawebmcp
cdawebmcp.configure(cache_dir="/path/to/cache")
~/.cdawebmcp/ # or custom path via configure()
├── observatories/ # Observatory catalog JSONs (bootstrapped from package)
├── metadata/ # Parameter metadata JSONs (bootstrapped from package)
├── cdf_cache/ # Downloaded CDF data files (permanent, reused across fetches)
│ └── ace/mfi/ # organized by observatory/instrument path
│ └── ac_h2_mfi_2024.cdf
└── overrides/ # Validation sync results (append-only)
└── ace/
└── AC_H2_MFI.json
observatories/— Observatory catalog JSONs. Bootstrapped from bundled package data on first use.metadata/— Parameter metadata JSONs. Bootstrapped from bundled package data on first use. New metadata is fetched on demand from Master CDFs.cdf_cache/— Permanent cache of downloaded CDF files. Once a CDF file is downloaded, it is never re-downloaded. Usemanage_cache(action="clean", category="cdf_cache")to free disk space.overrides/— Validation results from comparing fetched data against metadata. Append-only, one JSON per dataset.
Tools
| Tool | Description |
|---|---|
browse_observatories() |
List all 65 CDAWeb observatories with descriptions, dataset counts, and instruments |
load_observatory(observatory_id) |
Get the complete system prompt for an observatory (role instructions + full dataset catalog) |
browse_parameters(dataset_id) |
Browse all variables in a dataset — name, type, units, description, plus validation status if available |
fetch_data(dataset_id, parameters, start, stop, output_dir) |
Download CDF data, write to file, return metadata + per-column stats (min, max, mean, std, nan_ratio) |
manage_cache(action, ...) |
Cache management — status, clean, refresh metadata, refresh time ranges, rebuild catalog |
Typical workflow
browse_observatories → load_observatory("ace") → browse_parameters("AC_H2_MFI") → fetch_data(...)
- Discover available observatories
- Load an observatory's full catalog and instructions
- Inspect dataset parameters to choose what to fetch
- Fetch data for a time range — returns file path + statistics
Python Library
from cdawebmcp.catalog import browse_observatories
from cdawebmcp.prompts import build_observatory_prompt
from cdawebmcp.metadata import browse_parameters
from cdawebmcp.fetch import fetch_data
# List all 65 observatories
observatories = browse_observatories()
# Get observatory-specific system prompt
prompt = build_observatory_prompt("ace")
# Browse dataset parameters (instant — uses bundled metadata)
params = browse_parameters(dataset_id="AC_H2_MFI")
# Fetch data — returns DataFrames directly
result = fetch_data("AC_H2_MFI", ["Magnitude"], "2024-01-01", "2024-01-02")
mag = result["Magnitude"]
print(mag["data"]) # pandas DataFrame
print(mag["units"]) # "nT"
print(mag["stats"]) # per-column {min, max, mean, std, nan_ratio}
Data validation
When fetch_data downloads CDF files, it automatically compares actual data variables against the bundled Master CDF metadata. Discrepancies are recorded in ~/.cdawebmcp/overrides/ and surfaced through browse_parameters:
- Phantom parameters — listed in metadata but absent from actual data files
- Undocumented parameters — present in data files but not in official metadata
This validation runs once per unique CDF source URL and builds an append-only archive with full provenance (source file, URL, timestamp).
Bundled data
| Data | Count | Description |
|---|---|---|
| Observatory catalogs | 65 | Instruments, datasets, time coverage, PI info |
| Parameter metadata | 2880 | Variable names, types, units, fill values, sizes |
| Prompt templates | 2 | Generic role + CDAWeb-specific workflow instructions |
All bundled data ships with the package and is copied to the cache directory on first use. No network access needed for browsing — only fetch_data requires a connection to CDAWeb.
Catalog updates
Rebuild from CDAWeb REST API:
# Rebuild observatory catalogs (uses CDAWeb observatory groups API)
python -m cdawebmcp.scripts.build_catalog
python -m cdawebmcp.scripts.build_catalog --observatory ace
python -m cdawebmcp.scripts.build_catalog --list
# Rebuild parameter metadata from Master CDFs
python -m cdawebmcp.scripts.build_metadata
python -m cdawebmcp.scripts.build_metadata --observatory psp
Development
pip install -e ".[dev]"
pytest tests/ -v
For a CI-safe MCP check that does not fetch CDAWeb data, run:
uv run --extra mcp python scripts/smoke_mcp_list_tools.py --json
The smoke starts the stdio server with an isolated temporary cache, runs MCP
initialize + list_tools, and verifies the advertised tool names.
MCP registry manifest
This repository includes server.json for MCP registry publishing. Keep its version in sync with pyproject.toml and src/cdawebmcp/__init__.py.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。