CustomerDashboard MCP Server

by customerdashboard Your server? Claim it

answering

CustomerDashboard is answering right now. Last checked 15 min ago. It exposes 42 tools.

Build dashboards on your own data, including multi-customer views with per-customer login.

Uptime history 15 days of history

15 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

214 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check CustomerDashboard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add customerdashboard --transport http https://app.customerdashboard.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "customerdashboard": {
      "url": "https://app.customerdashboard.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.customerdashboard]
url = "https://app.customerdashboard.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "customerdashboard": {
      "url": "https://app.customerdashboard.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "customerdashboard": {
      "url": "https://app.customerdashboard.io/mcp"
    }
  }
}

Available tools 42

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dashboard

create_dashboard

Create a dashboard. Use type 'customer' for a multi-customer dashboard where each of your customers signs in and sees only their own rows, or 'internal' for a normal dashboard you view yourself or publish as one shared view. A 'Default' view is created automatically. Subject to your plan's dashboard limit.

delete_dashboard

Permanently delete a dashboard and everything on it. Calling this without confirm returns a preview of what would be removed; deleting for real needs confirm plus the dashboard's exact name. This cannot be undone.

get_dashboard

Get one dashboard in full: its settings, theme, publishing state, every view, and every widget on each view including the widget queries. This is the fastest way to understand an existing dashboard before changing it.

get_dashboard_share_url

Get the public URL of a published dashboard, and who can open it. Returns nothing to share if the dashboard is still private.

set_dashboard_formatting

Set the default locale and number, currency, percentage, duration, date and datetime formatting for a dashboard. Individual widgets can still override these.

set_dashboard_theme

Set the colour theme of a dashboard: page and surface backgrounds, text colours, brand colours and the chart series palette. All colours are hex values. Pass every field, since the theme is stored as one object.

update_dashboard

Rename a dashboard, set how long each view is shown when the dashboard auto-rotates on a screen, or set the test customer used to preview a customer dashboard. Use set_dashboard_theme for colours and publish_dashboard for sharing.

data

add_data_source

Connect a new database or spreadsheet to your workspace. Test the settings with test_data_source_connection first: this tool saves them whether or not they work. Subject to your plan's data source limit.

delete_data_source

Permanently delete a data source connection. This is refused while any widget still uses it. Calling this without confirm returns a preview. Your actual database is untouched; only the connection is removed.

get_data_source

Get one data source by id, including its non-secret connection settings. Credentials are never included.

get_data_source_schema

List the tables and columns available in a connected data source, so you can write correct widget queries. Supported for PostgreSQL, MySQL, SQL Server, Oracle, Aurora, Redshift and Google Sheets.

list_data_sources

List every data source connected to your workspace. Connection credentials are never included.

update_data_source

Rename a data source or replace its connection settings. The config you pass replaces the stored one entirely, so include every setting, not just the changed ones.

customer

add_customer

Add one of your customers to a multi-customer dashboard. The customerId must exactly match the value that identifies them in your own database, because it is what gets bound to :customer_id in every widget query. Adding a customer does not give anyone access; use add_customer_user for that. Subject to your plan's customer limit.

add_customer_user

Create a login for one of your customers so they can sign in to the published dashboard and see their own data. If you do not supply a password a strong one is generated and returned once. Subject to your plan's users-per-customer limit.

delete_customer

Permanently remove a customer from a multi-customer dashboard, along with all of their logins. They lose access immediately. Calling this without confirm returns a preview. This cannot be undone.

delete_customer_user

Permanently remove one login from a customer. They can no longer sign in. Calling this without confirm returns a preview. The customer itself and their data access rule remain.

update_customer

Rename a customer or correct the customerId their data is filtered by. Changing customerId immediately changes which rows they see, so confirm the new value with the user first.

widget

create_widget

Add a chart, table or KPI to a view. Call list_widget_types for the visualizationConfig each type needs, and run_query_preview first to confirm the query returns the columns you are about to reference. On a multi-customer dashboard the query must filter on :customer_id. Subject to your plan's widget limit.

delete_widget

Permanently delete a widget. Calling this without confirm returns a preview. This cannot be undone.

list_widget_types

List every visualization a widget can use, with the visualizationConfig keys each type requires and accepts. Call this before creating widgets so the configuration is correct first time. No sign-in required.

set_widget_layout

Reposition several widgets on a view at once, on the 12-column grid. Use this to lay out a whole view rather than moving widgets one at a time.

update_widget

Change a widget's title, query, visualization type, configuration, data source or position. Only the fields you pass are changed.

view

create_view

Add a view (tab) to a dashboard. New views are appended after the existing ones. Subject to your plan's view limit.

