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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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 have clearly distinct purposes: one decodes base64 to a file, the other encodes a file to base64. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern with clear prepositions ('decode_base64_to_file', 'encode_file_to_base64'), making them predictable and easy to understand.
With exactly two tools, the server is well-scoped for its purpose of base64 file encoding and decoding. Each tool serves a necessary and complementary role.
The server covers the full domain of file-based base64 operations: both encoding (file to base64) and decoding (base64 to file). No obvious gaps are present.