bluelink-mcp
Related Servers
Alternatives to bluelink-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI agents to inspect connected vehicles and issue lock/unlock commands through a scoped, authenticated vehicle API, with telemetry, capability, location access, and explicit confirmation for destructive actions.6134 npmMIT- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to your own Kia vehicle through the Kia Owners API, enabling vehicle status, location, odometer, EV charge state, and confirm-gated commands for doors, climate, and charging.16289 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an assistant to check a Tesla vehicle's status and lock it through signed Vehicle Command Protocol messages, including automatic nightly locking, while keeping status reads non-waking and state-changing actions confirmation-gated.MIT
- 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-
- AlicenseAqualityDmaintenanceEnables AI assistants to control and monitor Tesla vehicles via natural language through the Tessie API, supporting battery, climate, security, charging, and more.611MIT
- AlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Tesla vehicles via the Tessie API, providing state and command tools for climate, locks, charging, and navigation.MIT
TDQS
Scored across 6 tools
The main overlap is between refresh_vehicle_status and get_vehicle_status, but the descriptions explicitly distinguish them (wake vs. cached read), so an agent can choose correctly. All other tools target distinct data (commands, energy, trips, vehicle list).
All six tools follow a consistent verb_noun snake_case pattern (get_*, list_*, refresh_*), with no mixing of conventions. get_trips is a minor stylistic deviation but still fits the pattern.
Six tools is well-scoped for a read-oriented vehicle status server, with each tool covering a distinct data domain (status, commands, energy, trips, account). No filler or redundant tools.
get_command_status implies remote commands exist, yet there is no tool to issue commands (lock, start climate, charge), creating a dead end. Core read coverage (status, energy, trips, vehicles) is solid, but the command lifecycle is one-sided.