Unit Converter API MCP Server

Unit conversion — length, weight, temperature, volume, speed, data. x402 micropayment. Exposed over MCP by the unit converter api mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Convert between units -- length, weight, temperature, volume, speed, data storage. Formula included. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Its toolset

Everything the assistant can do here goes through one of these:

• utility_convert_units — POST

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Unit Converter API's toolset — utility_convert_units — is a fair guide to whether it matches your workflow. It is maintained by Br0ski777; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the unit converter api mcp server does with a few real requests.