eink-mcp
Related Servers
Alternatives to eink-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage persistent context, send signed messages, sync with peers, and share files through plain-file-based tools.54 npm18MIT- AlicenseAqualityBmaintenancePublish pages, documents, or folders to a public link. Anonymous links last 30 days; optional account authentication enables permanent storage and updates that keep the same URL.2146 npmMIT

A2AL MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables 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
SnapHostofficial
AlicenseNot gradedqualityBmaintenanceSend a live, private link to a client from Claude. SnapHost publishes what your assistant builds as a shareable website with a stable URL, updates it in place, restricts viewers by email or password, rolls back bad versions, serves custom domains, and stores form and waitlist data with no backend.MIT- AlicenseNot gradedqualityDmaintenanceEnables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.8 npm16Elastic 2.0
- AlicenseAqualityCmaintenanceSimple and free publishing of content on the web for AI Agents29,324 npmMIT
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.