I was looking at my agent's toolset yesterday and realized something unsettling. It wasn't just searching through my local repo or querying a Postgres instance to find an edge case. It was checking if the windows in my Volvo were closed.

We talk a lot about LLMs writing code, but we don't talk enough about the moment where 'context' shifts from digital files to physical state. When you bridge the gap between an agent and hardware via the Model Context Protocol (MCP), you aren't just giving it new data; you are extending its agency into the physical world.

The recent release of the Volvo Cars Connected MCP server is a perfect, albeit high-stakes, example of this shift. It isn't some novelty wrapper for checking your car's mileage. When you map tools like get_battery_status, get_doors_status, and get_tires_status to an agentic workflow, you are fundamentally changing how we interact with IoT infrastructure.

The technical reality of the implementation

You can find the specific server configuration here: https://vinkimius.com/mcp/volvo-cars-connected