TRMNL API MCP
Related Servers
Alternatives to TRMNL API MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to control playlists, library, catalog, discovery, playback, and the Up Next queue across macOS, Windows, and Linux.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage UniFi Network, Protect, and Access through official local APIs with read-only-by-default permissions, per-client tokens, and independent human approval for high-impact changes.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to search and manage playlists, library, catalog, discovery, playback, and the Up Next queue across macOS, Windows, and Linux.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to query and manage a Qbee-managed device fleet, offering read tools for device status, files, CVEs, and changes, plus confirmation-gated write operations for configuration, file management, membership, and IAM.Apache 2.0
- AlicenseAqualityCmaintenanceEnables local stdio MCP clients to list, get, plan, and probe registered devices and their connection endpoints from a private inventory, while keeping credential references rather than secrets in agent responses.4MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: devices, playlist items, schedules, visibility, and ordering are clearly separated. The read/write schedule pair and visibility vs. removal are described with enough distinction to prevent misselection.
All tools follow a consistent snake_case verb_noun pattern using list/get/set/add/remove/reorder/replace. The naming style is uniform and the resource hierarchy is predictable.
Eight tools cover the device listing and playlist management workflows without redundancy or bloat. The count is well within the ideal range and each tool contributes a distinct playlist lifecycle operation.
The playlist item lifecycle is well covered: add, list, read schedule, update visibility, replace schedule, reorder, and remove. The main gap is that add_playlist_item requires an external plugin_setting_id with no corresponding tool to discover plugin settings, forcing agents to get that ID from outside the server.