PT5 MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PT5 MCP Server Parse the data from battery_test.pt5 and show summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PT5 MCP Server
MCP (Model Context Protocol) server for parsing Monsoon Power Monitor PT5 files.
Enables any MCP-compatible client (WorkBuddy, Claude Desktop, Cursor, etc.) to read, analyze, and export power measurement data from .pt5 files captured by Monsoon Solutions' Power Tool software.
Features
parse_pt5 — Parse a PT5 file and return summary statistics (avg/min/max current, voltage, power, energy)
get_pt5_channels — List available measurement channels and field types from the captureDataMask
get_pt5_samples — Retrieve sample data with time-range filtering and decimation
export_pt5_csv — Export sample data to CSV file for external analysis
get_pt5_header — Return raw header and status packet metadata (hardware info, calibration, scaling)
analyze_pt5_trend — Analyze current trend: peak detection, periodicity (autocorrelation), trend segments, anomalies
Related MCP server: eplusout-mcp
Quick Start
Use with npx (no install needed)
Add to your MCP client configuration (e.g., ~/.workbuddy/mcp.json or Claude Desktop claude_desktop_config.json):
{
"mcpServers": {
"pt5": {
"command": "npx",
"args": ["pt5-mcp-server"]
}
}
}Install globally
npm install -g pt5-mcp-serverThen configure:
{
"mcpServers": {
"pt5": {
"command": "pt5-mcp-server"
}
}
}Local development
git clone https://github.com/YOUR_USERNAME/pt5-mcp-server.git
cd pt5-mcp-server
npm install
npm run buildConfigure with local path:
{
"mcpServers": {
"pt5": {
"command": "node",
"args": ["/path/to/pt5-mcp-server/build/index.js"]
}
}
}PT5 File Format
PT5 is the native binary format of Monsoon Solutions' Power Tool software. The file structure is:
Section | Offset | Description |
Header | 0 | 212-byte fixed header with capture metadata |
Status Packet | 272 | Variable-length hardware status (calibration, scaling) |
Sample Data | 1024 | Sequential current/voltage samples at 5 kHz |
Each sample contains:
Main Current (signed Int32, µA) — if channel enabled
USB Current (signed Int32, µA) — if channel enabled
Aux Current (signed Int32, µA) — if channel enabled
Voltage (unsigned UInt16, with marker bits) — always present
Voltage tick resolution depends on hardware revision:
Hardware | Main | USB | Aux |
Rev A | 62.5 µV/tick | 62.5 µV/tick | 62.5 µV/tick |
Rev B | 125 µV/tick | 125 µV/tick | 62.5 µV/tick |
Rev C | 125 µV/tick | 125 µV/tick | 125 µV/tick |
HVPM | 500 µV/tick | 125 µV/tick | 500 µV/tick |
Tools Reference
parse_pt5
Parse a PT5 file and return summary statistics.
Parameters:
file_path(string, required): Absolute path to the .pt5 file
Returns: JSON with sample count, duration, avg/min/max current (mA), avg voltage (V), avg power (mW), total energy (mJ).
get_pt5_channels
List available measurement channels and fields.
Parameters:
file_path(string, required): Absolute path to the .pt5 file
Returns: Channels (Main/USB/Aux), fields (Min/Avg/Max Voltage/Current/Power), sample rate, hardware info.
get_pt5_samples
Retrieve sample data with filtering options.
Parameters:
file_path(string, required): Absolute path to the .pt5 filestart_time_sec(number, optional): Start time in seconds (default: 0)end_time_sec(number, optional): End time in seconds (default: end of capture)decimation(number, optional): Return every Nth sample (default: 1)max_samples(number, optional): Max samples to return (default: 5000)
Returns: Array of sample objects with timestamp, current (mA), and voltage (V).
export_pt5_csv
Export sample data to a CSV file.
Parameters:
input_path(string, required): Absolute path to the input .pt5 fileoutput_path(string, required): Absolute path for the output .csv file
Returns: Confirmation with file size and sample count.
get_pt5_header
Return raw header and status packet metadata.
Parameters:
file_path(string, required): Absolute path to the .pt5 file
Returns: Full header and status packet data, including voltage tick sizes per channel.
analyze_pt5_trend
Analyze current trend in a PT5 file: detect periodic peaks, autocorrelation-based periodicity, trend direction, and anomalies.
Parameters:
file_path(string, required): Absolute path to the .pt5 filechannel(enum: "main" | "usb" | "aux", optional): Channel to analyze (default: "main")peak_window_ms(number, optional): Peak detection window in ms (default: 50)min_peak_prominence_ma(number, optional): Minimum peak prominence in mA (default: auto — 5% of mean current)anomaly_threshold_std(number, optional): Anomaly detection threshold in standard deviations (default: 3)max_lag_sec(number, optional): Maximum lag for autocorrelation in seconds (default: 10)
Returns:
Basic stats: mean, std, CV, min, max current
Peak analysis: total peaks, top peaks with time/current/prominence, average peak interval
Periodicity: dominant period/frequency from autocorrelation, confidence score (0–1)
Trend: overall direction (rising/falling/stable), slope, segment breakdown
Anomalies: intervals where current deviates >N standard deviations from mean
Histogram: current distribution bins
Example output:
=== Trend Analysis: air-mode.pt5 (channel: main) ===
Mean current: 131.854 mA, Std: 82.512 mA, CV: 0.6259
--- Peak Analysis ---
Total peaks detected: 4244
Average peak interval: 0.0531s (std: 0.0073s)
Top peaks: t=4.610s I=3783.4mA, t=4.709s I=2527.3mA ...
--- Periodicity (Autocorrelation) ---
Dominant period: 0.052s (19.2308Hz)
Confidence: 57.3%
--- Overall Trend ---
Trend: stable (slope: -0.0172 mA/s)
Segments: 80 rising, 60 falling, 84 stable (224 total)
--- Anomalies ---
Found 35 anomaly intervalsLicense
MIT
Available Tools
6 toolsanalyze_pt5_trendA
Analyze current trend in a PT5 file: detect peaks, periodicity (autocorrelation), trend segments, and anomalies. Useful for identifying periodic power consumption patterns, current spikes, and abnormal power behavior.
Inputs: file_path (required), channel, peak_window_ms, min_peak_prominence_ma, +2 more.
export_pt5_csvB
Export PT5 sample data to a CSV file. Includes timestamps, current (mA), voltage (V), markers, and missing data flags.
Inputs: input_path (required), output_path (required).
get_pt5_channelsA
List the available measurement channels (Main, USB, Aux) in a PT5 file based on its captureDataMask, plus hardware info and sample rate.
Inputs: file_path (required).
get_pt5_headerA
Return the raw header and status packet metadata from a PT5 file, including hardware info, calibration data, trigger settings, and scaling factors.
Inputs: file_path (required).
get_pt5_samplesA
Retrieve sample data from a PT5 file, with optional time range filtering and sample decimation. Returns current (mA) and voltage (V) values.
Inputs: file_path (required), start_time_sec, end_time_sec, decimation, +1 more.
parse_pt5A
Parse a Monsoon Power Monitor PT5 file and return a summary of the captured power data, including sample count, duration, average/min/max current, voltage, and power.
Inputs: file_path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: analyzing trends, exporting, listing channels, getting header, getting samples, and parsing summary. No overlap, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_pt5_noun pattern (e.g., analyze_pt5_trend, get_pt5_channels). This predictable structure aids agent selection.
With 6 tools, the server is well-scoped for a file format utility. Each tool serves a necessary function without redundancy or unnecessary complexity.
The set covers all essential operations for PT5 files: reading raw data and metadata, parsing summaries, analyzing trends, listing channels, and exporting. No obvious gaps for common use cases.
Related MCP Connectors
Read, analyze, and safely edit Microsoft Project MPP files.
Patents MCP — wraps the USPTO Open Data Portal (ODP) Patent File Wrapper API
Normalize bank statements (CSV, camt, MT940, OFX, QIF) to JSON, analyze, export.
Normalize bank statements (CSV, camt, MT940, OFX, QIF) to JSON, analyze, export.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to access, analyze, and extract information from STDF-V4 semiconductor test data files, supporting metadata extraction, parametric analysis, yield calculations, and multi-site test data filtering with CSV/Excel export capabilities.2MIT
- FlicenseBqualityDmaintenanceProvides comprehensive access to EnergyPlus building energy simulation results, enabling discovery, analysis, and extraction of data from epJSON, SQL, and HTML files through MCP tools with pandas integration.191-
- FlicenseNot gradedqualityDmaintenanceExposes tools to query and analyze energy monitoring sessions stored in CSV files, enabling users to get consumption stats, compare sessions, and view historical data through natural language in Claude Desktop.-
- 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.-