bluelink-mcp
Provides tools for interacting with Hyundai Bluelink, enabling AI assistants to check vehicle status (battery/fuel, range, charging, climate, locks, doors, windows, tyres, warnings), retrieve location and trips, and optionally send commands like lock/unlock, start/stop climate, start/stop charging, set charge limits, and flash hazard lights.
Works with Kia Connect accounts to provide similar vehicle status, location, trip, and energy usage data, and optionally execute remote commands such as locking, climate control, and charging management.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bluelink-mcpIs my car locked and charged? What's the range?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bluelink-mcp
Talk to your Hyundai.
An open-source Model Context Protocol server for Hyundai Bluelink. It lets Claude and other AI assistants check your car's charge, fuel, range, locks and location, and, if you allow it, pre-heat the cabin, lock the doors or start charging.
Quick start · Documentation · Tool reference · Contributing
It's built on hyundai_kia_connect_api, the library behind the Home Assistant Kia/Hyundai integration, so it also works with Kia Connect and Genesis accounts in the regions that library supports.
"Is the car charged, and is it locked?" The Santa Fe is at 80% (about 52 km of electric range, 610 km total with fuel) and finished charging at 06:10. All doors are locked and the windows are closed. Bluelink last heard from it 25 minutes ago.
This is an unofficial project and isn't affiliated with Hyundai. Bluelink's API is undocumented and changes without notice.
Tools
Tool | What it does | Needs |
| Vehicles on the account | |
| Last reported battery/fuel, range, charging, climate, locks, doors, windows, tyres, warnings and charging schedule. Doesn't wake the car. | |
| Wakes the car for live data. Rate limited (see below). | |
| Latitude/longitude, map link and optional address | |
| A day's trips, or a month's summary | |
| Daily energy use for driving, climate, electronics and battery care | |
| Result of an earlier command | |
| Lock the doors | writes |
| Pre-condition the cabin: temperature, duration, defrost, heated rear window/mirrors and steering wheel, seats | writes |
| Start or stop charging | writes |
| AC/DC charge limits (EVs; most plug-in hybrids don't support this) | writes |
| Flash the hazards to find the car | writes |
| Unlock the doors | writes + unlock |
Every tool takes an optional vehicle (name, VIN or ID). You can leave it out if the account has one car.
Related MCP server: Tesla MCP Server
Quick start
You need a Bluelink account that works in the app, and uv or Docker.
Claude Code with uv (stdio)
git clone https://github.com/mattoddie/bluelink-mcp && cd bluelink-mcp
claude mcp add bluelink \
-e BLUELINK_USERNAME=you@example.com \
-e BLUELINK_PASSWORD='your-password' \
-e BLUELINK_PIN=1234 \
-e BLUELINK_ALLOW_WRITES=true \
-- uv run --directory "$PWD" bluelink-mcpClaude Desktop and other clients use the same command (uv run --directory /path/to/bluelink-mcp bluelink-mcp) with the same environment variables.
Docker (Streamable HTTP)
cp example.env .env # fill in BLUELINK_* and a random MCP_AUTH_TOKEN (openssl rand -hex 32)
docker compose up -d
claude mcp add --transport http bluelink http://<docker-host>:8080/mcp \
--header "Authorization: Bearer <MCP_AUTH_TOKEN>"Then ask "How's the car doing?"
Configuration
All settings are environment variables; example.env lists and explains them.
Variable | Default | |
| Your Bluelink app login (required) | |
| Your Bluelink PIN. Europe needs it for remote commands. | |
|
|
|
|
|
|
|
| Response language (Europe) |
|
| Add a street address to the location via OpenStreetMap |
|
| Register the command tools |
|
| Also register |
|
| Minimum gap between |
|
| How long a status read is reused |
|
| Login token cache. Set it empty to turn caching off. |
|
|
|
|
| HTTP listen address |
| Bearer token clients must send. Required for | |
| Optional Host header allow-list for DNS rebinding protection |
Which region?
In the UK and the rest of Europe, start with europe, the classic Bluelink Europe service. Some newer Hyundais use the CCI/"OneApp" backend instead. If login or status fails with europe, try europe-cci.
Being kind to your car (and your account)
Reads come from Bluelink, not the car.
get_vehicle_statusreturns what the car last uploaded, which happens when it is switched off, while charging and after commands. Checklast_updated_at.Waking the car costs something.
refresh_vehicle_statusmakes the car's modem report in. Done often, this drains the 12V battery, and Hyundai Europe limits API calls per day. It is rate limited per car (BLUELINK_MIN_REFRESH_MINUTES).Logins are cached. Repeated password logins can get a Bluelink account temporarily blocked, so the server keeps the token in
BLUELINK_TOKEN_FILE(mode0600). The file contains your session tokens and password, so treat it like a password.Commands are slow. They travel over the mobile network and usually take 20–60 s. With
wait=true(the default), the tool waits for the car to confirm.timeoutmeans the car didn't answer, not necessarily that nothing happened.
Safety
The server is read-only unless you set BLUELINK_ALLOW_WRITES=true, and unlock_vehicle needs its own BLUELINK_ALLOW_UNLOCK=true switch. Tools carry MCP annotations (read-only, destructive) so clients can ask before running them. In HTTP mode every request needs the bearer token, so don't expose the port to the internet without TLS in front of it.
Documentation
From nothing to your first question | |
Claude Code, Claude Desktop, VS Code, Cursor, Codex, stdio | |
Every setting, and choosing a region | |
Example questions, cached vs live data, commands | |
Every tool and argument | |
Running it well |
Development
uv sync
uv run pytest
uv run ruff check . && uv run ruff format --check .The tests use a fake vehicle manager, so they need no Bluelink account or network. See Development and the contributing guide.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
- mytesla.ioOAuthio.mytesla
Control your Tesla from your AI assistant - climate, charging, access, and security.
- AskMyEVOAuthcom.askmyev
Tesla data for your AI: battery, range, charging, tires, alerts, history. Controls off by default.
Tesla Fleet API for AI: send navigation destinations, read battery and location, run car commands.
Control your Tesla - wake it, warm it up, unlock and more. Get your developer token at https://Infoseek.ai/mcp. Also requires your own Tesla developer token which is tied to your car/fleet.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to control and monitor Tesla vehicles via natural language through the Tessie API, supporting battery, climate, security, charging, and more.611MIT
- FlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Tesla vehicles via the Tessie API, providing state and command tools for climate, locks, charging, and navigation.-
- FlicenseAqualityDmaintenanceExposes a connected-vehicle OBD-II/telematics platform to AI agents, enabling vehicle health scoring, live data queries, DTC decoding, maintenance prediction, and gated remote commands via a pluggable data layer.9-
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to read selected Home Assistant data and perform limited home-control actions like turning on/off lights and running scenes, with a strict allowlist for security.MIT