Official New

Wheel Fitment API MCP Server

Name: wheel-size-mcp
Author: Wheel-Size.com

Connect Claude, Cursor, Windsurf, Zed or any MCP-capable client to live wheel & tire fitment data — no code required. Built and maintained by Wheel-Size.com, the API provider, via the Model Context Protocol.

GitHub PyPI v0.5.1 MCP Registry $ uvx wheel-size-mcp

What you can ask

Once connected, your AI assistant can query the vehicle catalog, run fitment searches and build product cards on your behalf. Great for rapid prototyping, interactive data exploration, and getting to a first working integration faster.

“What are the OEM wheel specs for a 2024 Toyota Camry?”

“Which vehicles fit 5x114.3 18x8 ET35 rims?”

“Calculate plus-size options for 225/50R17 on 7Jx17 ET40”

“Generate a product card for this wheel showing all compatible vehicles”

Quick start

Get an API key

Sign up free — the Sandbox plan needs no credit card. Once your application is approved, replace your-api-key-here in the snippets below with your key.

Add the server to your AI client

The server runs via uv (uvx) — no manual install, no cloning. Pick your client:

One command in your terminal:

export WHEELSIZE_API_KEY="your-api-key-here"
claude mcp add wheel-size-api -- uvx wheel-size-mcp

Or commit a shared config to .mcp.json in your project root (reads the key from your shell environment):

{
  "mcpServers": {
    "wheel-size-api": {
      "command": "uvx",
      "args": ["wheel-size-mcp"],
      "env": {
        "WHEELSIZE_API_KEY": "${WHEELSIZE_API_KEY}"
      }
    }
  }
}

Add to claude_desktop_config.json — on macOS: ~/Library/Application Support/Claude/, on Windows: %APPDATA%\Claude\:

{
  "mcpServers": {
    "wheel-size-api": {
      "command": "uvx",
      "args": ["wheel-size-mcp"],
      "env": {
        "WHEELSIZE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "wheel-size-api": {
      "command": "uvx",
      "args": ["wheel-size-mcp"],
      "env": {
        "WHEELSIZE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "wheel-size-api": {
      "command": "uvx",
      "args": ["wheel-size-mcp"],
      "env": {
        "WHEELSIZE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Add to your Zed settings.json (Cmd+, opens settings):

{
  "context_servers": {
    "wheel-size-api": {
      "command": {
        "path": "uvx",
        "args": ["wheel-size-mcp"],
        "env": {
          "WHEELSIZE_API_KEY": "your-api-key-here"
        }
      }
    }
  }
}

Restart your client and ask away

The server starts automatically when the client launches. Try: “What are the OEM wheel specs for a 2024 Toyota Camry?”

Available tools (21)

Every tool maps to a Wheel Fitment API v2 endpoint. Your assistant picks the right one from your question.

Catalog — vehicle lookup

6 tools

ws_list_makes — all manufacturers; the entry point
ws_list_models — models for a make
ws_list_years — available years
ws_list_generations — generations as an alternative to years
ws_list_modifications — trims for a specific vehicle
ws_list_regions — market regions (USDM, EUDM, JDM…)

Search — fitment data

8 tools

ws_search_by_vehicle — OEM wheel & tire specs for a vehicle
ws_search_by_rim — vehicles compatible with a rim
ws_search_by_tire — vehicles by metric tire size, with facets
ws_search_by_hf_tire — vehicles by high-flotation (LT) size
ws_check_rim_fitment_for_vehicle — one-call rim check
ws_check_tire_fitment_for_vehicle — one-call tire check
ws_check_hf_tire_fitment_for_vehicle — one-call HF-tire check
ws_calculate_upsteps — plus/minus sizing calculator

Classified — e-commerce product cards

6 tools

ws_find_tires_for_rim — compatible tire sizes for a rim
ws_find_vehicles_for_rim — vehicles that fit a rim
ws_find_vehicle_modifications_for_rim — trim-level drill-down
ws_find_vehicles_for_tire — vehicles that use a tire size
ws_find_vehicles_for_package — vehicles for a rim + tire combo
ws_find_vehicle_modifications_for_package — package drill-down

Utility & workflow prompts

1 tool + 3 prompts

ws_get_spec_metadata — computed geometry, population stats and intelligence hints for any spec

Pre-built MCP prompts guide agents through multi-step flows:

vehicle_fitment_lookup — full catalog-to-search chain
rim_compatibility_check — metadata-to-classified flow
product_card_generation — e-commerce card workflow

Self-hosted HTTP mode

Besides stdio, the server can run as a standalone Streamable HTTP service — one shared instance for your team instead of Python on every machine:

wheel-size-mcp --transport http --port 8000

The MCP endpoint is served at http://127.0.0.1:8000/mcp/. The server binds to localhost by default and holds your API key server-side — expose it beyond localhost only behind an authenticating reverse proxy. Details in the README.

Fair use of search tools

Per the API Terms of Usage, search, fitment-check and classified tools must be initiated by real users — do not call them in autonomous agent loops. Catalog and utility tools carry no such restriction.

Why “official” matters

This server is published in the MCP Registry as io.github.driveate/wheel-size-mcp and is the only server built and maintained by Wheel-Size.com, the API provider. Third-party wrappers exist in the registry but are not affiliated with us, are not covered by our support, and may lag behind API changes.

Ready to try it?

A free Sandbox key is all you need — connect your assistant in under a minute.

Get Free API Key View on GitHub