cox-automotive-mcp
Related Servers
Alternatives to cox-automotive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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 npm2MIT
- AlicenseAqualityCmaintenanceFirst MCP server for the Procare Connect API, enabling querying child care center data (attendance, enrollments, family balances, etc.) via natural language from Claude, Cursor, or any MCP client.16MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.MIT
- AlicenseAqualityCmaintenanceMCP 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.7MIT
- 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.17293 npmMIT
- AlicenseBqualityDmaintenanceMCP server for accessing Claude Code plugins. Enables retrieving plugin lists and detailed information via MCP clients like Claude Desktop, Cursor.2MIT
TDQS
Scored across 14 tools
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.
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.
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.
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.