# Jersey Size Converter AI Agent Connect

> Jersey Size Converter MCP handles the math and mapping for apparel sizing. It lets your AI client translate specific manufacturer sizes or regional standards into the equivalent fit for a different brand or territory. Instead of guessing if a Nike US Men's Large fits the same as an Adidas EU Men's Large, your agent uses this MCP to get the exact match.

## Overview
- **Category:** utilities
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_rHhv5s5TawEbd4cXnpf4jUiqAoaV9VJ1bDClRJq8/ai-agent-connect
- **Tags:** size-conversion, jersey, apparel, mapping, sports-gear

## Description

Managing apparel inventory or helping customers find the right fit is difficult when every brand uses different sizing logic. This MCP solves that by providing your AI agent with precise mapping tables for jersey sizes. You can use it to bridge the gap between regional standards, like US vs EU, or between specific manufacturer scales. 

Your agent can check if a specific size identifier is even valid before attempting a conversion, preventing errors in your workflow. It can also look up which sizing systems are currently supported to ensure you're using the right context for a request. Whether you are building a shopping assistant or managing a sports gear database, this MCP provides the technical translation layer needed to ensure sizing accuracy across diverse product catalogs.

## Tools

### get_size_equivalence
This tool calculates the exact equivalent size in a target scale for a specific jersey. It provides the direct translation between two different sizing systems.

### list_available_systems
This tool shows you all the valid sizing mapping tables and systems currently supported. Use it to see which brand or regional contexts are available for conversion.

### search_size_mappings
This tool identifies the possible size transitions available between two specific contexts. It helps your agent understand how sizes move from one system to another.

### validate_size_format
This tool checks if a size identifier is valid and recognizable. It acts as a guardrail to ensure a size is legitimate before you try to convert it.

## Prompt Examples

**Prompt:** 
```
What is the equivalent size for a 'Large' in the Nike_US_Men system when converting to ISO_Standard_Adult?
```

**Response:** 
```
The equivalent size in the ISO_Standard_Adult system is 'L'.
```

**Prompt:** 
```
Is the size 'XL' valid in the Adidas_EU_Women system?
```

**Response:** 
```
Yes, 'XL' is a valid size identifier in the Adidas_EU_Women system.
```

**Prompt:** 
```
List all available size systems for the 'sports' category.
```

**Response:** 
```
The available systems in the sports category are: Nike_US_Men, Adidas_EU_Men, and ISO_Standard_Adult.
```

## Capabilities

### Cross-brand mapping
Your agent translates sizes from one manufacturer's scale to another.

### Regional conversion
The MCP converts sizes between different regional standards like US and EU.

### Size validation
Your agent verifies that a size string is valid before processing it.

### System discovery
The agent can query which specific sizing systems are available to use.

## Use Cases

### Automated Shopping Assistants
An agent uses the MCP to tell a customer that their usual size in one brand matches a specific size in another.

### Inventory Normalization
A developer uses the tool to convert various supplier size formats into a single standard for a database.

### Customer Support Bots
A support agent uses the tool to accurately answer fit questions during a live chat.

### Sports Gear Cataloging
A user maps different sports jersey sizes to a unified ISO standard for easier searching.

## Benefits

- Eliminates manual lookup of brand-specific size charts.
- Prevents errors by validating size formats before conversion.
- Standardizes apparel data across multiple regional systems.

## How It Works

Connect the MCP to your client and let your agent handle the sizing math.

1. Connect the MCP to your AI client via Vinkius.
2. Your agent identifies the available sizing systems.
3. The agent validates the input size format.
4. The agent performs the conversion using the mapping tables.
5. The final equivalent size is returned to your workflow.

## Frequently Asked Questions

**How does this MCP handle different brands?**
It uses specific manufacturer mapping tables to translate sizes between different brand scales.

**Can I use this with Claude or Cursor?**
Yes, this MCP works with any MCP-compatible client including Claude, Cursor, and Windsurf.

**Does it support international sizing?**
Yes, it includes regional mapping tables to convert between different global sizing systems.

**How do I know if a size is valid?**
You can use the validate_size_format tool to check if a size identifier is recognized by the system.

**Where is the data hosted?**
Vinkius hosts and manages the MCP, so it is ready to use immediately after connection.

**How do I know which size systems are available?**
You can use the `list_available_systems` tool to retrieve a full registry of all valid mapping contexts and their descriptions.

**Can I convert sizes between different brands?**
Yes, provided a mapping table exists between the two brands. Use `search_size_mappings` to check if a transition is defined between your source and target systems.

**What happens if a size is not found in the target system?**
If the `get_size_equivalence` tool cannot find a match for the provided size within the specified system, it will return an error indicating the size is not found.