Vehicle Diagnosis MCP Server

This repository provides a Spring Boot MCP server that bridges a local vehicle diagnosis REST API to prompt-driven requests using the MCP Java SDK.

Requirements

• Java 17+
• Maven 3.9+
• Docker + Docker Compose (for containerized runs)

Configuration

The server proxies requests to the locally installed diagnosis backend. Configure the base URL with:

export DIAGNOSIS_API_BASE_URL=http://localhost:8090

Default: http://localhost:8090.

The MCP server itself runs on http://localhost:7070 by default (override with SERVER_PORT).

Swagger file path defaults to input/swagger-docs.customization.json and can be overridden via MCP_SERVER_SWAGGER_PATH (must stay within the input directory).

Build

mvn clean package

Run Locally

mvn spring-boot:run

MCP Prompt Endpoint

Send a prompt to /mcp/prompt (REST convenience endpoint):

curl -X POST http://localhost:7070/mcp/prompt \
  -H "Content-Type: application/json" \
  -d '{"prompt":"What is the identification of the ECU Engine electronics from my connected Audi Q4 e-tron FZ"}'

Select Vehicle

curl -X POST http://localhost:7070/mcp/selectVehicle \
  -H "Content-Type: application/json" \
  -d '{"manufacturer":"Audi","series":"Q4 e-tron","vehicle":"FZ"}'

MCP SDK Endpoints

The MCP SSE endpoint is /sse, and the message endpoint is /mcp/message (see mcp.server.base-url).

Claude Desktop (localhost:8085)

If you run the MCP server on http://localhost:8085, configure the port before starting:

export SERVER_PORT=8085
mvn spring-boot:run

In Claude Desktop, open Settings → Developer → Edit Config and add an MCP server that targets the local SSE endpoint:

{
  "mcpServers": {
    "vehicle-diagnosis": {
      "transport": "sse",
      "url": "http://localhost:8085/sse",
      "messageUrl": "http://localhost:8085/mcp/message"
    }
  }
}

Restart Claude Desktop after saving the config.

Docker

docker compose build
docker compose up

Update the diagnosis-backend image in docker-compose.yml to the actual container image for your installed diagnosis backend.

Notes

• The MCP endpoint currently routes prompts to the underlying REST API with a minimal keyword-based mapping.
• The backend REST API definition is available in input/swagger-docs.customization.json (single-line JSON file).
• The MCP SSE endpoints are exposed at /sse and /mcp/message.