mcpdirectory.dev
9,129 servers · updated 23 Sept

Dashboardbase MCP server

official from Dashboardbase Active last commit 50 d
{
  "mcpServers": {
    "dashboardbase": {
      "command": "npx",
      "args": [
        "-y",
        "@dashboardbase/mcp@latest"
      ],
      "env": {
        "DASHBOARDBASE_API_URL": "https://...",
        "DASHBOARDBASE_API_KEY": "<dashboardbase_api_key>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dashboardbase/mcpversion 1.0.0

What it does

This MCP server validates Dashboardbase widget endpoint responses and dashboard setup files against the live Dashboardbase contract. It is for developers building dashboards and widget endpoints who want to catch JSON validation errors before deploying to Dashboardbase.

  • Validate a widget endpoint's JSON response to ensure it matches the Dashboardbase widget contract before deployment.
  • Check a complete dashboard setup file for errors and warnings in widget definitions and datasource configuration.
  • Iterate on dashboard JSON locally with immediate validation feedback instead of discovering errors after deploying to Dashboardbase.

Tools this server exposes

ToolDoes
validate_setup_fileValidates a Dashboardbase setup file against the contract, reporting errors and warnings with field, line and column locations.
validate_widget_responseValidates a widget endpoint's JSON response against the Dashboardbase widget contract, reporting the path and message for each validation problem.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.