Skip to main content
Glama

Related Servers

Alternatives to TRMNL Controller

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      An 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.
      1
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Local-first MCP server for repo-scoped development tasks like inspection, testing, documentation, and patching, designed to complement Cline with a structured local execution layer.
      -
    • A
      license
      A
      quality
      C
      maintenance
      A 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.
      10
      214 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A 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.
      42
      49 npm
      13
      MIT

    TDQS

    C2.9/5.0

    Scored across 199 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues