eink-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EINK_PREFIX | No | The folder inside the store, one per device or fleet. Defaults to 'eink/'. | eink/ |
| BLOB_READ_WRITE_TOKEN | Yes | A Vercel Blob read-write token. This is the only credential; the store is the only state. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusC | The public base URL devices sync from (set it as update_url on the device), the manifest, and the file count. |
| list_filesA | Every file in the store with its size, sha256, public URL and last update. |
| put_fileA | Upload a file by path (relative, as it will appear in the device app directory). Give text as |
| put_file_from_urlA | Download a URL and store it under |
| get_fileA | Read a file back: text for text types, base64 otherwise. Large files are truncated; use the URL from list_files for the whole thing. |
| delete_fileA | Remove a file from the store and the manifest. Devices delete their copy on the next sync. |
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 6 tools
Each tool targets a distinct operation: status reports server-level info, list_files enumerates metadata, put_file and put_file_from_url are clearly separated by input source, get_file retrieves content, and delete_file removes files. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tools follow a consistent verb_noun pattern: list_files, put_file, get_file, delete_file, and put_file_from_url extends that pattern naturally. The single outlier is status, which is a noun rather than verb_noun, but it is a conventional command name and not confusing.
Six tools is well-scoped for a file store sync server. Each tool covers a necessary operation without redundancy, and the count is neither too thin nor too heavy for the stated purpose.
The tool surface covers the full file lifecycle: create/update via put_file and put_file_from_url, read via get_file and list_files, delete via delete_file, plus status for device sync configuration. There are no obvious missing operations for the domain.