Skip to content
MCP server

Hyundai Bluelink / Kia Connect

Check charge, range, locks and location of a Hyundai, Kia or Genesis, and pre-heat it

Runs locallyStatus and history
Pricing
Open source
Platforms
self-hosted, CLI, macOS
Runs
Locally
Version
0.5.0
Listing updated
2 days ago

About Hyundai Bluelink / Kia Connect

Hyundai Bluelink / Kia Connect is an open-source MCP server for vehicles and mobility. It runs locally on your machine and is started by your AI client.

The server is read-only until you opt in. Seven read tools cover vehicles, last reported status, a rate-limited live refresh, trips, daily energy use and command results, and location is off unless allowed because it reveals where you live and park. Commands and unlocking are two separate switches, and tools that are not allowed are never registered, so the assistant cannot call them or be talked into it.

With writes enabled it can lock, start and stop climate with temperature, defrost, heated seats and steering wheel, start and stop charging, set charge limits and flash the hazard lights. Unlocking needs a further flag and confirmation each time. An optional audit log records each command without its location.

It is built on the library behind the Home Assistant integration and works with Bluelink, Kia Connect and Genesis Connect across Europe, the USA, Canada, Australia and other regions. It is unofficial, and the vehicle makers' APIs are undocumented and can change. Waking the car is rate limited to spare its 12V battery.

Install

Run in a terminal

claude mcp add bluelink-mcp --env BLUELINK_USERNAME='<BLUELINK_USERNAME>' --env BLUELINK_PASSWORD='<BLUELINK_PASSWORD>' --env BLUELINK_PIN='<BLUELINK_PIN>' -- docker run -i --rm -e BLUELINK_USERNAME -e BLUELINK_PASSWORD -e BLUELINK_PIN ghcr.io/mattoddie/bluelink-mcp:0.5.0

Add to claude_desktop_config.json

{
  "mcpServers": {
    "bluelink-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BLUELINK_USERNAME",
        "-e",
        "BLUELINK_PASSWORD",
        "-e",
        "BLUELINK_PIN",
        "ghcr.io/mattoddie/bluelink-mcp:0.5.0"
      ],
      "env": {
        "BLUELINK_USERNAME": "<BLUELINK_USERNAME>",
        "BLUELINK_PASSWORD": "<BLUELINK_PASSWORD>",
        "BLUELINK_PIN": "<BLUELINK_PIN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "bluelink-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BLUELINK_USERNAME",
        "-e",
        "BLUELINK_PASSWORD",
        "-e",
        "BLUELINK_PIN",
        "ghcr.io/mattoddie/bluelink-mcp:0.5.0"
      ],
      "env": {
        "BLUELINK_USERNAME": "<BLUELINK_USERNAME>",
        "BLUELINK_PASSWORD": "<BLUELINK_PASSWORD>",
        "BLUELINK_PIN": "<BLUELINK_PIN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "bluelink-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BLUELINK_USERNAME",
        "-e",
        "BLUELINK_PASSWORD",
        "-e",
        "BLUELINK_PIN",
        "ghcr.io/mattoddie/bluelink-mcp:0.5.0"
      ],
      "env": {
        "BLUELINK_USERNAME": "<BLUELINK_USERNAME>",
        "BLUELINK_PASSWORD": "<BLUELINK_PASSWORD>",
        "BLUELINK_PIN": "<BLUELINK_PIN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "bluelink-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BLUELINK_USERNAME",
        "-e",
        "BLUELINK_PASSWORD",
        "-e",
        "BLUELINK_PIN",
        "ghcr.io/mattoddie/bluelink-mcp:0.5.0"
      ],
      "env": {
        "BLUELINK_USERNAME": "<BLUELINK_USERNAME>",
        "BLUELINK_PASSWORD": "<BLUELINK_PASSWORD>",
        "BLUELINK_PIN": "<BLUELINK_PIN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "bluelink-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BLUELINK_USERNAME",
        "-e",
        "BLUELINK_PASSWORD",
        "-e",
        "BLUELINK_PIN",
        "ghcr.io/mattoddie/bluelink-mcp:0.5.0"
      ],
      "env": {
        "BLUELINK_USERNAME": "<BLUELINK_USERNAME>",
        "BLUELINK_PASSWORD": "<BLUELINK_PASSWORD>",
        "BLUELINK_PIN": "<BLUELINK_PIN>"
      }
    }
  }
}

