Schema | OBD MCP Server

OBD MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

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`	{}

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.

Interactive templates invoked by user choice

Name	Description
`obd_read_only_safety`	Apply the server's read-only and non-roadworthiness constraints.

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.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ayhammouda/obd-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server