TRMNL Controller
Related Servers
Alternatives to TRMNL Controller
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server that enables programmatic management and monitoring of development servers through a unified interface and interactive TUI. It provides tools for process control, log streaming, and experimental browser automation via Playwright.1MIT
- AlicenseNot gradedqualityBmaintenanceA full-featured MCP server for local development with filesystem, shell, editor, session persistence, and security features.2MIT
- AlicenseAqualityAmaintenanceA local, read-only MCP server that deterministically validates rights-aware production metadata manifests before delivery or release.1MIT
- -licenseNot gradedqualityNot gradedmaintenanceLocal-first MCP server for repo-scoped development tasks like inspection, testing, documentation, and patching, designed to complement Cline with a structured local execution layer.-
- AlicenseAqualityCmaintenanceA local MCP server that reads and edits a Figma Design file through a development plugin, creating real editable layers (frames, text, shapes, components, images) rather than flattened screenshots. It runs entirely on loopback with no personal access token, API key, or cloud bridge, letting an agent inspect documents, build and update layers, export previews, and wire up prototype navigation.10214 npm1MIT
- AlicenseAqualityDmaintenanceA lightweight, local-first MCP server for executing HTTP requests and managing API collections and environments without cloud dependencies. It enables testing APIs, handling authentication, and importing OpenAPI specifications directly within MCP-compatible workflows.4249 npm13MIT
TDQS
Scored across 199 tools
The set covers many distinct domains, but within plugin settings, installations, connections, playlists, devices, fleets, and room booking there are numerous sibling tools with subtly different scopes. Names help, but an agent can easily confuse configuration vs. installation configuration vs. connection attempts, or public vs. owner booking operations.
Almost all tools use a consistent trmnl_ prefix and snake_case verb_noun structure, which is readable and predictable. Minor deviations exist in compound resource phrases such as plugin_settings vs. plugin_setting and in some noun-heavy names, but the overall convention is stable.
199 tools is far beyond a well-scoped MCP surface and is overwhelming for agent selection. Even if each maps to a real API operation, the count creates a massive selection and cognitive-load problem.
The surface is extremely comprehensive, covering devices, playlists, plugin settings, installations, recipes, room booking, fleets, auth, local projects, pipelines, and documentation. It provides CRUD and lifecycle coverage across nearly every apparent TRMNL domain.