Skip to main content
Glama
codecube

kindle-dashboard

by codecube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to kindle-dashboard

No user-submitted related servers found.

    Related Servers

    • tesserae-mcp

      dmellok
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to build freeform dashboards for e-ink panels by listing widgets and devices, laying out a canvas, rendering a preview, and pushing to the panel.
      18
      AGPL 3.0

    • mcp-kindle

      kogecoo
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for accessing local Kindle library data, exposing tools to query profile, health, and book metadata.
      MIT

    • E-Ink MCP (墨水屏推送服务)

      three6198-lab
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables pushing text from an AI conversation to a low-cost BLE e-ink shelf label via an MCP tool, with rich-text markup, card-style letter layouts, and real-time SSE delivery to a phone control page. Also lets clients check current screen content, update time, push history, and whether a phone is online.
      -

    • paperboy

      michaelellis003
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that delivers research papers to your e-reader, using Zotero as the source of truth. Allows searching, queuing, and sending papers to Kindle, PocketBook, or Kobo.
      14
      7
      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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct, covering screen management, activation, preview, and content updates. The main ambiguity is between update_region and push_updates, but their descriptions clarify single-region vs atomic batch updates.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: update, push, render, get, list, activate, upsert. There are no mixed conventions or vague placeholder names.

    Tool Count5/5

    Seven tools is well-scoped for a Kindle dashboard server, covering screen CRUD, content updates, preview, and activation without unnecessary bloat. Each tool appears necessary to the workflow.

    Completeness4/5

    The core dashboard lifecycle is covered: create/replace screens, update regions, push updates, preview, list, and activate. A delete_screen tool is the most obvious missing operation, but it is not a blocking gap for typical dashboard management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources