Cars MCP Server

What is Cars MCP Server?

The Cars MCP Server is an MCP (Model Context Protocol) server built using Spring AI. It demonstrates the use of Spring AI’s ToolCallback API to expose tools that interact with a static list of cars representing Amarpreet’s wishlist.

How to use Cars MCP Server?

Build the project with mvn clean install, then run java -jar target/carsmcpserver-0.0.1-SNAPSHOT.jar. The server registers three tools (get_cars, get_car_by_name, get_car_by_years) that can be invoked programmatically or through an AI-driven interface. No web UI is provided—it is a non‑web MCP server.

Key features of Cars MCP Server

• Built with Spring AI and the ToolCallback API
• Exposes three car query tools (get_cars, get_car_by_name, get_car_by_years)
• Manages a hardcoded wishlist of four cars
• Initialized via @PostConstruct at application startup
• Configured as a non‑web MCP server via application.properties

Use cases of Cars MCP Server

• Query the complete wishlist of cars using the get_cars tool
• Find a specific car by its model name with get_car_by_name
• Retrieve a car by its build year using get_car_by_years
• Serve as a reference implementation for Spring AI MCP tool registration

FAQ from Cars MCP Server

What tools does the server provide?

Three tools: get_cars (returns all cars), get_car_by_name (finds by model name), and get_car_by_years (finds by build year).

How do I run the server?

Build with mvn clean install, then run java -jar target/carsmcpserver-0.0.1-SNAPSHOT.jar. The server starts without a web interface.

What cars are in the initial wishlist?

The initial list contains: BMW Neue Klasse (2025), Ferrari EV (2025), Mercedes AMG 4dr EV (2025), and Porsche 718 Boxster (2025).

Is this a web application?

No. The application is configured as a non‑web MCP server (spring.main.web-application-type=none), so it does not expose an HTTP endpoint.