OBD-II MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBD_FAST | No | Whether to use fast mode (true/false). | |
| OBD_PORT | No | The serial port for the ELM327 adapter (e.g., COM3 or /dev/rfcomm0). | |
| OBD_TIMEOUT | No | Timeout in seconds (e.g., 30). | |
| OBD_BAUDRATE | No | The baudrate to use (e.g., 38400). | |
| OBD_MCP_HOST | No | Host for HTTP transport (e.g., 127.0.0.1). | |
| OBD_MCP_HTTP_PORT | No | Port for HTTP transport (e.g., 8000). | |
| OBD_MCP_TRANSPORT | No | Transport mode: 'stdio' or 'streamable-http'. | |
| OBD_RECONNECT_DELAY | No | Delay in seconds between reconnect attempts. | |
| OBD_RECONNECT_ATTEMPTS | No | Number of reconnect attempts. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connection_statusA | Check the ELM327/ECU connection, port, and OBD-II protocol. Use this first when a vehicle may be off or disconnected. |
| list_supported_sensorsA | List live sensor PIDs discovered as supported by the vehicle. Use these exact names with read_sensor. |
| read_sensorB | Read one or several supported sensors and return values with units. Examples: RPM, SPEED, COOLANT_TEMP, INTAKE_PRESSURE. |
| read_dtcA | Read stored and pending/current-cycle diagnostic trouble codes. Includes python-OBD technical descriptions when known and does not modify the ECU. |
| clear_dtcA | Clear ECU DTCs and freeze-frame only after explicit user approval. Set confirm=true; this may reset readiness monitors and temporarily turn off the MIL. |
| get_vehicle_infoA | Read VIN, Check Engine/MIL state, DTC count, and OBD-II protocol. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear and distinct purpose: connection status, supported sensor list, live sensor reads, DTC reading, DTC clearing, and vehicle info. Potential overlap between get_connection_status and get_vehicle_info regarding protocol is minimal and contextually distinct.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_connection_status, read_sensor, clear_dtc). The verb choices are appropriate for each action and create a predictable API surface.
Six tools cover the core OBD-II operations without unnecessary bloat. The count is well suited to the domain and keeps the interface focused and manageable.
The set covers the essential OBD-II workflows: checking connectivity, discovering supported sensors, reading live data, retrieving DTCs, clearing DTCs, and obtaining vehicle identification. No critical operations appear missing for a read-focused OBD-II MCP server.