Connect AI assistants (MCP)

The MCP server lets AI assistants like Claude query the Tire Library catalog through natural conversation — no code required. Ask things like "Find 205/55R16 winter tires from Michelin" and the assistant looks them up for you.

Requirements

  • An active API Monthly subscription (the same plan that unlocks API keys).
  • An MCP-compatible client: Claude.ai, Claude Desktop, ChatGPT, or similar.

Connect in Claude.ai

  1. Go to Settings → Connectors → Add custom connector.
  2. Enter the server URL: https://mcp.tireweblibrary.com/sse
  3. Click Connect — a browser window opens to our sign-in page.
  4. Sign in with your Tire Library email and password.
  5. Done — the assistant can now query the catalog on your behalf.

What the assistant can do

  • Search tires by size, item number, make, or detailed filters (speed/load rating, season, terrain, run-flat, 3PMSF, and more)
  • Browse makes and patterns, get full tire specs, compare tires side by side
  • Check which sizes fit a specific vehicle (year/make/model/trim)
  • Look up current manufacturer rebates

Everything is read-only — the assistant can view catalog data but can't change anything.

Sign-in behaviour

  • You sign in once through your browser (OAuth). No API key is needed.
  • Sessions renew automatically while you're using the assistant. After about 7 days of inactivity, you'll be asked to sign in again — just click Connect and log in once more.

MCP or API key?

  • Interactive assistants (Claude on your desktop, team use): use the MCP server (this page).
  • Production integrations and unattended server-side agents: use an API key against the REST API instead. A headless process can't complete the browser sign-in, so MCP sessions would stop working after the 7-day expiry. See API keys.

Troubleshooting

"Your account does not have MCP access"

MCP requires the API Monthly plan. Upgrade your subscription, then connect again.

The assistant suddenly asks me to sign in again

Normal — sessions expire after ~7 days of inactivity. Reconnect and sign in once; you're good for another week of active use.

Slow or failing responses under heavy use

Tool calls share the REST API's rate limit (200 requests per 60 seconds). If the assistant reports errors mentioning status 429, wait a moment and retry.

See also