Configuration

  • MCP_TRANSPORTRun over stdio. The image defaults to HTTP.
  • BLUELINK_USERNAMEThe email address you log in to the Bluelink, Kia Connect or Genesis Connect app with.Required
  • BLUELINK_PASSWORDYour app password.Required
  • BLUELINK_PINYour 4-digit app PIN. Europe and Canada need it for commands; reads work without it.
  • BLUELINK_REGIONWhere your account was created. europe includes the UK; try europe-cci if europe fails.
  • BLUELINK_BRANDhyundai (Bluelink), kia (Kia Connect, formerly UVO) or genesis (Genesis Connect).
  • BLUELINK_ALLOW_WRITESAllow commands to the car, such as locking, climate, charging, the horn and lights. Unlock has its own setting.
  • BLUELINK_ALLOW_UNLOCKAlso allow unlocking, after you confirm each time. Needs BLUELINK_ALLOW_WRITES.
  • BLUELINK_ALLOW_LOCATIONShare where the car is parked. This reveals where you live, work and park.
  • BLUELINK_AUDIT_LOGRecord every command as JSON lines: stderr, or a path in the container such as /data/audit.jsonl.

Tools this server provides (15)

Taken from the project documentation; the running server may differ.

list_vehicles
Lists vehicles on the account.
get_vehicle_status
Last reported battery or fuel, range, charging, climate, locks, doors, windows and tyres.
refresh_vehicle_status
Wakes the car for live data, rate limited.
get_vehicle_location
Latitude, longitude, map link and optional address.
get_trips
A day's trips or a month's summary.
get_energy_usage
Daily energy use for driving, climate, electronics and battery care.
get_command_status
Result of an earlier command.
lock_vehicle
Locks the doors.
start_climate
Pre-conditions the cabin.
stop_climate
Stops pre-conditioning.
start_charging
Starts charging.
stop_charging
Stops charging.
set_charge_limits
Sets AC and DC charge limits.
flash_hazard_lights
Flashes the hazards to find the car.
unlock_vehicle
Unlocks the doors.

What it does

Read-only by default
Commands and unlock each need their own switch.
Vehicle status
Charge, fuel, range, locks, doors, windows, tyres and warnings.
Climate control
Starts or stops pre-conditioning with temperature, defrost, seats and steering wheel.
Charging control
Starts or stops charging and sets AC and DC limits.
Trips and energy
Daily trips, monthly summaries and energy use.
Audit log
Optionally records every command sent to the car.

Good for

  • Ask whether the car is charged and locked
  • Warm the cabin before leaving
  • Review a month of driving
  • Find where you parked

Pricing

Open source

MIT licence; needs your Bluelink or Kia Connect login

Prices change. Check bluelink-mcp.mattoddie.dev before you buy.

Hyundai Bluelink / Kia Connect FAQ

Which brands work?

Hyundai Bluelink, Kia Connect and Genesis Connect, in most regions.

Can it unlock the car?

Only if both writes and unlock are enabled, and each unlock is confirmed.

Is it official?

No. It is unofficial and not affiliated with Hyundai, Kia or Genesis.

How do I run it?

Use Docker, uv, or the one-click Claude Desktop bundle; a Bluelink or Kia Connect login is required.

Is Hyundai Bluelink / Kia Connect free?

Yes. Hyundai Bluelink / Kia Connect is open source, so you can use and self-host it for free.

How do I add Hyundai Bluelink / Kia Connect to Claude Code?

Run this command in your terminal: claude mcp add bluelink-mcp --env BLUELINK_USERNAME='<BLUELINK_USERNAME>' --env BLUELINK_PASSWORD='<BLUELINK_PASSWORD>' --env BLUELINK_PIN='<BLUELINK_PIN>' -- docker run -i --rm -e BLUELINK_USERNAME -e BLUELINK_PASSWORD -e BLUELINK_PIN ghcr.io/mattoddie/bluelink-mcp:0.5.0