all-your-base64

All Your Base64 exposes an MCP server that provides base64 encoding/decoding tools optimized for AI workflows and automation. The server runs as a standalone process and communicates via standard I/O, exposing tools such as encode, decode, recall, jobs, datauri, memory, and more. Users can integrate the MCP server into their MCP clients (e.g., VS Code, Claude Desktop, or custom clients) to issue tool calls like encode or datauri and then retrieve structured results along with metadata. The server is designed to remember previous tasks, detect changes via checksums, and recall previous jobs to streamline repetitive encoding/decoding tasks in AI or coding pipelines.

Prerequisites:

• Node.js and npm installed on your system
• Access to the npm registry (public internet)

Install globally (recommended for quick access):

npm install -g ayb64

Or install locally in a project:

npm install ayb64

Run the MCP server using the provided command:

ayb64 mcp

Alternatively, you can run the development/startup variant if you prefer:

npm run mcp

For advanced usage, you can also run via npx (no installation):

npx ayb64 mcp

This will start the MCP server that exposes the ayb64 tooling to MCP clients via the standard input/output channel.

Tips and notes:

• The MCP server provides memory via a cache, job recall by ID, and change-detection checksums to optimize AI workflows.
• Tools available within the MCP server include: encode, decode, recall, jobs, datauri, and memory. These enable encoding/decoding, persisting job metadata, generating web-ready data URIs, and managing the tool cache.
• In MCP client configuration, reference the server with command ayb64 and args ["mcp"]. Example MCP client config shown in the README uses this form.
• If you prefer a binary-based run, you can use the ayb64-mcp binary directly or run via tsx in development setups.
• Ensure your environment paths include the npm global bin directory if you install ayb64 globally so the ayb64 command is discoverable from your shell.
• There are no required environment variables documented in the README; use the provided defaults unless you need to customize paths or cache limits in a larger deployment.