Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Kia Access MCP

No user-submitted related servers found.

    Related Servers

    • Tesla MCP Server

      scald
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that connects to the Tesla Fleet API, allowing AI assistants like Claude to control Tesla vehicles and access vehicle information through natural language commands.
      19
      MIT

    • Unoffical Polestar 2 MCP

      holger1411
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that exposes Polestar 2 vehicle data to AI assistants like Claude. Query your car's battery status, vehicle info, and health data through natural conversation.
      1
      MIT

    • mcp-teslamate-fleet

      lodordev
      A
      license
      B
      quality
      D
      maintenance
      MCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.
      29
      2
      MIT

    • toyota-mcp

      zepgram
      A
      license
      A
      quality
      A
      maintenance
      Connects a MyToyota or MyLexus Europe account to Claude and other MCP clients, enabling natural-language access to fuel, range, location, trips, health, climate, charging data, and remote commands such as lock, climate, and charging.
      26
      72 PyPI
      1
      MIT

    • Tesla MCP Server

      Sara3
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects to the Tesla Fleet API, allowing users to control vehicles and retrieve real-time status updates through Claude and other AI assistants. It supports functions such as waking up vehicles, viewing detailed vehicle information, and debugging via both stdio and HTTP/SSE transports.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool targets a distinct resource+action, and the descriptions explicitly resolve the few potentially confusable pairs: kia_vehicle_status vs kia_refresh_status (cached vs live), and kia_session_status vs kia_healthcheck (local config check vs authenticated probe). The three MFA tools are clearly ordered steps with explicit inputs (otpKey/xid). No two tools appear to do the same thing.

    Naming Consistency5/5

    All 16 tools follow a uniform `kia_` prefix plus a consistent snake_case verb_noun pattern (kia_start_climate, kia_stop_charge, kia_set_charge_limits, kia_get... style reads like kia_vehicle_status, kia_charge_targets). Verb style is predictable throughout with no camelCase or mixed-convention outliers.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 band but each earns its place: read vs refresh, start vs stop pairs, charge read vs write, and three distinct auth steps. The count is justified by the breadth of the domain rather than padding.

    Completeness4/5

    Auth/MFA lifecycle (start_login, send_otp, verify_otp, forget_session, session_status, healthcheck), vehicle listing, status read/refresh, location, climate and charge control are all covered. The notable gap is remote door lock/unlock and other accessory commands (horn, lights) — vehicle_status reports door lock state but no tool can change it, though agents can work around the rest.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources