mcp-rs-cmw500

Drive the Rohde & Schwarz CMW500 Wideband Radio Communication Tester from any MCP-compatible AI client. Direct TCP/IP SCPI (port 5025) — 84 tools across LTE signaling, WLAN, Bluetooth/BLE, and GPRF. No CMWrun dependency.

Quick start · Tools · Workflows · Documentation

What is mcp-rs-cmw500?

mcp-rs-cmw500 is a Model Context Protocol server that automates the R&S CMW500 Wideband Radio Communication Tester over direct TCP/IP SCPI (port 5025). No CMWrun dependency, no proprietary middleware — your AI agent talks to the CMW500 the same way a Python script would, only in natural language.

The server covers five RF technology domains: LTE signaling (cell config, NAS/bearer, C-DRX, full TX measurements), WLAN non-signaling (802.11a/b/g/n/ac/ax with 20/40/80/160 MHz channels), Bluetooth/BLE non-signaling (Classic DH1-DH5 + LE 1M/2M/Coded), GPRF generator/analyzer (CW/ARB output, power/spectrum measurements), and shared signal-path control.

What mcp-rs-cmw500 does well:

• 🤖 AI-native via MCP. First-class Model Context Protocol server with 84 tools across 5 RF technology domains. Any Claude / LLM agent can drive it.

• 🐍 Python + MCP surfaces. Import rs_cmw500_mcp for direct driver access, or run as an MCP server for AI-agent automation.

• ⚡ Direct SCPI. TCP/IP straight to the CMW500 — no CMWrun, no NI-VISA install, no vendor middleware.

• ✅ Pre-built templates. lte_tx_power, gprf_power, nonsig_rx, wlan_tx, wlan_rx, ble_tx, ble_rx, bt_classic_tx.

• 🔒 AGPL-3.0-or-later. Safety system (power / frequency clamps), SCPI-injection-guarded, raw-SCPI disable flag.

Related MCP server: 5G-MAG M1 Interface MCP Server

Quick start

Install

git clone https://github.com/RFingAdam/mcp-rs-cmw500.git
cd mcp-rs-cmw500
uv pip install -e ".[dev]"

Configure

cp .env.example .env   # edit with your CMW500 IP + safety limits

Two surfaces, same answer

Python

import asyncio
from rs_cmw500_mcp.driver import CMW500Driver
from rs_cmw500_mcp.models.cmw_types import CellConfig

async def main():
    async with CMW500Driver("192.168.1.100", 5025) as cmw:
        await cmw.lte_configure_cell(
            CellConfig(
                band=7,
                bandwidth_mhz=20,
                dl_earfcn=3100,
                dl_level_dbm=-70,
            )
        )
        await cmw.lte_cell_on()
        # ... wait for UE attach ...
        await cmw.lte_meas_configure(stat_count=10)
        await cmw.lte_meas_trigger()
        results = await cmw.lte_meas_fetch_all()
        # Each view is an envelope: check the verdict before the numbers.
        power = results["power"]
        if power["trustworthy"]:
            print(power["values"])
        else:
            print("no measurement:", power["error"])

asyncio.run(main())

MCP (Claude Desktop, Claude Code, any MCP client)

{
  "mcpServers": {
    "rs-cmw500": {
      "command": "uv",
      "args": [
        "--directory", "/path/to/mcp-rs-cmw500",
        "run", "rs-cmw500-mcp"
      ]
    }
  }
}

Then ask your assistant:

"Bring up a 20 MHz LTE cell on band 7 EARFCN 3100, wait for the UE to attach, then trigger TX power, EVM, ACLR, SEM, and frequency-error measurements."

The agent walks the LTE measurement workflow tool-by-tool and returns the result set.

Run

rs-cmw500-mcp        # MCP server over stdio

Try it without a CMW500

cmw-simulator --port 5125 --time-scale 0.01   # in one terminal
CMW_DEFAULT_PORT=5125 rs-cmw500-mcp           # in another

The simulator parses a real SCPI command tree, keeps a real error queue, and can inject the failures that matter — dropped responses, surplus responses, and specific reliability codes:

cmw-simulator --port 5125 --drop-responses 1   # exercise desync recovery

It binds loopback only unless you pass --allow-remote.

Tools

84 MCP tools, grouped:

Available templates: lte_tx_power, gprf_power, nonsig_rx, wlan_tx, wlan_rx, ble_tx, ble_rx, bt_classic_tx. Full tool reference in docs/tools.md.

What it solves

Safety

The server enforces configurable safety limits to protect your equipment:

• Generator power — bounded between CMW_MIN_GENERATOR_POWER_DBM and CMW_MAX_GENERATOR_POWER_DBM.

• Analyzer expected power — bounded by CMW_MAX_EXPECTED_POWER_DBM.

• Frequency range — bounded between CMW_MIN_FREQUENCY_HZ and CMW_MAX_FREQUENCY_HZ.

• SCPI sanitization — all parameters validated against injection patterns.

• Raw SCPI off by default — must explicitly set CMW_ALLOW_RAW_SCPI=true.

• Path traversal — state-file paths validated against directory traversal.

Workflows

mcp-rs-cmw500 fits in the following eng-mcp-suite workflow bundles:

• lab-automation — pair with copper-mountain-vna-mcp, mcp-rs-spectrum-analyzer, and mcp-rs-siggen for end-to-end RF bench-test workflows driven from a single agent session.

• cellular-compliance — drive 3GPP TS 36.521 LTE test cases under AI control with mcp-emc-regulations supplying market-specific limits.

eng-mcp-suite install --workflow lab-automation

Documentation

• 📘 Quick Start — install through first call.

• 🛠️ Tool reference — every MCP tool, every argument.

• 📐 Usage examples — an LTE TX measurement walkthrough.

• 🏗️ Architecture — how this MCP fits in eng-mcp-suite.

• 📝 Changelog

Part of eng-mcp-suite

This MCP server is part of

Part of eng-mcp-suite — an open umbrella of MCP servers for RF / EMC / PCB / signal-integrity engineering. Drop into the lab-automation workflow bundle with eng-mcp-suite install --workflow lab-automation.

Contributing

See CONTRIBUTING.md for development guidelines.

uv run pytest tests/ -q                # all unit tests (no hardware)
uv run pytest tests/ -m "not integration" -q
ruff check src/ tests/ && ruff format src/ tests/
mypy src/rs_cmw500_mcp/

License

AGPL-3.0-or-later. Relicensed from Apache-2.0 in v0.3.0 to align with the eng-mcp-suite toolkit-wide AGPL move.

Acknowledgments

• Rohde & Schwarz — for the published CMW500 SCPI command reference.

• The MCP working group — for the Model Context Protocol specification.

Part of eng-mcp-suite — built for RF engineers, PCB designers, EMC labs, and AI agents.