OBD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| obd_list_vehiclesA | List configured vehicles using normalized, VIN-safe identities. |
| obd_get_vehicle_statusB | Read connection and ECU status. This is an observation, not a roadworthiness determination. |
| obd_read_standard_pidsA | Read only fixed, centrally allowlisted Mode 01 PIDs; arbitrary commands and service identifiers are not accepted. |
| obd_read_dtcsB | Read DTC observations without clearing or changing vehicle state. |
| obd_read_ecu_snapshotB | Read an ECU snapshot using only identifiers in a validated, source-labeled read-only profile. |
| obd_open_issueA | Create an issue only in the local SQLite database. This never sends a vehicle command or changes vehicle state. |
| obd_get_issue_timelineA | Read a diagnostic issue timeline from the local SQLite database. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| obd_read_only_safety | Apply the server's read-only and non-roadworthiness constraints. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OBD MCP read-only safety contract | Safety and interpretation guidance for every OBD MCP result. |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: listing vehicles, reading status, reading PIDs, reading DTCs, reading ECU snapshots, and managing local issues. There is no overlap between tool purposes.
All tools follow a consistent 'obd_verb_noun' naming pattern (e.g., obd_read_dtcs, obd_open_issue), making the tool set highly predictable.
7 tools is a reasonable number for a diagnostics-focused server, covering core read operations and local issue tracking without being overwhelming or sparse.
The tool set covers essential read-only OBD functions and issue management, but lacks common operations like reading VIN, freeze frame data, or clearing DTCs, which are typical in OBD diagnostics.