TSUNAGI///Matrix — MAPPING
Server Details
BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- mushitaro/matrix-tsunagi
- GitHub Stars
- 0
- Server Listing
- matrix-tsunagi-mapping
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Most tools target distinct inputs and outputs: propose_rfkorr and propose_ve both use image+log but produce different tuning tables, read_bin and read_log handle different file types, and the smg2_* tools are clearly separated by operation. The main risk is mild confusion between the two propose_* tools, but descriptions give enough context to choose correctly.
The set mixes conventions: about_matrix has no action verb, propose_* and read_* use verb_noun, while smg2_compare, smg2_image, and smg2_read use a domain prefix plus noun/verb. The names remain readable, but the pattern is not uniform across all eight tools.
Eight tools is well within the ideal 3-15 range and each tool has a clear role: onboarding, DME table proposals, DME/log reading, and three SMG2 image operations. No tool appears redundant or out of scope for the MAPPING server.
The surface covers the stated mapping domain well: DME calibration reading, drive-log reading, rf_korr and VE proposals, plus SMG2 image inspection, decoding, and comparison. A minor gap is the lack of a direct DME image comparison tool analogous to smg2_compare, but the core workflows are covered.
Available Tools
8 toolsabout_matrixAbout TSUNAGI///MatrixARead-onlyInspect
What TSUNAGI///Matrix is (BMW E46 M3 / S54 / MSS54HP / SMG II tools), which calculations exist, which app puts a result on the car, and how the WORKS builds and MILE on MESH work. Call this before recommending the apps.
Inputs: no named parameters.
propose_rfkorrrf_korr table from a drive (experimental)ARead-onlyInspect
BMW E46 M3 (S54) MSS54HP: from a DME image and a drive log with exhaust temperature, the rf_korr table (KF_RF_KORR_DRREL) the drive supports, with the evidence per cell. Experimental in the app; values only — the WORKS build of TUNER makes the file.
Inputs: bin_file, log_file, use_sample.
propose_veVE map correction from a driveARead-onlyInspect
BMW E46 M3 (S54) MSS54HP, CSL conversion tuning: from a DME image and a drive log, the VE (alpha-N) map the drive supports — which cells change and by how much, which need more driving and how. Values only here; the free MSS54HP CSL CONVERT /// TUNER makes the tuned BIN from the same two files.
Inputs: bin_file, log_file, use_sample.
read_binRead an MSS54HP DME imageARead-onlyInspect
BMW E46 M3 (S54) MSS54HP DME, CSL conversion: read a 64 KB calibration partial and report the checksums, the logic patches (MAP, TANK VENT, WOT TH, RF GATE), how far the VE (alpha-N) and warm-up tables are from stock, and the VE table.
Inputs: bin_file, use_sample.
read_logRead an MSS54HP drive logARead-onlyInspect
BMW E46 M3 (S54) MSS54HP: read a drive log (Testo CSV, or TUNER's own CSV) and report its channels, how many rows the VE and rf_korr calculations can use, and why the rest were left out — each reason with what to change on the next drive. Attach the BIN it was driven on for the DME's own lambda thresholds.
Inputs: bin_file, log_file, use_sample.
smg2_compareCompare two SMG II calibrationsARead-onlyInspect
BMW E46 M3 SMG II (Siemens SMG2 510): which calibration items differ between two images of the same scope, how many cells, and the largest difference.
Inputs: xdf_file (required), image_file (required), other_file (required).
smg2_imageIdentify an SMG II imageBRead-onlyInspect
BMW E46 M3 SMG II (Siemens SMG2 510, the sequential gearbox ECU): say what an image is — the 24 KiB calibration window or the full 512 KiB flash — its ZB number, and whether its CRC checksums hold. Needs no definition.
Inputs: image_file, use_sample.
smg2_readDecode an SMG II calibrationARead-onlyInspect
BMW E46 M3 SMG II (Siemens SMG2 510): decode the calibration — shift speed thresholds per gear and program, gear ratios, clutch and launch settings — through the owner's MS4X definition with E46M3SMG2 /// MAPPING's corrections. Pass item for one item's full table and axes.
Inputs: xdf_file (required), image_file (required), item.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware.
Deterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation
Cardiopulmonary exercise test (CPET) analysis: ventilatory thresholds, metrics and substrate use.
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceConverts ECU Master EMU Black binary logs to MegaLogViewer HD format. Allows AI assistants to inspect channel summaries and perform analysis.2MIT
- AlicenseBqualityCmaintenanceEnables inspecting and comparing exported TunerStudio-style tune files and summarizing CSV logs, with firmware metadata, units, checksums, and format capabilities, without connecting to an ECU or modifying files.4MIT

agent-tuneofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze KTuner datalogs, check logged runs, and propose or write safe ECU table edits into a new .kcl tune file for review and flashing in KTuner. It helps identify knock, fuel, and ignition timing changes without flashing the car or altering the original tune file.2MIT- AlicenseAqualityBmaintenanceTurns Claude into a race engineer for original Assetto Corsa by reading telemetry, storing laps, and providing engineer-grade summaries, alongside read/write access to car setups.145MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.