UDS-MCP
Related Servers
Alternatives to UDS-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA local-first, read-only MCP server for vehicle diagnostics that exposes structured OBD-II tools for reading PIDs, DTCs, and ECU snapshots without raw protocol access.7Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to identify connected drives, read/write and back up parameters, control speed and positioning, capture oscilloscope data, flash firmware, and run validation workflows through existing Drivesoft communication components.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to deterministically inspect, author, convert, validate, and diagnose Classical CAN and CAN FD databases and trace logs, including bit-layout validation, template generation, trace aggregation, ISO-TP/UDS reassembly, bus-health analysis, and reverse engineering.MIT
- AlicenseNot gradedqualityAmaintenanceExposes 20 vehicle-security tools to AI coding agents such as Claude Code and Cursor, enabling them to send, fuzz, and analyze CAN frames, run UDS diagnostics and seed-key handshakes, simulate DoIP ECUs, and decode ISO-TP, J1939, DBC, and V2X data. Everything runs against a virtual CAN bus, so no vehicle or hardware is required.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to interact with Vector CANoe for automotive bus testing and diagnostics using natural language commands.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that drives Keil µVision debug sessions for 8051/C51 targets via the native UVSOCK/UVSC interface: build, run control, breakpoints, and read/write of variables, memory & expressions (22 tools). Works with the Keil Simulator (no hardware needed) or GLink+/ULINK on real targets.1MIT
TDQS
Scored across 11 tools
Each tool maps to a distinct UDS diagnostic service or utility, so an agent can readily choose between session control, reset, DID read/write, security access, routines, DTCs, and tester present. send_raw overlaps by design as an explicit fallback for services without a dedicated tool, but its purpose is clearly stated and does not make the specialized tools ambiguous.
All tool names use consistent snake_case and largely mirror standard UDS service terminology, making the set readable and predictable. However, several names are noun phrases rather than strict verb_noun forms (e.g. security_access, routine_control, tester_present), so the pattern is slightly mixed.
Eleven tools is well-scoped for a UDS diagnostic server: the set covers the core services agents commonly need without becoming unwieldy. Each dedicated tool has a clear role, and send_raw prevents the need to add many rarely used service-specific tools.
The server covers the main diagnostic lifecycle: session control, reset, DID read/write, security access, routines, DTC read/clear, tester present, and raw requests. Some UDS service areas such as IO control, memory transfer/download, or extended DTC snapshot reads lack dedicated tools, but send_raw provides a practical fallback.