Skip to main content
Glama
eink-mcp

eink-mcp

by sberan

eink-mcp

An MCP server that hosts files for e-ink devices and syncs them down.

Agents put files here with MCP tools. Each file version lands once at an immutable, content-addressed public URL in a Vercel Blob store, and a small manifest.json maps paths to those URLs with their sha256. Only the manifest is ever overwritten, so a reader can never see a manifest that disagrees with the file it names; it can only be up to a minute behind. A device such as a jailbroken Kindle running eink-ui points its update URL at that manifest and pulls whatever changed on every start, wake and reload. Nothing has to reach the device: it is behind NAT and asleep most of the day, so it always pulls.

agent ──MCP──▶ eink-mcp ──put──▶ Vercel Blob (public URLs + manifest.json) ◀──pull── device

Tools

tool

effect

status

the public base URL to set as the device's update URL, the manifest URL, file count

list_files

every file with size, sha256, URL and last update

put_file

upload content (text) or content_base64 (binary) at a relative path

put_file_from_url

download a URL into the store, for large builds coming out of CI

get_file

read a file back (text or base64, truncated past 512 KiB)

delete_file

remove a file; devices drop their copy on the next sync

Paths are relative and map straight onto the device's app directory. On eink-ui devices app.js is the React bundle and eink-host is the host binary; changing either restarts the host.

Related MCP server: slm-mesh

Run it

Environment:

  • BLOB_READ_WRITE_TOKEN (required): a Vercel Blob read-write token. This is the only credential; the store is the only state.

  • EINK_PREFIX (default eink/): the folder inside the store, one per device or fleet.

npx eink-mcp                      # from npm, stdio
nix run github:sberan/eink-mcp    # from the flake, stdio

Claude Code

claude mcp add eink -e BLOB_READ_WRITE_TOKEN=... -- npx eink-mcp

pg_mcp (Nix runtime)

pg_mcp builds the flake at a pinned commit and runs it over stdio; the Blob token is supplied as the server's bearer credential through token_env.

SELECT mcp.register_server('eink', auth => 'bearer',
  options => '{"token_env":"BLOB_READ_WRITE_TOKEN","env":{"EINK_PREFIX":"kindle/"}}'::jsonb,
  runtime => '{"kind":"nix","source":"github:sberan/eink-mcp","revision":"<commit>",
               "attribute":"mcp","executable":"bin/eink-mcp"}'::jsonb);
-- then set the bearer token (the Blob token) and wait for mcp.status('eink').runtime = ready

Manifest

{ "version": 1, "generated": "2026-09-17T01:59:51Z",
  "base": "https://<store>.public.blob.vercel-storage.com/kindle/",
  "files": { "app.js": { "sha256": "…", "size": 123304, "url": "…", "content_type": "application/javascript", "updated": "…" } } }

A device keeps the manifest's ETag and the sha256 of each file it holds, downloads only files whose hash changed, verifies the hash (the CDN can lag a file behind its manifest for up to a minute, in which case the device simply tries again on its next sync), and deletes files that left the manifest.

Develop

npm install && npm run build
BLOB_READ_WRITE_TOKEN=... npm run smoke   # end to end against a throwaway prefix

Available Tools

6 tools
delete_fileDelete a fileA

Remove a file from the store and the manifest. Devices delete their copy on the next sync.

Inputs: path (required).

get_fileGet a 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.

Inputs: path (required).

list_filesList filesA

Every file in the store with its size, sha256, public URL and last update.

Inputs: no named parameters.

put_filePut a fileA

Upload a file by path (relative, as it will appear in the device app directory). Give text as content or binary as content_base64. Devices pick it up on their next sync.

Inputs: path (required), content, content_type, content_base64.

put_file_from_urlPut a file from a URLA

Download a URL and store it under path, so large binaries (a host build from CI, for example) never pass through the conversation.

Inputs: url (required), path (required), content_type.

statusStore statusC

The public base URL devices sync from (set it as update_url on the device), the manifest, and the file count.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Related MCP Connectors

    Related MCP Servers