dakboard-mcp-server
Manage DAKboard digital dashboards through MCP tools covering screens, blocks, loops, devices, and custom metrics.
Test the DAKboard MCP server connection and configuration.
List, inspect, and update screens, including name, orientation, dimensions, refresh rate, and default status.
List, inspect, and update blocks on screens, including position, size, content, URL, text, z-index, and visibility.
Visualize screen block layouts as ASCII diagrams, optionally using a screen UUID for accurate rendering.
List and inspect screen loops, including screen rotation details.
List, inspect, and update devices, including name, IP address, and assigned screen.
List and inspect custom metrics with their data points.
Create metric data points with values and optional timestamps/expiration.
Delete metrics and delete metric data points at a specific timestamp.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dakboard-mcp-server list all my screens"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DAKboard MCP Server
A Model Context Protocol (MCP) server for managing DAKboard digital dashboards - screens, blocks, devices, loops, and metrics.
Quick Start
Option 1: NPX (No install required)
DAKBOARD_API_KEY=your_api_key npx dakboard-mcp-serverOr add to your MCP config (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"dakboard": {
"command": "npx",
"args": ["dakboard-mcp-server"],
"env": {
"DAKBOARD_API_KEY": "your_api_key"
}
}
}
}Option 2: Claude Code
claude mcp add --transport stdio dakboard -- npx dakboard-mcp-serverThen set the environment variable in your shell before launching Claude Code:
export DAKBOARD_API_KEY=your_api_keyRelated MCP server: Boardstate MCP Server
Tools
Screens
Tool | Description |
| List all DAKboard screens |
| Get detailed screen information including settings |
| Update screen settings (name, orientation, dimensions, refresh rate) |
Blocks
Tool | Description |
| List all blocks on a screen |
| Get detailed block information |
| Update block position, size, content, and visibility |
| Visualize spatial layout as ASCII diagram (provide screen_uuid for accurate layout) |
Loops
Tool | Description |
| List all screen loops |
| Get loop details including screen rotation |
Devices
Tool | Description |
| List all DAKboard devices |
| Get detailed device information |
| Update device settings (name, IP address, assigned screen) |
Metrics
Tool | Description |
| List all custom metrics |
| Get a metric with its data points |
| Create data points for a metric |
| Delete a metric and all its data points |
| Delete data points at a specific timestamp |
Utility
Tool | Description |
| Test server connection and configuration |
Configuration
Environment Variables
Variable | Required | Default | Description |
| Yes | - | Your DAKboard API key |
| No |
| Transport mode: |
| No |
| Port for HTTP server mode |
| No |
| Host for HTTP server mode |
Getting Your API Key
Log in to DAKboard
Go to Settings > API
Copy your API key
Development
Commands
pnpm install # Install dependencies
pnpm build # Build TypeScript
pnpm dev # Build with watch mode
pnpm test # Run tests
pnpm lint # Lint code
pnpm format # Format code
pnpm validate # Format + lint + test + build (pre-commit check)
pnpm run ci # validate's checks without fixing, as CI runs them (type `run`: `pnpm ci` is a clean install)
pnpm inspect # Build and launch MCP InspectorCLI Options
npx dakboard-mcp-server --version # Show version
npx dakboard-mcp-server --help # Show helpHTTP Server Mode
For web-based clients, use HTTP transport:
DAKBOARD_API_KEY=your_api_key TRANSPORT_TYPE=httpStream PORT=3000 node dist/index.jsThe server will be available at http://127.0.0.1:3000/mcp.
Architecture
Built with:
FastMCP - MCP server framework
Zod - Schema validation for tool parameters
functype - Functional programming (Either for errors, Branded types for IDs)
ts-builds - Standardized TypeScript build toolchain
License
MIT
Available Tools
18 toolscreate_metric_data_pointsA
Create data points for a DAKboard metric. Send an array of values with optional timestamps.
Inputs: data_points (required), metric_name (required).
delete_metricA
Delete a DAKboard metric and all its data points. WARNING: This cannot be undone.
Inputs: metric_name (required).
delete_metric_data_pointsA
Delete data points from a DAKboard metric at a specific timestamp
Inputs: timestamp (required), metric_name (required).
get_blockB
Get detailed information about a specific block on a DAKboard screen
Inputs: block_id (required), screen_id (required).
get_deviceB
Get detailed information about a specific DAKboard device
Inputs: device_id (required).
get_loopA
Get detailed information about a DAKboard screen loop including its screen rotation
Inputs: loop_id (required).
get_metricB
Get a DAKboard metric with its data points
Inputs: metric_name (required).
get_screenA
Get detailed information about a specific DAKboard screen including settings
Inputs: screen_id (required).
list_blocksA
List all blocks on a DAKboard screen
Inputs: screen_id (required).
list_devicesA
List all DAKboard devices
Inputs: no named parameters.
list_loopsB
List all DAKboard screen loops
Inputs: no named parameters.
list_metricsA
List all DAKboard custom metrics
Inputs: no named parameters.
list_screensB
List all DAKboard screens
Inputs: no named parameters.
test_dakboard_connectionA
Test the DAKboard MCP Server connection and configuration
Inputs: no named parameters.
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.
Inputs: block_id (required), screen_id (required), h, w, +7 more.
update_deviceA
Update a DAKboard device's settings (name, IP address, assigned screen)
Inputs: device_id (required), name, ip_addr, screen_id.
update_screenA
Update a DAKboard screen's settings (name, orientation, dimensions, refresh rate)
Inputs: screen_id (required), name, width, height, +3 more.
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.
Inputs: screen_id (required), screen_uuid.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Dashboards as data. Author, validate, render, and share dvt dashboards from any MCP client.
Manage Timequip projects, tasks, comments, members, and dashboards through MCP.
Manage uptime monitors, incidents and status pages from any MCP client.
Manage FeatureOS feedback boards, roadmaps, changelogs and help-center articles from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to compose and edit dashboards through MCP tools, allowing them to manage tabs, widgets, layout, and data bindings via a unified control plane.20MIT
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools for Cisco Meraki Dashboard API, enabling management of networks, configuration templates, and health checks via natural language commands.-
- AlicenseNot gradedqualityBmaintenanceEnables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.MIT