MCP Overview¶
RFlect ships a Model Context Protocol server so an AI agent (Claude Code, Cline, Continue, etc.) can drive RFlect programmatically — no GUI required.
RFlect has no LLM of its own
As of v5.0.0 RFlect makes no outbound LLM/API calls and needs no API key or subscription. It is a deterministic RF analysis + rendering toolkit. The driving MCP agent is the LLM: it calls RFlect's tools for data, and — if you want narrative prose in a report — authors it itself and passes it to generate_report via the narrative parameter.
What you can do over MCP¶
- Import passive HPOL/VPOL pairs, active TRP files, S-parameter sweeps
- Run analysis: HPBW, F/B ratio, gain stats, polarization, UWB SFF, impedance bandwidth, S11/VSWR, group delay
- Compare antennas head-to-head; estimate link budget / range; compute MIMO diversity
- Generate branded DOCX reports (deterministic prose by default, or agent-authored)
- Generate active chamber calibration files and track calibration drift across time
- Run a standard procedure on a folder with a single call via
process_folder— auto-detects intent, runs the right workflow, optionally generates a report
Tool count¶
41 tools across 9 categories. See Tools Reference for the full list with signatures.
| Category | Count |
|---|---|
| Import | 6 |
| Analysis | 5 |
| Reports | 3 |
| Bulk | 5 |
| UWB | 3 |
| Cal Drift | 8 |
| Orchestration | 1 |
| Validation | 1 |
| Analysis (RF) | 6 |
| Misc | 3 |
Why an orchestrator?¶
Before v4.2.0, an MCP client wanting to "process this folder and give me a report" had to:
list_measurement_files(folder)to see what's inside- Decide passive vs active based on filenames
bulk_process_passive(folder, freqs)orbulk_process_active(folder)import_passive_pair(...)orimport_active_processed(...)for each onegenerate_report(path, options)
That's a five-step chain that every agent had to script. process_folder collapses all of it into one call:
See Recipes for the full set of standard procedures.
Where to next¶
- Installation — wire RFlect into Claude Code / Cline / generic clients
- Tools Reference — every tool, signature, return shape
- Recipes — standard procedures for common workflows
- Troubleshooting — what to do when it doesn't connect