kindle-dashboard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KINDLE_DASHBOARD_STATE | No | Override the default state file path. Defaults to ~/.local/state/kindle-mcp-dashboard/dashboard.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dashboardB | Return the complete dashboard configuration and current content. |
| list_screensA | List screens, their names, region IDs, and which screen is active. |
| activate_screenB | Make a configured screen visible on the Kindle. |
| upsert_screenB | Create or replace a screen. Region coordinates use a normalized 1000x1000 canvas. |
| update_regionC | Update region content such as value, label, items, status, icon, unit, size or invert. |
| push_updatesB | Atomically apply content updates. Each item needs region_id and fields. |
| render_previewA | Render the current screen to a 758x1024 PNG and return its absolute path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| dashboard_resource | Current dashboard state as JSON. |
TDQS
Scored across 7 tools
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.
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.
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.
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.