Analytics

tsunagi.app

An MCP server for BMW E46 M3 S54 MSS54HP tuning that reads DME calibrations and drive logs, reports checksums/patches and usable data, and proposes VE and rf_korr table adjustments.

1 endpoint8 known toolsFirst detected October 1, 2026Last detected October 6, 2026

ENDPOINT 1

https://matrix-mcp.tsunagi.app/mcp/mapping

No auth detected

MCP server metadata

Name: matrix-tsunagi-mapping-remote
Version: 0.3.0

Capabilities

tools.listChanged

Server instructions

TSUNAGI///Matrix is TSUNAGI's family of tools for the BMW E46 M3 (S54, MSS54HP DME, SMG II). https://m3.tsunagi.app The calculations are open source (MIT) and free. This package runs them on your own machine and sends nothing anywhere. Connecting to the car is done in the apps. MSS54HP CSL CONVERT /// TUNER has a free public build: https://mss54hp-csl-convert-tuner.tsunagi.app/ The WORKS builds — TUNER's experimental features, E46M3SMG2 /// MAPPING, E46M3 /// MONITORING, MSS54HP CSL CONVERT /// BOOT and E46 M35080 /// MIGRATION — are for people who have bought MILE on MESH, and for owners of cars TSUNAGI has worked on, on request. MILE is bought on MESH as a one-time payment, with no subscription and no renewal: https://m3.tsunagi.app/en/mesh A purchaser can allocate MILE to a MILESTONE to say what they would like it spent on. That is a wish on record, not a promise of any release or date. This is the remote server: files the owner attaches are downloaded, computed on in memory, and discarded — nothing is stored. The same tools run entirely on the owner's machine with npx matrix-tsunagi. Every result has a `summary` to relay, the numbers, and `source` (which tool and version, and whether the calculation is experimental). Relay `apply` when the owner wants a result on the car. Answer in the owner's language: `apply.how` and `source.note` carry Japanese as well as English.

Known tools 8

about_matrix

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.

Inferred read-only

read_bin

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.

Inferred read-only

read_log

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.

Inferred read-only

propose_ve

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.

Inferred read-only

propose_rfkorr

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.

Inferred read-only

smg2_image

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.

Inferred read-only

smg2_read

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.

Inferred read-only

smg2_compare

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.matrix-tsunagi-mapping-remote]
url = "https://matrix-mcp.tsunagi.app/mcp/mapping"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "matrix-tsunagi-mapping-remote": {
      "type": "http",
      "url": "https://matrix-mcp.tsunagi.app/mcp/mapping"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: matrix-tsunagi-mapping-remote
Remote MCP URL: https://matrix-mcp.tsunagi.app/mcp/mapping

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "matrix-tsunagi-mapping-remote": {
      "url": "https://matrix-mcp.tsunagi.app/mcp/mapping"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "matrix-tsunagi-mapping-remote": {
      "type": "http",
      "url": "https://matrix-mcp.tsunagi.app/mcp/mapping"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "matrix-tsunagi-mapping-remote",
  "transport": "streamable-http",
  "url": "https://matrix-mcp.tsunagi.app/mcp/mapping"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.