English Français العربية

io.github.qso-graph/eme-mcp

Official registry Other

EME prediction for amateur radio: moon windows, path loss and degradation, computed locally

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package eme-mcp
Claude Code 
claude mcp add eme-mcp -- uvx eme-mcp==0.4.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eme-mcp": {
            "command": "uvx",
            "args": [
                "eme-mcp==0.4.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. eme-mcp
  2. Why it needs nothing from the network
  3. Install
  4. Tools
  5. The two path-loss figures
  6. Licence

eme-mcp

MCP server for EME — Earth-Moon-Earth, moonbounce. When the moon is up from your grid, when it is up from both ends of a schedule at once, what the path costs on 2m, 70cm and 23cm, and which days ahead are least degraded.

Part of the qso-graph project. No network, no authentication.

Why it needs nothing from the network

The moon's position is computed here, from the abridged ELP-2000/82 series as Meeus tabulates it (Astronomical Algorithms, chapter 47). That is around 250 lines of standard library and a coefficient table. It is also what WSJT-X does, and the norm for EME software.

That matters for more than tidiness. Moonrise and moonset are different for every grid square, so a service-backed answer means a request per location per query — and a planning tool that stalls, rate-limits, or goes dark when a remote service does.

JPL Horizons is still here — as the test oracle. Recorded Horizons responses are fixtures, so every CI run checks these numbers against NASA's rather than against themselves. Measured against Horizons for a Boise grid:

agreement
Azimuthwithin 0.01°
Elevationwithin 0.003°
Rangewithin 9 km of ~392,000 (0.002%)

Thirty arcseconds, against a 432 MHz array that is degrees wide.

Install

uvx eme-mcp            # run it; nothing to install

Tools

ToolDescription
eme_moon_windowMoon azimuth, elevation and range from a grid square over time — and, given a second locator, the mutual window when both stations can see it
eme_path_lossOne-way, round-trip and echo path loss on 2m / 70cm / 23cm, or any frequency
eme_degradationHow much worse than perigee this moment is, with the moon's declination
eme_calendarThe least degraded days ahead
get_version_infoService version and the ephemeris series used
What this does not yet do

Sky noise is not included. The full degradation figure an EME operator plans with combines the distance term with the galactic background behind the moon, from the Haslam 408 MHz all-sky map. That map is not yet carried and pinned, so eme_degradation and eme_calendar report the distance term and say so in every answer rather than returning a number that looks complete and is not. Tracked in qso-graph-devel#52.

Elevations are geometric: no atmospheric refraction, which lifts an object near the horizon by about half a degree.

The two path-loss figures

They answer different questions and are often confused, so both are returned:

  • echo_db is the one to budget a station with — the radar equation, accounting for the moon reflecting about 6.5% of what reaches it. Near 252 dB on 2m, 262 on 70cm and 271 on 23cm at mean distance, which are the numbers EME operators know.
  • round_trip_db is twice the free-space loss. It ignores the moon entirely.

Licence

GPL-3.0-or-later. See LICENSE.

The algorithms are from Jean Meeus, Astronomical Algorithms (2nd edition, Willmann-Bell, 1998), chapters 7, 11, 12, 22, 40 and 47 — cited in the source where each is used. The implementation is ours; the mathematics is his and is not claimed.

Frequently asked questions

What is io.github.qso-graph/eme-mcp?

EME prediction for amateur radio: moon windows, path loss and degradation, computed locally

How do I install io.github.qso-graph/eme-mcp?

It runs on your machine. In Claude Code: claude mcp add eme-mcp -- uvx eme-mcp==0.4.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.qso-graph/eme-mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.qso-graph/eme-mcp open source?

Yes. Its code is on GitHub under the GPL-3.0 license.

Who maintains io.github.qso-graph/eme-mcp?

It is published by qso-graph. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.