Unit Converter API
Convert length, weight, temperature, volume, speed, and data units inside agent workflows without hard-coding conversion tables.
Overview
io.github.Br0ski777/unit-converter is an MCP server for the Build phase that converts length, weight, temperature, volume, speed, and data units via a remote API.
What is this MCP server?
- Converts length, weight, temperature, volume, speed, and data-size units
- Remote Unit Converter API exposed as MCP over SSE
- x402 micropayment on unit-converter.api.klymax402.com
- Version 1.1.0 from Br0ski777/unit-converter-x402 repository
- Agent-callable alternative to embedding large static conversion libraries
- Server version 1.1.0
- Remote SSE: https://unit-converter.api.klymax402.com/mcp
- Unit families listed: length, weight, temperature, volume, speed, data
What problem does it solve?
Your agent keeps guessing unit math in specs and code, risking subtle conversion bugs across locales and domains.
Who is it for?
Developers using agents to build apps with mixed unit systems who want a single MCP call instead of copying conversion snippets.
Skip if: Hard real-time embedded systems or production hot paths that cannot depend on remote APIs or micropayments.
What do I get? / Deliverables
You get authoritative converted values in agent context so generated code, configs, and copy use consistent units.
- Converted numeric values across supported unit families
- Agent context usable in code snippets, tests, and user-facing strings
Recommended MCP Servers
Journey fit
Unit conversion is a Build-phase utility when agents generate formulas, configs, migrations, or UI copy that must stay dimensionally correct. Integrations covers small dependable external capabilities; this MCP offloads conversion math so feature code stays focused on product logic.
How it compares
Hosted conversion micro-API over MCP, not a bundled open-source library skill in your repo.
Common Questions / FAQ
Who is io.github.Br0ski777/unit-converter for?
Solo builders and agent users who need quick, consistent unit conversions while writing application logic, docs, or tests.
When should I use io.github.Br0ski777/unit-converter?
Use it during Build when agents draft features involving physical units, temperatures, speeds, or data sizes and you want verified numbers inline.
How do I add io.github.Br0ski777/unit-converter to my agent?
Add remote MCP server URL https://unit-converter.api.klymax402.com/mcp (SSE) in your client and configure x402 payments if required.