EMC Regulations MCP Server

EMC and RF regulatory lookup — emission limits, immunity levels, restricted bands, and certification matrices. Drive it from your IDE, terminal, or AI agent the moment a compliance question shows up.

Quick start · Tools · Workflows · Documentation

What is mcp-emc-regulations?

mcp-emc-regulations is an MCP server that answers concrete EMC and RF compliance questions — emission limits, immunity test levels, frequency allocations, restricted bands, certification requirements — directly from cited standards. No PDFs, no copy-paste from a regulatory site.

It implements lookups against curated datasets sourced from FCC Part 15/18/95, CISPR 11/12/14-1/22/25/32, IEC 61000-4-x, ISO 11452 / 7637 / 16750, 3GPP TS 36.101 / 38.101, ISED RSS-Gen, and EU harmonised standards. Live FCC text is fetched on demand from the official eCFR API.

What it does well:

• 🤖 AI-native via MCP. First-class Model Context Protocol server with 45 tools across FCC, CISPR, automotive, medical, cellular, wireless protocols, and certification advisory.

• 🐍 Multiple surfaces. Use it from any MCP client (Claude Desktop, Claude Code, Codex), or call the Python package directly.

• ⚡ Cited and dated. Every dataset carries source, version, and last_updated. The data_sources tool reports current versions; live eCFR queries are tagged with the eCFR snapshot date.

• ✅ Composable. Compare FCC vs CISPR at a frequency with distance correction. Generate full test plans (test_plan_generator, immunity_test_plan) across regions and standards in one call.

• 🔒 MIT licensed. Drop-in for compliance review workflows.

Quick start

Install

Pre-alpha: not yet on PyPI. Install from source:

git clone https://github.com/RFingAdam/mcp-emc-regulations.git
cd mcp-emc-regulations
uv pip install -e .

Two surfaces, same answer

Python

from mcp_emc_regulations.tools import fcc

# FCC Part 15.109 Class B radiated limit at 100 MHz
result = fcc.fcc_part15_limit(
    section="15.109",
    frequency_mhz=100,
    classification="B",
)
print(result)

CLI (via uv run)

uv run --directory /path/to/mcp-emc-regulations \
  mcp-emc-regulations
# JSON-RPC over stdio — drive it from any MCP client

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

Add to your claude_desktop_config.json:

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

Then ask your assistant in plain English:

"What's the FCC Part 15 Class B radiated limit at 100 MHz, and how does it compare to CISPR 32 Class B at the same frequency?"

The agent calls fcc_part15_limit and emc_compare_limits and reports both with distance corrections.

Tools

45 MCP tools, grouped by domain. Full reference in docs/tools.md.

Emission limits

Automotive

Medical / safety

Immunity (IEC 61000-4-x)

Cellular (3GPP)

Wireless protocols

Frequency bands

Certification advisory

Reference / sources

What it solves

Workflows

mcp-emc-regulations fits in the following eng-mcp-suite workflow bundles:

• emc-compliance — combine with mcp-pcb-emcopilot and drawio-engineering-mcp for the full layout-to-cert-letter loop.

• rf-design — verify wireless-protocol limits and restricted bands while sizing a transmit chain.

• automotive-emc — chain CISPR 25 / ISO 11452 lookups with test setup generation in drawio-engineering-mcp.

Part of eng-mcp-suite. Use in the emc-compliance workflow bundle.

See the suite manifest for the full list of sibling MCPs and bundle definitions.

Documentation

• 📘 Quick Start — install through first call.

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

• 📐 Usage examples — practical end-to-end walkthroughs.

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

Part of eng-mcp-suite

This MCP server is part of

An open umbrella for engineering MCP servers across RF, EMC, PCB, signal integrity, EM simulation, and lab test. Same brand, same docs structure, designed to compose. See the full catalog or jump to a sibling:

Data currency

• Curated datasets in src/mcp_emc_regulations/data/ carry metadata fields with source, version, and last_updated. Use the data_sources tool to see versions at runtime.

• ecfr_query pulls live CFR text from the eCFR API on each call.

• For compliance work, verify against the official standard before sign-off.

External sources can be configured in sources.json; use sources.local.json for private overrides. Run:

uv run python scripts/update_sources.py

to refresh data_sources/manifest.json.

Contributing

Contributions are welcome.

1. Pick a GitHub issue.

2. Fork + branch (feature/your-thing or fix/your-bug).

3. Run the local check suite:

   uv run pytest

4. Open a PR — link the issue, request review.

License

AGPL-3.0-or-later. Earlier commits had a stale "MIT" badge without a matching LICENSE file; v0.2.0 settles the repo on AGPL-3.0-or-later to align with the eng-mcp-suite toolkit-wide license move.

Acknowledgments

• eCFR — for the live regulatory text API.

• FCC / IEC / ISO / CISPR / 3GPP / ISED / ETSI — for the published standards this server indexes.

• 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.