Skip to main content
Glama
zepgram

toyota-mcp

by zepgram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to toyota-mcp

No user-submitted related servers found.

    Related Servers

    • Kia Access MCP

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      A 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.
      17
      433 npm
      MIT

    • myUplink MCP Server

      kalmma
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients (e.g., Claude) to your NIBE myUplink heat-pump account for reading sensors and controlling settings via OAuth2 authentication.
      1
      MIT

    • KOVA MCP

      joeexafionbot-dev
      A
      license
      A
      quality
      C
      maintenance
      Connects Claude and other MCP clients to myGEKKO building controllers via the official Query API, enabling natural-language queries and control of smart-home devices. It is read-only by default, with write actions available only through explicit opt-in and safety policies.
      3
      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.3/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action with explicit 'Use for' guidance and cross-references, e.g. get_status vs get_health and get_energy vs get_charging. Even near-overlaps like find_car vs sound_horn and the three trip tools are cleanly separated by output shape or intent.

    Naming Consistency5/5

    All tools follow a consistent toyota_ + verb + object pattern in snake_case, e.g. toyota_get_status, toyota_lock_doors, toyota_start_climate. The only slight deviation is toyota_charge_now, but it still reads naturally as a command verb.

    Tool Count3/5

    26 tools is a heavy surface, above the 16-25 band and bordering on too many for a single MCP server. However, each tool earns its place given the broad Toyota connected-car domain of reads, trips, and remote commands, so the count feels broad rather than redundant.

    Completeness4/5

    The set covers vehicle discovery, status, energy, charging, trips, health, location, climate, fuel stations, and major remote commands. Minor gaps remain around management actions such as setting charging schedules, customizing climate presets, and stopping charging, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources