Skip to main content
Glama
sanjibani

cox-automotive-mcp

by sanjibani

Related Servers

Alternatives to cox-automotive-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Pipedrive API v2, enabling management of deals, persons, organizations, products, activities, and pipelines through natural language in MCP clients like Cursor and Claude Desktop.
      28 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the Qualia title and escrow platform, enabling you to talk to your orders, messages, and documents from Claude, Cursor, or any MCP client.
      7
      MIT
    • 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
      293 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct action (create, delete, get, update, list, iterate, search) on specific resources (vehicle, account, incentive, health). Even the paired list_/iter_ versions are clearly differentiated by pagination vs. flat array. No ambiguity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern. The outlier is health_check, which uses a noun_noun structure instead of a clear verb (e.g., check_health). Otherwise, naming is predictable and uniform.

    Tool Count5/5

    14 tools is well-scoped for a dealership management domain. Each tool serves a clear purpose without redundancy. The count is neither too sparse nor excessive.

    Completeness4/5

    Vehicles have full CRUD coverage (create, get, update, delete, list, iterate, search). Accounts and incentives are read-only (get, list, iterate/search) but that may be by design. Minor gap: no create/update/delete for accounts or incentives, but core workflows are covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues