encode_decode_base64 — utility converter MCP Tool
encode_decode_base64
(encode decode base64) is one of 7 tools on the
utility converter
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call encode_decode_base64 from your client
- Claude Code utility converter encode_decode_base64 run in your project directory
- Claude Desktop utility converter encode_decode_base64 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor utility converter encode_decode_base64 ~/.cursor/mcp.json
- VS Code utility converter encode_decode_base64 .vscode/mcp.json
- Zed utility converter encode_decode_base64 ~/.config/zed/settings.json
- Windsurf utility converter encode_decode_base64 ~/.codeium/windsurf/mcp_config.json
- Cline utility converter encode_decode_base64 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI utility converter encode_decode_base64 ~/.gemini/settings.json
- Grok utility converter encode_decode_base64 .mcp.json (in your project root)
- ChatGPT utility converter encode_decode_base64 Settings → Connectors → Advanced → Developer mode
- Claude.ai utility converter encode_decode_base64 Settings → Connectors → Add custom connector
- LangChain utility converter encode_decode_base64 pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http utility-converter https://utility-converter.onrender.com/mcpOther tools on this server
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.