Log inSubmit server
Kiaaccess MCP logo

Kiaaccess MCP

Connects Claude to Kia Access for vehicle status, location, EV charging, climate, and confirmation-gated vehicle commands.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kiaaccess MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kiaaccess-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "kiaaccess-mcp"
      ],
      "env": {
        "KIA_USERNAME": "YOUR_VALUE_HERE",
        "KIA_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 16 tools correctly (1d ago).

Overview

The kiaaccess-mcp MCP server connects MCP clients to a Kia vehicle through the private Kia Owners API used by the Kia Access app. It supports MFA bootstrapping, vehicle discovery, cached status, location, odometer, EV charging data, climate control, and selected vehicle commands. Use it when an agent needs to inspect or manage an enrolled Kia, while accounting for confirmation requirements and real-world command effects. Node.js 22.5 or later and Kia Access account credentials are required.

Use cases

  • Check a Kia vehicle's lock state and EV charge
  • Refresh vehicle telemetry before reading the odometer
  • Find a vehicle using its last reported location
  • Start climate preconditioning with confirmation
  • Set charging limits for supported plug types

Key features

  • Kia Access account MFA bootstrap
  • Vehicle status and location queries
  • EV charge state and target management
  • Climate and charging commands
  • Confirmation-gated door controls
  • Local session token storage

Tools16

What Kiaaccess MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

What it can do

From the 16 tools this server returned when we ran it; 16 declare their own safety hints.

Can delete or modify data · 3Handles credentials · 10Makes network requests · 14Read-only tools · 13
Unusual tool instructions. 1 tool description contain text aimed at the AI model rather than at you (asks the assistant to hide something from the user). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age85 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · kiaaccess-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.8kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed16Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Kiaaccess MCP works

What kiaaccess-mcp does

The kiaaccess-mcp MCP server exposes Kia Access account and vehicle operations through MCP. It can establish a session with a Kia Owners or Kia Access account, list enrolled vehicles, and retrieve information such as lock state, ignition, climate data, mileage, location, and EV charge state. Vehicle identifiers are supplied through the listing tool, while VINs and other sensitive values are masked in responses.

Read operations include session inspection, vehicle listing, cached status, status refresh, location lookup, charge targets, and odometer-related data. The status refresh wakes the vehicle telematics unit but does not return the new reading directly; call the status tool afterward.

How it works

Initial access uses a three-step MFA flow. The server starts a login, sends a one-time code by SMS or email, and exchanges that code for a stored remember-me token. The token is saved locally and is not returned through an MCP tool. Subsequent sessions can be created without repeating MFA until the stored session is discarded or replaced.

Write operations are confirmation-gated. Depending on client support and configuration, a write either displays a confirmation prompt or uses a preview and one-time confirmation token. Commands report acceptance separately from observed vehicle state because Kia may acknowledge a request before the car applies it. State changes can take 30–60 seconds to appear.

Setup and configuration

Build the project with Node.js 22.5 or newer using npm install followed by npm run build, then provide KIA_USERNAME and KIA_PASSWORD. The repository includes an environment-file example, and the local .env file is intended to remain untracked. The server does not log credentials or return the password through tools.

Set KIA_WRITE_MODE to control which command tools are registered. none enables no vehicle commands, comfort enables climate and charging commands, and all additionally enables door locking and unlocking. Invalid values fail closed to none.

For a remote deployment, bootstrap MFA on a machine where someone can read the code, use the same fixed KIA_DEVICE_ID on both machines, and provide the resulting token through KIA_RMTOKEN. The token should be handled like a password because it bypasses MFA and permits vehicle control when combined with the account credentials.

Tools and capabilities

The available tools cover:

  • Session status, login initiation, OTP delivery, OTP verification, and local session removal.
  • Vehicle listing with keys, nicknames, models, mileage, and masked VIN suffixes.
  • Cached status, telematics refresh, last reported location, map link, and charge targets.
  • Climate start and stop, charging start and stop, and charge-limit updates.
  • Door locking and unlocking when the all write mode is enabled.

The kiaaccess-mcp MCP server verifies climate, charging, charge-limit, and door commands by reading the relevant vehicle fields again. Climate temperature is best-effort, and charge commands require the car to be plugged in to take effect.

Limitations and notes

The location tool returns the last reported position, not a live GPS fix. Cached status is only as current as the vehicle's last upload, while refreshing status takes longer and consumes some vehicle power.

Unlocking leaves the vehicle physically unsecured and is available only in all mode. Commands affect a real vehicle, so confirmations should be treated as operational safeguards rather than ordinary tool permissions. Kia's terms govern use, and the project is not an official Kia integration.

Do not repeatedly retry a rejected login. Kia counts failed attempts and may enable a reCAPTCHA requirement that prevents server-side login for the account. Verify the credentials in the Kia Access app before trying again.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kiaaccess MCP

kiaaccess-mcp is an MCP server that connects an MCP client to an enrolled Kia vehicle through the Kia Owners API used by Kia Access. Its main tools handle MFA login, vehicle listing, status, location, climate, charging, charge limits, and confirmation-gated door lock or unlock commands.

Install it with Node.js 22.5 or later by cloning the repository, running `npm install`, and then running `npm run build`. Configure `KIA_USERNAME` and `KIA_PASSWORD`, then register the server in an MCP client such as Claude Code.

Authenticate it through the three-step MFA flow: start the login, send an OTP by SMS or email, and verify the code. The resulting remember-me token is stored locally and is not returned by the tools.

Yes, but only when `KIA_WRITE_MODE=all` registers the door tools and the command is confirmed. Unlocking leaves the vehicle unsecured, and the server verifies the resulting door state by reading the vehicle again.

Yes. Claude Desktop can use the server through its confirmation-token flow because it does not provide the same confirmation prompt behavior as Claude Code. Writes first return a preview and require a valid follow-up token.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKiaaccess MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kiaaccess-mcp?style=directory)](https://allmcps.com/mcp/kiaaccess-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/kiaaccess-mcp"><img src="https://allmcps.com/api/badge/kiaaccess-mcp?style=directory" alt="Kiaaccess MCP on AllMCPs" /></a>