Kia Access MCP
Related Servers
Alternatives to Kia Access MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA 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.16MIT
- AlicenseNot gradedqualityDmaintenanceAn 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.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for controlling Polestar vehicles via natural language, enabling climate, charging, locks, location, and vehicle status management through Claude.MIT
- AlicenseBqualityDmaintenanceMCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.292MIT
- AlicenseAqualityAmaintenanceConnects 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.26189 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceAn 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
TDQS
Scored across 17 tools
Every tool targets a distinct resource or action: the MFA flow is spread across start_login, send_otp, and verify_otp with explicit ordering, session introspection cleanly splits local (session_status) from network (healthcheck), and ambiguous reads like refresh_status vs vehicle_status are clearly differentiated by freshness intent. Even the paired start/stop commands are unambiguous because the target (climate vs charge) is embedded in the name.
All tools share the kia_ prefix with underscore-separated names, but conventions split: actions use verb_noun (start_climate, set_charge_limits, forget_session) while passive reads use bare noun phrases (vehicle_status, session_status, charge_targets, healthcheck) without a get_ or read_ prefix. kia_healthcheck also breaks the pattern as a compound noun rather than a verb-initial name.
At 17 tools this is slightly above the typical 3-15 sweet spot, but the breadth of the domain justifies it: MFA bootstrap requires three sequential steps, session management needs status/forget/export operations, and vehicle control requires read/write and start/stop pairs for both climate and charging. Each tool earns its place with a distinct role.
Core workflows are well covered: full session lifecycle (bootstrap, verify, status, forget, export, healthcheck), vehicle state (list, cached status, refresh, location), charging (targets read/write, start/stop), and climate (start/stop). Obvious gaps like door lock/unlock or remote horn/light commands are absent, but the server's apparent scope of climate, charging, status, and session management is complete.