dakboard-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host for HTTP server mode | 127.0.0.1 |
| PORT | No | Port for HTTP server mode | 3000 |
| TRANSPORT_TYPE | No | Transport mode: stdio or httpStream | stdio |
| DAKBOARD_API_KEY | Yes | Your DAKboard API key |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test_dakboard_connectionA | Test the DAKboard MCP Server connection and configuration |
| list_screensB | List all DAKboard screens |
| get_screenA | Get detailed information about a specific DAKboard screen including settings |
| update_screenA | Update a DAKboard screen's settings (name, orientation, dimensions, refresh rate) |
| list_blocksA | List all blocks on a DAKboard screen |
| get_blockB | Get detailed information about a specific block on a DAKboard screen |
| update_blockA | Update a block on a DAKboard screen (position, size, content, visibility). IMPORTANT: DAKboard uses non-linear per-block coordinate scaling. The API coordinate values (x, y, w, h) do NOT map 1:1 to screen pixels, and updating a block changes its scaling factor permanently. Use rendered pixel values at 1920x1080 design resolution as coordinate values. Use visualize_screen_layout with screen_uuid first to see the actual layout before making changes. |
| visualize_screen_layoutA | Visualize the spatial layout of blocks on a DAKboard screen as an ASCII diagram. Provide screen_uuid for accurate CSS-based rendering (from the public screen URL), otherwise falls back to API coordinates. |
| list_loopsB | List all DAKboard screen loops |
| get_loopA | Get detailed information about a DAKboard screen loop including its screen rotation |
| list_devicesA | List all DAKboard devices |
| get_deviceB | Get detailed information about a specific DAKboard device |
| update_deviceA | Update a DAKboard device's settings (name, IP address, assigned screen) |
| list_metricsA | List all DAKboard custom metrics |
| get_metricB | Get a DAKboard metric with its data points |
| create_metric_data_pointsA | Create data points for a DAKboard metric. Send an array of values with optional timestamps. |
| delete_metricA | Delete a DAKboard metric and all its data points. WARNING: This cannot be undone. |
| delete_metric_data_pointsA | Delete data points from a DAKboard metric at a specific timestamp |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action: list/get/update for screens, blocks, devices, and loops, plus metric-specific operations. The visual layout and connection test tools are clearly separate. No two tools appear to do the same thing.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_screens, get_block, update_device, create_metric_data_points). The naming is uniform and predictable across all resources.
18 tools is slightly above the ideal range but justified by the multiple resource types (screens, blocks, loops, devices, metrics) and auxiliary operations like visualization and connection testing. It is not excessive and each tool has a clear role.
The surface has significant gaps: there are no create operations for screens, blocks, loops, or devices, and no delete operations for screens, blocks, loops, or devices. Metrics have delete and data-point management but lack a create_metric tool, leaving no way to create a metric initially.