get_calculator_info
Get detailed information about a specific calculator including its inputs, outputs, and formula. Use this to understand what parameters a calculator needs before running it.
LABSCO SUMMARY
Engineering formulas that run as code, not as a model's recollection of them.
The argument for it is narrow and sound: an LLM asked for a microstrip width will confidently drop the copper-thickness correction, whereas run_calculation executes Hammerstad-Jensen and returns the number with its units. The free half needs no account at all — only the server-side simulations are metered.
What it is
An MCP server for rftools.io. The calculators are bundled as local functions — microstrip impedance, link budgets, filter design, converter sizing, antenna patterns — so an assistant calls the same validated code that runs on the site instead of doing the arithmetic itself. Heavier work is submitted to rftools.io as a simulation job.
What you get
- list_calculators — the available calculators, optionally filtered to rf, pcb, power, signal, antenna, general, motor, protocol, emc, thermal, sensor, unit-conversion or audio
- get_calculator_info — a calculator's inputs with units and defaults, its outputs, and the formula it uses
- run_calculation — run one by slug with your inputs; it executes locally, so it is instant and consumes no quota
- list_simulation_tools — the server-side jobs and their jobType identifiers, from NEC2 antenna simulation and FDTD S-parameters to SMPS loop stability and radiated-emission estimates
- run_simulation — submit a job and wait for the result; typically 15–120 seconds, plus queue time
Requirements
Nothing for the calculators — clients launch it with npx -y rftools-mcp over stdio and all 232 run locally with no sign-up. The simulation tools need RFTOOLS_API_KEY from an rftools.io dashboard; free accounts get 5 simulation runs a month, Pro 100, and the API tier 10,000.
Setup effort
One command — npx -y rftools-mcp
USE CASES
01
Sizing a trace for a target impedance
Find the microstrip calculator, check which inputs it wants, and run it against your stack-up.
02
Checking whether a radio link will close
Run the link budget for the frequency, distance and antenna gains and read the margin.
03
Simulating an antenna before building it
Look up the job type for wire-antenna simulation and submit the geometry.
04
Testing a filter against component tolerances
Submit a Monte Carlo tolerance run and read the spread it comes back with.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_calculators
List available RF & electronics calculators. Optionally filter by category: rf, pcb, power, signal, antenna, general, motor, protocol, emc, thermal, sensor, unit-conversion, audio.
list_simulation_tools
List the 14 server-side RF simulation tools available via API key. These require RFTOOLS_API_KEY (set in env). Free tier: 5 runs/month. Pro: 100/month. API tier: 10 000/month.
run_calculation
Run an RF/electronics calculator with the given inputs. Use get_calculator_info first to see required inputs.
run_simulation
Submit a server-side RF simulation job and wait for the result. Requires RFTOOLS_API_KEY environment variable. Simulations typically complete in 15–120 seconds; queue wait may add more time. Use list_simulation_tools to see available jobTypes and required params.
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. The 232 calculators and 13 simulations are catalogue entries passed to run_calculation and run_simulation, not tools. list_simulation_tools and run_simulation need an API key; omit the env block for calculators only.
Requires
npx on PATH
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y rftools-mcpMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"rftools": {
"command": "npx",
"args": [
"-y",
"rftools-mcp"
],
"env": {
"RFTOOLS_API_KEY": "<YOUR_RFTOOLS_API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add rftools-mcp -e RFTOOLS_API_KEY=<YOUR_RFTOOLS_API_KEY> -- npx -y rftools-mcp
