Connect your AI (Claude or another) to your vehicle
Connect Claude Desktop, Claude Code or another AI client to your organization's vehicles to analyze their reads in depth. Your AI reads; if it needs a new read, it asks and you approve it.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Administration › AI agents
The platform has an MCP server (the protocol Claude and other AI clients use to connect to tools). With a key of your organization, your AI looks at your vehicles, your diagnosis reads and the code library, and helps you find the cause of a fault.
1. Create the key (only your organization's administrators)
- Go to Administration › AI agents and click “New key”.
- Give it a name that says where you will use it (for example, “Claude on the workshop computer”) and choose how long it is valid.
- Under “What it can do”, tick “Vehicle diagnosis” and, if you want your AI to be able to ask for new reads, “Request new reads”.
- Click “Create key” and confirm your identity with the second factor.
- Copy the key right away: it is not shown again.
2. Connect your AI client. The server address is https://app.diaglana.com/api/v1/agent/mcp and the key goes in the “Authorization: Bearer” header followed by the key.
| Client | Setup (replace YOUR_KEY with yours) |
|---|---|
| Claude Code | claude mcp add --transport http diaglana https://app.diaglana.com/api/v1/agent/mcp --header "Authorization: Bearer YOUR_KEY" |
| Claude Desktop | In the configuration file, inside “mcpServers”: "diaglana": { "command": "npx", "args": ["-y", "mcp-remote", "https://app.diaglana.com/api/v1/agent/mcp", "--header", "Authorization:${DIAGLANA_AUTH}"], "env": { "DIAGLANA_AUTH": "Bearer YOUR_KEY" } } |
| Another MCP client | A “Streamable HTTP” server at that address, with the header Authorization: Bearer YOUR_KEY. |
3. What your AI can do
- See your organization's vehicles (make, model, year and the end of the VIN) and their finished diagnosis reads: codes with their status bits, freeze frames, live values, monitors and control units, with the full VIN.
- See the saved results of “Full diagnosis” and compare them with the previous one of the same vehicle.
- Look up the meaning, causes and “What to check” of a code, and “What already worked in your workshop” with that code.
- Ask for a new read that only reads (a diagnosis read, the automatic vehicle detection or a service function that only reads). The request appears in Administration › AI agents › “Reads your AI asks for”: nothing reaches the device until a person clicks “Approve and send”. The device still asks for its own confirmations.
4. What your AI can never do
- Write to the vehicle, clear codes, code, program, adapt or run routines or actuator tests.
- Use vehicle security functions (immobilizer, keys, security codes).
- See your customers' contact details or data of other organizations.
- Follow orders written inside the data: what the vehicle, the control units or external sources say arrives marked as data, never as an instruction.
5. Price and balance
- The platform sets the price of the advanced tools: it can be free, per request, per session or per day of use, and your organization can have its own price. You see it in Administration › AI agents.
- It is charged to your organization's prepaid balance. Without enough balance, your AI only has the reduced report (codes with their meaning and severity) and is told how to top up.
- A request that fails or is refused is not charged.
6. Your data
- Your AI receives the data of your vehicles and reads, including the full VIN. Your AI's provider processes it under the terms you have with them.
- Every request is audited with your name and the key's, and counts toward each key's limit of 30 per minute and 600 per hour.
- The platform's diagnosis assistant is another option: it works inside the web. Using your own provider key in it is being prepared.
Important: Keep the key like a password. Do not paste it in chats, documents or repositories. If you suspect it, click “Revoke”: it stops working at once.
Tip: Start by asking your AI, for example: “Look at the vehicle's latest read and tell me what you would check first”.
More guides in this section
- How a remote session works
- Tunnel plan: connect a tool to the vehicle remotely
- Accept or withdraw remote access to your vehicle
- Collaborating in a session: messages, prompts and photos
- Unit PassThru mode from the app
- PassThru on Mac, Linux and iOS
- Assistance requests, appointments and work orders
- Legacy vehicle configuration and diagnostics: VAG and other makes
- Modern vehicle coding and programming
- How to diagnose each type of vehicle
- Automatic diagnosis: one tap and it explains
- Reading a vehicle and sharing the report
- CANopen diagnostics for machinery
- Vehicle details: identifying it by the VIN
- Live dashboard, service functions and battery test
- v2 procedures: beta and operational
- Control unit images: store, edit and prepare writing
- Forensic cases: custody of forensic reads
- Forensic mode and diagnosis mode
- Forensic authorizations: who can use the forensic reads
- Quick inspection for authority agents
- Aftertreatment expert review (sensors, monitors and indicators)
- Compatibility notices for your tool
- CAN captures
- Pre-purchase report
- Vehicle report
- Battery health of electric and hybrid cars
- Asking Diaglana for help
- Your first read: understanding the result and what to do
- Diagnosis options: each setting and when to change it
- Workshop settings: requests, orders, network and notices
- Reading: choosing the protocol and understanding the OBD on UDS report
- What a fault code means
- Live data: dashboards, recording and export
- Attaching fault codes to a work order
- Procedures that write, program or authenticate
- ISOBUS: reading and changing an implement's NAME
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates
- AI diagnosis assistant: asking for help with a read