Skip to main content
Glama
gjermundgaraba

terminus-mcp

by gjermundgaraba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to terminus-mcp

No user-submitted related servers found.

    Related Servers

    • ELEMS MCP

      HappyLDE
      F
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP-capable agents to an authenticated ELEMS account, enabling website creation and inventory management, page and element editing, media and template handling, structured content authoring, draft previews, and explicit publishing.
      -

    • TRMNL API MCP

      renzel
      F
      license
      A
      quality
      C
      maintenance
      Enables local MCP access to read TRMNL devices and manage playlist items, visibility, ordering, and weekly display windows.
      8
      1
      -

    • @socheli/mcp

      Socheli
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-enabled agents to manage Socheli content: list, inspect, generate renders, dispatch to device fleet, publish across platforms, and curate the dated content plan via natural language.
      8 npm
      MIT

    • postifys-mcp

      mfarooqone
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to manage social media publishing, media uploads, and content queues through the Postifys API.
      17
      13 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action combination: playlists, screens, docs, and device context are clearly separated. The only potential overlap is list_playlists vs save_playlist vs assign_playlist, but their verbs (list, save, assign) make the differences explicit.

    Naming Consistency5/5

    All tool names follow the snake_case verb_noun pattern consistently (list_*, get_*, search_*, read_*, create_*, update_*, save_*, assign_*). There are no camelCase or mixed-style names, so the naming pattern is uniform and predictable.

    Tool Count5/5

    The server has 10 tools, which is within the ideal 3-15 range. Each tool serves a clear purpose in the Terminus workflow (screens, playlists, docs, device context), and no tool feels redundant.

    Completeness3/5

    The core lifecycle is covered for screens (create, update, list, get image) and playlists (save, list, assign), but there is no delete operation for either screens or playlists. Additionally, there is no way to unassign a playlist from a device or retrieve the raw HTML of a screen, which are notable gaps in the workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources