Your mechanic charges by the hour. Claude charges by the token and it still can't hold a wrench.
A mobile dev on r/mcp hooked his car up to Claude through an MCP server he built for his own OBD2 app, typed "check my car" from the couch, and got back a diagnosis that caught stuff he'd skimmed past for over a year. The car isn't fixed yet tho. And honestly that's the most interesting part.
ok so what did he actually build
The car is a 2015 Audi Q5 (2.0 TFSI, EA888 Gen2, about 186k km) with a cold start misfire on cylinders 1 and 2 that's been hanging around for over a year. He got tired of copy pasting scanner logs into chats so he wired the whole thing up properly:
ELM327 (BLE) > his phone app (Kotlin Multiplatform) > MCP server > Claude
Through that server Claude can check if the phone is connected and what the car supports (adapter, protocol, VIN, battery voltage, MIL), read stored, pending and permanent codes with the freeze frame, read readiness monitors and IUMPR, pull live data or record a session that comes back as min/max/avg plus a trend per channel, open saved scans synced to his account, and look up codes in a catalog in 10 languages.
that synced-scans bit means the agent works when he's nowhere near the car.
The app is his own, AI ELM, and he disclosed that up top, respect. Per the post the scanner part is free and the Claude connector is part of the subscription. The AI ELM site lists a €4.99 monthly plan with 100 AI credits, though the site itself doesn't mention MCP at all right now.
what Claude pulled out of one report
From a single saved report it flagged: MIL on, P0300/P0301/P0302 stored and permanent, plus an old P0456 (small EVAP leak). The freeze frame was captured 3 seconds after start with coolant at 25°C and 1296 rpm, no load. Timing sat at -17.5°, which is catalyst heating mode, and the misfire only shows up in that window.
Then the fuel trims. LTFT was +14.8% cold, and his older logs showed +20 to 23% at warm idle but only +10 to 12% under load. Lean at idle that improves with load usually points to unmetered air, so the PCV / oil separator diaphragm became suspect number one. It also called out 11.8 V with key on (weak battery) and catalyst, O2 and EVAP monitors still not ready after 34 km and 6 warm ups.
Over a few sessions it got sharper. An earlier VCDS scan had P11A600 (AVS cam actuator, cyl 2), Claude called that the root cause, he swapped the actuator and that code hasn't come back. Mode 06 counters per cold start were cyl 2 = 327, cyl 1 = 64, cyl 3 and 4 = 0. The plan now is cheapest first: PCV, swap coils, cold leak down test, then walnut blasting.
ngl solid triage. it's giving "senior tech who reads the freeze frame."
hot take: the car is the least interesting part
Everyone's gonna read this as "AI mechanic is here." I don't think that's the story. The misfire is still there, the one confirmed fix was a code that a human scan tool already surfaced, and generic OBD2 can't even read manufacturer codes like P11A6. He still uses VCDS for those.
The real gold is the section he called "stuff I learned building it," because it's basically a free MCP design guide:
- Claude tested the server and found real bugs. Search only matched translated names, results got cut off with no flag saying so, and one preset quietly swapped channels when the car didn't support misfire counters.
- Send summaries, not raw samples. Min/max/avg plus a 12 point trend per channel was plenty for the model to reason with.
- Say out loud when a channel isn't supported. Otherwise the model happily reasons over data that was never recorded.
- The freeze frame is underrated. If he could give an LLM one thing from a scan, it'd be that.
All of that applies to your CRM tool too. Silent truncation and silent fallbacks are how agents end up confidently wrong, and imo "the tool lied by omission" is a way more common failure than "the model is dumb."
read-only is a feature, not a limitation
Compare this with the other car-plus-Claude story going around. The Drive reported on a YouTuber whose 1994 Jeep Cherokee failed California emissions. Claude identified the old computer's protocol, suggested a $3 Arduino Nano to read it, then asked to run the fuel pump and cranked up the pressure on its own. Later, with help from OpenAI's Codex, they reflashed the computer and the Jeep passed.
Cool! Also lowkey terrifying. The AI ELM server, going by what the post lists, reads codes and data and stops there. imo that's the right default for anything with an engine.
Same logic applies to agents in boring software land. Say your agent reads a scan report and then books a garage slot in Google Calendar. You want it to create events, sure, but not delete your whole week. That's the kind of split MewCP handles: you pick which tools each agent gets, like read and send but not delete, and anything switched off is stopped before it reaches the app. The keys sit in a vault and get injected per call, so the agent never holds a login it could leak.
stuff we still don't know
- The comments. The r/mcp post had 13 upvotes and 6 comments when we checked and the thread wouldn't load, so no community verdict yet.
- Whether the PCV theory is right. It's a reasoned guess from fuel trim patterns, not a confirmed fix. He says plainly the car isn't fixed.
- How the connector is exposed. The post describes the tools but not the auth setup or whether the server is open to other users yet, and the AI ELM site doesn't cover it.
Until a follow up says "it was the PCV," it's a great tool-design case study wearing a car costume.
Sources