Skip to main content
Glama
AetherLink SDR MCP

AetherLink SDR MCP

by N-Erickson

Related Servers

Alternatives to AetherLink SDR MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Conversational AI control for Software Defined Radio via the Model Context Protocol.
      9
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to control an RTL-SDR receiver through MCP tools: sweep spectrum, inspect waterfall and spectrogram images, demodulate and transcribe audio, monitor intermittent signals, and decode ISM devices.
      7
      6
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to operate a Fishball7020/PlutoSky software-defined radio, including tuning, spectrum analysis, band scanning, IQ capture, FPGA filtering, and optional transmission.
      16
      4
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to process RF signals, perform spectral analysis, and execute radar DSP primitives such as Range-Doppler processing and CFAR detection, supporting both file-based and live SDR capture.
      14
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language control of a live GNU Radio SDR flowgraph, allowing users to tune frequencies, adjust gain, capture IQ samples, analyze spectra, and detect signals through an MCP-compatible client.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables natural language-driven creation and management of GNU Radio flowgraphs with validated block connections and parameter configurations. It provides tools for searching the GNU Radio block library, detecting SDR hardware, and generating functional signal processing code.
      8
      MIT

    TDQS

    B3.4/5.0

    Scored across 34 tools

    Disambiguation4/5

    Tools are cleanly separated by domain prefix (sdr_, aviation_, pager_, marine_, satellite_, ism_, spectrum_, recording_, audio_record_), and the recurring start/stop/get triads make intent obvious. The only mild overlaps are spectrum_scan vs ism_start_scanning (mitigated by rtl_433-specific wording) and recording_start (IQ) vs audio_record_start (WAV), which descriptions do clarify.

    Naming Consistency4/5

    Strong, predictable domain-prefix + verb_noun pattern (sdr_set_frequency, aviation_track_aircraft, pager_get_messages, ism_stop_scanning) applied across nearly all 34 tools. Deviations are few: signal_generator (noun phrase, no prefix) and hackrf_set_tx_gain (device prefix instead of sdr_), plus the slightly longer audio_record_start/stop.

    Tool Count2/5

    34 tools is heavy for a single MCP server and exceeds a comfortable surface; the per-decoder start/stop/get triads multiply quickly. Each group is individually justified by the domain, but marginal entries like signal_generator and hackrf_set_tx_gain could be folded into general SDR controls.

    Completeness4/5

    Core lifecycle is well covered: device discovery, connect/disconnect, frequency, sample rate, gain, ppm, bias tee, status, plus spectrum, recording, audio, TX and four decoder families with prediction support. Minor gaps exist around demodulation mode/bandwidth/squelch settings (audio recording implies a demod choice that cannot be set) and no recording file management or listing.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data