# PrecisionConvert Unit Engine MCP > PrecisionConvert Unit Engine converts physical measurements instantly and accurately. It handles everything from lengths (meters to feet) to weights, temperatures, and volumes across Metric and Imperial systems. Your AI client acts like a dedicated conversion specialist, ensuring that regardless of your field—be it engineering calculation or recipe scaling—your physical data is always normalized. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** unit-conversion, measurement, metric-system, imperial-system, physical-constants, data-transformation ## Description Your AI client uses the `convert_units` tool to instantly transform a numerical value between any two specified physical units. This engine handles conversions across mass, length, temperature, and volume. The conversion process maps data automatically between major global systems like Metric standards and Imperial standards. You just give your agent a number and two unit types—say, feet and meters—and it spits out the accurate numerical result. It's built to handle complex scenarios where you need consistent numbers regardless of whether you’re working in New York or Tokyo. For instance, if you’re scaling up a recipe, it converts weight units (like pounds to kilograms). If you’re doing an engineering calculation, it handles length conversions (like inches to millimeters) and volume measurements. You don't need to look up conversion factors; the engine manages that dirty work for you. When your agent uses `convert_units`, it returns a precise numerical output based on the two physical units and the value you provide. This means whether you're converting degrees Celsius to Fahrenheit, or milliliters to liters, the system handles the entire calculation in one go. If you need to verify what conversions are even possible before running a calculation, your agent uses the `list_supported_units` tool. Calling this function returns an exhaustive list of every single unit type supported by the conversion engine. This allows you to check the database and make sure your input units—like 'tons' or 'rankine'—are valid categories for conversion. The scope of measurements is massive. It handles temperature conversions across all major scales, so if you give it a reading in Fahrenheit, it won’t just guess; it converts it correctly to Celsius, and vice versa. Similarly, when dealing with length, the system knows that meters relate to feet, and those relationships hold true even if you mix them up in your prompt. This setup is critical for any field that deals with global data sets or mixed measurement systems. Think about a construction project where one team uses imperial measurements for lumber while another uses metric units for concrete pour volumes. Your AI agent keeps everything normalized, ensuring the final numbers match up perfectly. It’s not just converting; it's standardizing. The `list_supported_units` capability lets you pull back full lists of categories and specific units available in the database. You get a complete picture, so when your prompt requires a unit—say, 'psi' for pressure or 'BTU' for heat—you know exactly what codes to use. It’s documentation built right into the workflow. The `convert_units` tool handles multiple physical dimensions simultaneously. If you need to convert a mix of units in one go—like converting the volume from gallons and also ensuring the corresponding weight is correctly converted from pounds—the system processes those relationships accurately. You don't write boilerplate conversion logic into your client; you just ask for the final, correct number. The precision means that if your calculation requires a specific degree of accuracy for mass (like grams to ounces) or length (like yards to meters), the engine delivers it without fail. It’s reliable because it accesses a massive internal mapping structure, so you never have to worry about deprecated conversion standards or outdated formulas. This server lets your agent act like a specialized unit clerk who speaks every language of measurement. When you send data through your AI client, it gets cleaned up and standardized immediately. You get the final number you need—no messy intermediate steps, no manual checks required on your end. ## Tools ### convert_units Takes two physical units and a value to return the converted numerical result. ### list_supported_units Returns an exhaustive list of every unit type supported by the conversion engine. ## Prompt Examples **Prompt:** ``` Convert 25 degrees Celsius to Fahrenheit. ``` **Response:** ``` Converting... 25 degrees Celsius is equal to 77 degrees Fahrenheit. Would you like to perform another temperature conversion? ``` **Prompt:** ``` How many pounds are in 50 kilograms? ``` **Response:** ``` Checking the mass conversion... 50 kilograms is approximately 110.23 pounds. ``` **Prompt:** ``` List all supported length units. ``` **Response:** ``` Retrieving the unit list... I've found various length units including meters (m), kilometers (km), miles (mi), inches (in), and feet (ft). Would you like to see the full technical identifiers? ``` ## Capabilities ### Convert Physical Measurements Converts numerical values between specified physical units, covering mass, length, temperature, volume, and more. ### Handle Global Standards Mapping Maps data between major systems like Metric and Imperial standards automatically during conversion calls. ### Identify Supported Unit Types Retrieves a full list of every unit type available in the database, allowing you to check unit validity before calculation. ## Use Cases ### A Mechanical Engineer needs report consistency. The engineer is writing a stress analysis that uses metric units but must reference Imperial standards. Instead of manually converting every value, they prompt their agent: 'Convert 150 megapascals to pounds per square inch.' The agent uses `convert_units` and provides the exact required number, saving hours of cross-checking. ### A Science student needs a reference list. The student is writing a literature review that references multiple measurement systems. First, they ask their agent to run `list_supported_units` just to see all the length units available (meters, miles, feet). Then, they use `convert_units` for specific conversions needed in their thesis. ### A Supply Chain analyst is normalizing raw data. The team receives an inventory manifest listing materials by volume in cubic meters and weights in tons. The analyst directs the agent to use `convert_units` multiple times, converting all units into standardized imperial measurements (cubic feet, pounds), making the data usable for export. ### A Culinary hobbyist scales a recipe. The user finds an excellent international recipe that uses cups and ounces. They ask their agent: 'How many milliliters are in 3.5 cups?' The agent uses `convert_units` to provide the precise volume measurement, allowing them to cook without guessing. ## Benefits - **Calculate Temperature Changes:** You don't have to remember if a formula needs Celsius or Fahrenheit. Just ask your agent to convert it using `convert_units`, and you get the correct reading every time. - **Maintain Data Integrity in Reports:** When compiling global reports, physical units often clash. By calling `convert_units`, your data pipeline automatically normalizes weights (e.g., kg to lbs), preventing fatal errors. - **Validate Unit Systems Fast:** Before writing code or running a calculation, use `list_supported_units`. This quickly shows you if the system supports feet, inches, or specific temperature scales you need. - **Handle Diverse Physical Quantities:** The engine covers more than just length. You can convert volumes (liters to gallons) and weights (pounds to kilograms) using a single tool call, making your agent reliable across domains. - **Simplify Unit Conversions for Non-Engineers:** If you're just converting a recipe from metric to imperial on the fly, `convert_units` handles the complexity, letting you get the number you need without looking up conversion charts. ## How It Works The bottom line is: you ask for a unit change using plain language, and it gives you the correct number without error. 1. Subscribe to this server. No API key is needed; it has public access. 2. Ask your AI client to perform a conversion (e.g., 'What's 50 kilograms in pounds?'). 3. The engine runs the calculation and returns the precise, converted value back to your chat or code. ## Frequently Asked Questions **Can I convert 100 meters to feet?** Yes! Use the `convert_units` tool with `value` set to 100, `from` to 'm', and `to` to 'ft'. It will return the result accurately. **How many units are supported by this engine?** The engine supports hundreds of units across categories like length, mass, volume, temperature, and pressure. Use the `list_supported_units` tool to see the full list. **Is the conversion high precision?** Yes. The underlying engine uses industry-standard conversion factors to ensure decimal-level accuracy for scientific and engineering needs. **Does using `convert_units` require an API key or special authentication?** No, this server is public access and requires no API keys. You can connect your AI agent to perform conversions immediately. This makes setup fast and straightforward for any client. **How do I check what types of units are supported using `list_supported_units`?** It lists all physical units across categories like length, weight, temperature, and volume. Calling this tool gives you the full range of measurement systems available for conversion. **What is the best practice when calling `convert_units` with different unit types?** You must specify both the numerical value and the source/target units in a single call. For example, converting 'kilograms to pounds' requires clear input for both parameters. **Are there any limitations when using `PrecisionConvert Unit Engine` with different AI clients?** No specific limits exist across MCP-compatible clients like Claude or Cursor. Your agent simply needs to be able to invoke the defined tools via the Model Context Protocol. **When should I call `list_supported_units` before attempting a conversion?** You use it when you aren't sure of the exact technical identifier for a unit. This ensures your agent uses the precise name required by the system, preventing conversion errors.