# CustomerDashboard (remote · app.customerdashboard.io)

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

- Trust score: 88/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.customerdashboard.io`: 88/100 (this document), [markdown](https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app.md), [page](https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app)

## Channel facts

- Endpoint: `https://app.customerdashboard.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 4255 tokens (~101/item across 42 items; 42 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CustomerDashboard MCP server?

CustomerDashboard is a hosted endpoint at https://app.customerdashboard.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "io-customerdashboard-customerdashboard": {
      "type": "http",
      "url": "https://app.customerdashboard.io/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-customerdashboard-customerdashboard": {
      "type": "remote",
      "url": "https://app.customerdashboard.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-customerdashboard-customerdashboard --url 'https://app.customerdashboard.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-customerdashboard-customerdashboard:
    url: "https://app.customerdashboard.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-customerdashboard-customerdashboard": {
      "Transport": "http",
      "Url": "https://app.customerdashboard.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-customerdashboard-customerdashboard -t streamable-http -u 'https://app.customerdashboard.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-customerdashboard-customerdashboard": {
      "type": "http",
      "url": "https://app.customerdashboard.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 81, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (42)

### `get_platform_overview` (~55 tokens)

About CustomerDashboard

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.

### `list_supported_data_connectors` (~48 tokens)

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.

### `list_widget_types` (~46 tokens)

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.

### `list_plans_and_limits` (~44 tokens)

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.

### `explain_customer_filtering` (~51 tokens)

Explain per-customer data 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.

### `get_started` (~47 tokens)

How to 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.

### `get_account` (~54 tokens)

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.

### `list_data_sources` (~24 tokens)

List data sources

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

### `get_data_source` (~40 tokens)

Get data source

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

Input parameters:

- `dataSourceId` (string, required): Data source id.

### `test_data_source_connection` (~135 tokens)

Test a 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.

Input parameters:

- `config` (object): Connection settings for this connector type, for example { host, port, database, username, password, ssl } for postgres. Credentials are stored encrypted at rest and are never returned by read tools.
- `dataSourceId` (string): Test a saved data source. Omit to test new settings.
- `type` (string): Connector type. Call list_supported_data_connectors for the settings each one expects.

### `add_data_source` (~133 tokens)

Add a 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.

Input parameters:

- `config` (object, required): Connection settings for this connector type, for example { host, port, database, username, password, ssl } for postgres. Credentials are stored encrypted at rest and are never returned by read tools.
- `name` (string, required): A name for this connection, shown in the dashboard editor.
- `type` (string, required): Connector type. Call list_supported_data_connectors for the settings each one expects.

### `update_data_source` (~104 tokens)

Update a 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.

Input parameters:

- `config` (object): Connection settings for this connector type, for example { host, port, database, username, password, ssl } for postgres. Credentials are stored encrypted at rest and are never returned by read tools.
- `dataSourceId` (string, required): Data source id.
- `name` (string)

### `get_data_source_schema` (~82 tokens)

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.

Input parameters:

- `dataSourceId` (string, required): Data source id.
- `table` (string): Return only this table. Useful when a database has many tables.

### `run_query_preview` (~199 tokens)

Preview a query

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.

Input parameters:

- `customerId` (string): The id of a customer (from list_customers) to run the query as. Required when the query uses :customer_id, unless dashboardId is given.
- `dashboardId` (string): A customer dashboard whose configured test customer should be used instead of a real customer. Only needed when the query uses :customer_id.
- `dataSourceId` (string, required): Data source id.
- `limit` (integer): Rows to return. Defaults to 25.
- `query` (string, required): The SQL to run, or an A1 range for Google Sheets. Use :customer_id where a customer's own identifier belongs.

### `list_dashboards` (~28 tokens)

List dashboards

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

### `get_dashboard` (~78 tokens)

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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `includeWidgets` (boolean): Include every widget on every view. Defaults to true.

### `create_dashboard` (~121 tokens)

Create a 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.

Input parameters:

- `name` (string, required): Dashboard name.
- `type` (string): 'customer' for a per-customer, login-gated dashboard; 'internal' for a single shared dashboard. Defaults to 'internal'. This cannot be changed later.

### `update_dashboard` (~136 tokens)

Update a 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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `name` (string)
- `testCustomerId`: A customer identifier from your own data, used to preview a customer dashboard before real customers exist. This is bound to :customer_id during previews only.
- `viewRotationSeconds`: Seconds each view is shown before rotating to the next, for wall displays. 0 or null turns rotation off.

### `list_views` (~40 tokens)

List views

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

Input parameters:

- `dashboardId` (string, required): Dashboard id.

### `create_view` (~59 tokens)

Create a view

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

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `name` (string, required): View name, shown on the tab.

### `update_view` (~51 tokens)

Rename a view

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

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `name` (string, required): New view name.
- `viewId` (string, required): View id.

### `reorder_views` (~73 tokens)

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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `viewIds` (array, required): Every view id on this dashboard, in the order you want.

### `list_widgets` (~34 tokens)

List widgets

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

Input parameters:

- `viewId` (string, required): View id.

### `create_widget` (~253 tokens)

Create a 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.

Input parameters:

- `allowSharedAcrossAllCustomers` (boolean): Only for customer dashboards. Set true, after the user explicitly confirms, to allow a query with no per-customer filter so every customer sees identical rows.
- `dataSourceId` (string, required): Data source the query runs against.
- `layout` (object): Position and size on the 12-column grid. Omit on create and a free slot is chosen for you.
- `query` (string, required): SQL, or an A1 range for Google Sheets. On a customer dashboard include :customer_id, for example "WHERE customer_id = :customer_id".
- `title` (string, required): Widget title.
- `viewId` (string, required): View id the widget belongs to.
- `visualizationConfig` (object): Field mappings and display options for this visualization type. Call list_widget_types for the keys each type expects.
- `visualizationType` (string, required)

### `update_widget` (~176 tokens)

Update a widget

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

Input parameters:

- `allowSharedAcrossAllCustomers` (boolean): Only for customer dashboards. Set true, after the user explicitly confirms, to allow a query with no per-customer filter.
- `dataSourceId` (string)
- `layout` (object): Position and size on the 12-column grid. Omit on create and a free slot is chosen for you.
- `query` (string)
- `title` (string)
- `viewId` (string, required): View id the widget belongs to.
- `visualizationConfig` (object): Replaces the whole configuration object, so include every key you want to keep.
- `visualizationType` (string)
- `widgetId` (string, required): Widget id.

### `set_widget_layout` (~69 tokens)

Arrange widgets

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.

Input parameters:

- `layouts` (array, required): The widgets to move, with their new positions.
- `viewId` (string, required): View id.

### `list_customers` (~61 tokens)

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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.
- `includeUsers` (boolean): Include each customer's login email addresses.

### `add_customer` (~138 tokens)

Add a 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.

Input parameters:

- `customerId` (string, required): The identifier for this customer in your own data, for example the value in your orders.customer_id column. Must match exactly.
- `dashboardId` (string, required): A dashboard of type 'customer'.
- `name` (string, required): Display name for this customer, for your own reference.

### `update_customer` (~103 tokens)

Update a 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.

Input parameters:

- `customerId` (string): New identifier from your own data. This changes which rows this customer can see.
- `customerRecordId` (string, required): The customer's id from list_customers (not their customerId).
- `dashboardId` (string, required): Dashboard id.
- `name` (string)

### `add_customer_user` (~118 tokens)

Add a customer login

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.

Input parameters:

- `customerRecordId` (string, required): The customer's id from list_customers.
- `dashboardId` (string, required): Dashboard id.
- `email` (string, required): The person's email address. Must be unique on this dashboard.
- `password` (string): Leave empty to have a strong password generated.

### `validate_customer_filtering` (~56 tokens)

Check per-customer data isolation

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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.

### `set_dashboard_theme` (~170 tokens)

Set dashboard colours

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.

Input parameters:

- `backgroundColor` (string, required): Page background.
- `chartSeriesColors` (array): Explicit chart series palette. Leave empty to derive one from the brand colours.
- `dashboardId` (string, required): Dashboard id.
- `primaryBrandColor` (string, required): Main accent, used as the first chart series colour.
- `primaryTextColor` (string, required): Main text.
- `secondaryBrandColor` (string): Secondary accent, used for the second chart series.
- `secondaryTextColor` (string, required): Muted and secondary text.
- `surfaceColor` (string, required): Background of each widget card.

### `set_dashboard_formatting` (~149 tokens)

Set number and date formatting

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

Input parameters:

- `currency` (object): For example { "currency": "USD", "decimals": 2 }.
- `dashboardId` (string, required): Dashboard id.
- `date` (object)
- `datetime` (object)
- `duration` (object)
- `locale` (string): BCP 47 locale such as en-US, en-GB or de-DE.
- `nullDisplay` (string): What to show for an empty value, for example a dash.
- `number` (object)
- `percentage` (object)

### `publish_dashboard` (~165 tokens)

Publish a 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).

Input parameters:

- `access` (string): For internal dashboards: 'public' means anyone with the link, 'protected' requires a shared username and password. Ignored for customer dashboards, which always require a per-customer login. Defaults…
- `dashboardId` (string, required): Dashboard id.
- `password` (string): Shared password, for 'protected' access. Leave empty to have one generated and returned once.
- `username` (string): Shared username, for 'protected' access.

### `unpublish_dashboard` (~48 tokens)

Unpublish a 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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.

### `get_dashboard_share_url` (~46 tokens)

Get 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.

Input parameters:

- `dashboardId` (string, required): Dashboard id.

### `delete_dashboard` (~117 tokens)

Delete a 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.

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `dashboardId` (string, required): Dashboard id.

### `delete_view` (~111 tokens)

Delete a view

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

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `dashboardId` (string, required): Dashboard id.
- `viewId` (string, required): View id.

### `delete_widget` (~106 tokens)

Delete a widget

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

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `viewId` (string, required): View id.
- `widgetId` (string, required): Widget id.

### `delete_data_source` (~118 tokens)

Delete a 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.

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `dataSourceId` (string, required): Data source id.

### `delete_customer` (~131 tokens)

Delete a 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.

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `customerRecordId` (string, required): The customer's id from list_customers.
- `dashboardId` (string, required): Dashboard id.

### `delete_customer_user` (~140 tokens)

Delete a customer login

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.

Input parameters:

- `confirm` (boolean): Set to true only after the user has seen what will be deleted and explicitly agreed. Calling without it returns a preview instead of deleting.
- `confirmName` (string): The exact current name of the item being deleted, copied from the preview. Required alongside confirm.
- `customerRecordId` (string, required): The customer's id from list_customers.
- `dashboardId` (string, required): Dashboard id.
- `userId` (string, required): The login's id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app#diagnostics

## Score history

- 2026-09-20: 88
- 2026-09-19: 88
- 2026-09-18: 87
- 2026-09-17: 87
- 2026-09-16: 86
- 2026-09-15: 86
- 2026-09-14: 85
- 2026-09-13: 85
- 2026-09-12: 84
- 2026-09-11: 84
- 2026-09-10: 84
- 2026-09-09: 83
- 2026-09-08: 83
- 2026-09-07: 82
- 2026-09-06: 82
- 2026-09-05: 81
- 2026-09-04: 81

## Common questions

### What is the CustomerDashboard MCP server?

CustomerDashboard is an MCP server listed in the public MCP registry as io.customerdashboard/customerdashboard. Build dashboards on your own data, including multi-customer views with per-customer login. This page covers its hosted endpoint (https://app.customerdashboard.io/mcp).

### Is the CustomerDashboard MCP server safe to use?

CustomerDashboard scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CustomerDashboard MCP server expose?

CustomerDashboard exposes 42 tools: get_platform_overview, list_supported_data_connectors, list_widget_types, list_plans_and_limits, explain_customer_filtering, and 37 more. Their descriptions and schemas cost roughly 3,957 tokens of context every time the server is loaded.

### Does the CustomerDashboard MCP server require authentication?

Yes. CustomerDashboard asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the CustomerDashboard MCP server still maintained?

CustomerDashboard is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.customerdashboard.io/mcp
- Website: https://customerdashboard.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app.json
- HTML version of this page: https://verifymcp.io/servers/io-customerdashboard-customerdashboard/app