mcp-base64
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| encode_file_to_base64A | Encode a file to a base64 string. This tool reads a file in binary mode and returns its contents encoded as a base64 string. Only absolute paths are allowed for security reasons. |
| decode_base64_to_fileA | Decode a base64 string and write it to a file. This tool takes base64 encoded content and writes the decoded binary data to a file. Only absolute paths are allowed for security reasons. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are exact opposites with non-overlapping purposes: one encodes a file to base64, the other decodes base64 to a file. There is no ambiguity about which tool to select for a given direction.
Both names follow the same verb_object_preposition_object pattern: encode_file_to_base64 and decode_base64_to_file. The naming is symmetric, predictable, and clearly indicates the input and output of each operation.
Two tools is exactly the right scope for a focused base64 file conversion server. Each tool earns its place, and adding more tools would likely introduce redundancy or scope creep.
The server fully covers its stated domain: converting between file contents and base64 strings in both directions. There are no obvious missing operations for a file-based base64 utility.