Encoding MCP Tools for AI Agents

Ask an LLM to base64-encode a string and you'll get something that looks like base64 — but decodes to garbage. LLMs can't compute encodings; they generate plausible-looking output. These tools produce correct encoded/decoded values every time.

All Encoding Tools (20)

Your agent gets access to 20 encoding tools via the /mcp/encode/ endpoint. Here's the complete list:

Tool	Description
`encode/base64/encode`	Base64 Encode
`encode/base64/decode`	Base64 Decode
`encode/url/encode`	Url Encode
`encode/url/decode`	Url Decode
`encode/html/encode`	Html Encode
`encode/html/decode`	Html Decode
`encode/hex/encode`	Hex Encode
`encode/hex/decode`	Hex Decode
`encode/binary/encode`	Binary Encode
`encode/binary/decode`	Binary Decode
`encode/ascii/encode`	Ascii Encode
`encode/ascii/decode`	Ascii Decode
`encode/rot13`	Rot13
`encode/morse/encode`	Morse Encode
`encode/morse/decode`	Morse Decode
`encode/json/minify`	Json Minify
`encode/json/prettify`	Json Prettify
`encode/jwt/decode`	Jwt Decode
`encode/punycode/encode`	Punycode Encode
`encode/punycode/decode`	Punycode Decode

Agent Scenarios

Here's how real agents use these tools:

1. API integration agent

An integration agent base64-encodes credentials for HTTP Basic Auth headers. encode/base64-encode produces correct output.

Tool Call: encode/base64-encode

{ "text": "username:password" }

2. Web scraping agent

A scraping agent URL-encodes query parameters to build valid request URLs. encode/url-encode handles special characters correctly.

Tool Call: encode/url-encode

{ "text": "hello world & more" }

3. Security analysis agent

A security agent decodes JWT tokens to inspect claims without a secret key. encode/jwt-decode parses the payload safely.

Tool Call: encode/jwt-decode

{ "token": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0..." }

MCP Setup

Add encoding tools to your agent in under 2 minutes. Choose your client:

Claude Desktop / Claude Code

Add this to your MCP config:

{
  "mcpServers": {
    "tinyfn-encode": {
      "url": "https://api.tinyfn.io/mcp/encode/",
      "headers": {
        "X-API-Key": "your-api-key"
      }
    }
  }
}

Cursor

Go to Settings > MCP and add a new server:

Type: SSE
URL: https://api.tinyfn.io/mcp/encode/sse
Headers: X-API-Key: your-api-key

Tip: Use the category-specific endpoint (/mcp/encode/) for the best experience. The all-in-one endpoint (/mcp/all/) works too but has 500+ tools which some clients handle less efficiently.

When to Use These Tools

Use encoding MCP tools when your agent needs to:

Guarantee correctness — when wrong answers have real consequences
Process user data — when you're operating on actual user input, not hypothetical examples
Maintain consistency — when the same input must always produce the same output

You don't need these tools for casual conversation or rough estimates. Use them when precision matters.

Ready to add encoding tools to your agent?

Get Free API Key 100 requests/month free. No credit card required.

Frequently Asked Questions

Why can't LLMs do Base64 encoding?

Base64 encoding is a deterministic algorithm that maps bytes to characters. LLMs generate text probabilistically, so they produce output that resembles Base64 but doesn't decode correctly.

What encoding formats does TinyFn support?

TinyFn supports Base64 encode/decode, URL encoding/decoding, HTML entity encoding/decoding, hex encoding/decoding, JWT decoding, and morse code.

Can TinyFn handle binary data encoding?

TinyFn handles text-to-encoding conversions. For binary data, you can pass hex-encoded input and use the appropriate conversion tools.