unit-convert__unit_convert — Fatstack MCP Tool
unit-convert__unit_convert
(unit convert unit convert) is one of 14 tools on the
Fatstack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unit-convert__unit_convert from your client
- Claude Code Fatstack unit-convert__unit_convert run in your project directory
- Claude Desktop Fatstack unit-convert__unit_convert ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fatstack unit-convert__unit_convert ~/.cursor/mcp.json
- VS Code Fatstack unit-convert__unit_convert .vscode/mcp.json
- Zed Fatstack unit-convert__unit_convert ~/.config/zed/settings.json
- Windsurf Fatstack unit-convert__unit_convert ~/.codeium/windsurf/mcp_config.json
- Cline Fatstack unit-convert__unit_convert ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fatstack unit-convert__unit_convert ~/.gemini/settings.json
- Grok Fatstack unit-convert__unit_convert .mcp.json (in your project root)
- ChatGPT Fatstack unit-convert__unit_convert Settings → Connectors → Advanced → Developer mode
- Claude.ai Fatstack unit-convert__unit_convert Settings → Connectors → Add custom connector
- LangChain Fatstack unit-convert__unit_convert pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http registry https://www.fatstack.net/api/mcp
Other tools on this server
- fatstack__free_demo
- echo__echo_json
- json-schema-validate__json_schema_validate
- html-to-markdown__html_to_markdown
- url-metadata__url_metadata
- csv-to-json__csv_to_json
- text-language-detect__text_language_detect
- regex-test__regex_test
- cron-explain__cron_explain
- uuid-batch__uuid_batch
- markdown-lint__markdown_lint
- askzephy-quick-scan__sol_audit
- askzephy-quick-scan__sol_quick_scan
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.