INDIVIDUAL MCP TOOL

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.

tsunagi.appnone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for about_matrix and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

tsunagi.app

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.

Related tools

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