delete_view

Permanently delete a view and every widget on it. Calling this without confirm returns a preview. This cannot be undone.

update_view

Rename a view. Use reorder_views to change the tab order.

account

get_account

Get the signed-in CustomerDashboard account: name, email, workspace, current plan, what the plan allows and how much of it is already used. Call this first in an authenticated session to learn the workspace you are working in.

customers

list_customers

List the customers on a multi-customer dashboard, each with the customerId their data is filtered by and how many logins they have.

dashboards

list_dashboards

List every dashboard in your workspace, with its type, publishing state and share URL if published.

explain

explain_customer_filtering

Explain exactly how to write widget queries so each customer only sees their own rows on a multi-customer dashboard. Call this before writing any query for a `customer` type dashboard. No sign-in required.

plans

list_plans_and_limits

List CustomerDashboard's subscription plans, their monthly price and the resource limits each one allows. Useful for explaining why a create operation was blocked. No sign-in required.

platform

get_platform_overview

Explain what CustomerDashboard.io is, how multi-customer dashboards work, and how workspaces, dashboards, views, widgets and customers fit together. Call this first when you are unfamiliar with the product. No sign-in required.

preview

run_query_preview

Run a query against a connected data source and return the first few rows, so you can confirm it works before putting it on a widget. Results are capped at 100 rows. If the query contains :customer_id you must also say which customer to preview as, using customerId or dashboardId.

publish

publish_dashboard

Publish a dashboard and return its share URL. A customer dashboard is always login-gated, so its customers sign in with the logins you created. An internal dashboard can be published as 'public' (anyone with the link) or 'protected' (one shared username and password).

reorder

reorder_views

Set the tab order of a dashboard's views. Pass every view id in the order you want them shown. This is also the order they rotate in on a wall display.

started

get_started

Explain how to sign up for the free trial and connect this MCP server to a CustomerDashboard account, plus the order of steps for building a first multi-customer dashboard. No sign-in required.

supported

list_supported_data_connectors

List every data source type CustomerDashboard can connect to, the settings each one needs, whether widgets can query it, and whether its schema can be introspected. No sign-in required.

test

test_data_source_connection

Check whether a set of connection settings actually works, before saving them. Pass an existing dataSourceId to retest a saved connection, or a type and config to test new settings.

unpublish

unpublish_dashboard

Make a dashboard private again. The existing share link stops working immediately, and any shared username and password are cleared. Widgets and data are untouched.

validate

validate_customer_filtering

Audit a multi-customer dashboard and report any widget whose query would show the same rows to every customer. Run this before publishing a customer dashboard, and any time its queries change.

views

list_views

List the views (tabs) on a dashboard, in display order, with how many widgets each one holds.

widgets

list_widgets

List the widgets on a view, including each widget's query and visualization configuration.

Endpoints

URL	Transport	State	Latency	Checked
https://app.customerdashboard.io/mcp	streamable-http	answering	151 ms	15 min ago

Alternatives to CustomerDashboard

same job, measured the same way

Dryos Workspace

by dryos

Build live US power market dashboards in your own Dryos workspace. Sign-in required.

answering

HomeLab Monitor

by sikamikanikobg

Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).

local only

Infrapage

by infra

Read-only access to your Infrapage dashboards: pages, widgets, live values, weekly recaps.

answering

Logicmonitor

by ryanmat

LogicMonitor API integration with 167 tools for alerts, devices, dashboards, and more.

551 installs/wk local only

mcp-server-sigma

by christianclaudio

MCP server for Sigma Computing. Provision dashboards, build models, and automate cloud analytics.

862 installs/wk local only

Zoogent

by bepunk

AI agent orchestrator with Architect AI. Multi-team, web dashboard, 35+ MCP tools.

55 installs/wk local only

jobctl

by dmytrorybka

Job application tracker for developers - AI agents write over MCP, you review in a dashboard.

11 tools answering

Lastsaas

by jonradoff

Read-only admin MCP server for LastSaaS — dashboards, users, tenants, billing, logs, health.

local only

CustomerDashboard — questions

Answers built from our own checks of this server.

What can CustomerDashboard do?

It exposes 42 tools, read directly from the server on our last check. Among them: add_customer, add_customer_user, add_data_source, create_dashboard, create_view, create_widget and 36 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is CustomerDashboard mostly used for?

Its tools cluster around dashboard, data and customer. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is CustomerDashboard working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 214 ms. The bar chart above shows every period we have measured.

How do I connect CustomerDashboard?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does CustomerDashboard need an API key?

No. CustomerDashboard completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 42 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is CustomerDashboard?

It answers our handshake in 214 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.