PPK2 MCP Server
Related Servers
Alternatives to PPK2 MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants to power and measure devices using a Qoitech Otii Arc or Otii Ace, recording current and optional UART logs. It calculates energy, charge, and current statistics for entire recordings, selected time ranges, or intervals between firmware log messages.9MIT- AlicenseNot gradedqualityDmaintenanceMCP server for Nordic Semiconductor's Power Profiler Kit II (PPK2), enabling current measurement and device control via 12 tools from Claude.1MIT
- FlicenseAqualityDmaintenanceEnables MCP clients to control a Nordic PPK2 for power profiling: configure source/measurement modes, set voltage, power DUT, measure current/power/energy, and capture logic channels.6-
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to list, inspect, probe, capture, and analyze current measurements from the Nordic Power Profiler Kit II, returning aggregates and file paths rather than raw samples.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to automatically discover and control supported laboratory instruments over USB, LAN, and serial connections, including power-supply output, setpoint, and protection management plus multimeter measurements.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to capture, measure, and decode USB logic-analyzer signals, including 16-channel streaming and sigrok protocol decoding for UART, I2C, SPI, CAN, and other protocols.MIT
TDQS
Scored across 19 tools
Each tool targets a distinct action or resource: discovery vs. connection, device configuration setters, capture lifecycle, and post-capture analysis. The only adjacent pair is capture vs. start/stop_capture, but the blocking <=60s vs. background long-capture distinction is explicit, so misselection is unlikely.
Names are uniformly snake_case and almost all follow verb_noun or verb_object patterns (list_captures, set_mode, get_capture_status). Minor deviations like connect, disconnect, capture, and raw_command are conventional and readable rather than inconsistent.
19 tools is on the higher side but reasonable for a full-featured PPK2 client spanning device discovery, configuration, capture, analysis, and logic channels. No obvious redundant tool exists, though the capture lifecycle could be seen as slightly expansive.
The surface covers the core lifecycle: discover, connect, configure, capture (short and long), monitor, stop, analyze, segment, estimate battery, and read logic channels. Minor gaps like deleting/exporting captures, explicit sample-rate control, or calibration writes are mostly addressable via raw_command.