Physbound MCP Server

Add PhysBound to any MCP-compatible client. For example, in Claude Desktop (`claude_desktop_config.json`), Cursor, or Windsurf:

Local serverstdioPython

What is the Physbound MCP server?

If you already use Physbound, the physbound mcp server is the piece that lets your assistant work with it directly. Add PhysBound to any MCP-compatible client. For example, in Claude Desktop (claude_desktop_config.json), Cursor, or Windsurf:.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • rf_link_budget — Computes a full RF link budget using the Friis transmission equation. Validates antenna gains against aperture limits
  • shannon_hartley — Computes Shannon-Hartley channel capacity C = B * log2(1 + SNR) and validates throughput claims
  • noise_floor — Computes thermal noise power N = k_B * T * B, cascades noise figures through multi-stage receivers using the Friis noise formula, and calculates
  • radar_range — Computes the monostatic radar range equation R_max = [P_t G^2 lambda^2 sigma / ((4pi)^3 S_min L)]^(1/4) and validates detection range claims

Installation

physbound on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Physbound's toolset — rf_link_budget, shannon_hartley, noise_floor and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jonesrobm; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
rf_link_budgetComputes a full RF link budget using the Friis transmission equation. Validates antenna gains against aperture limits.
shannon_hartleyComputes Shannon-Hartley channel capacity C = B * log2(1 + SNR) and validates throughput claims.
noise_floorComputes thermal noise power N = k_B * T * B, cascades noise figures through multi-stage receivers using the Friis noise formula, and calculates receiver sensitivity.
radar_rangeComputes the monostatic radar range equation R_max = [P_t G^2 lambda^2 sigma / ((4pi)^3 S_min L)]^(1/4) and validates detection range claims.

How to install the Physbound MCP server

{
  "mcpServers": {
    "physbound": {
      "command": "uvx",
      "args": ["physbound"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Physbound to rf link budget.
  • Use Physbound to shannon hartley.
  • Use Physbound to noise floor.

Frequently asked questions

It connects Physbound to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (rf_link_budget, shannon_hartley, noise_floor, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Physbound directly.