eink-mcp
Related Servers
Alternatives to eink-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage persistent context, send signed messages, sync with peers, and share files through plain-file-based tools.20 npm18MIT- AlicenseAqualityAmaintenanceEnables AI agents to publish HTML pages, files, or directories as public permanent links, with optional token-based updates to keep the same URL.420MIT

A2AL MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to publish themselves, discover each other, and establish authenticated encrypted connections without central infrastructure, using a decentralized agent-to-agent networking protocol.1Mozilla Public 2.0- AlicenseNot gradedqualityCmaintenanceEnables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.49 npm19Elastic 2.0
- AlicenseAqualityAmaintenanceSimple and free publishing of content on the web for AI Agents25,766 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to self-host static websites by creating projects, editing files, previewing drafts, and publishing versioned releases with custom domains and a web dashboard.MIT
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.