CustomerDashboard
io.customerdashboard/customerdashboard · v0.1.0
Build dashboards on your own data, including multi-customer views with per-customer login.
MCPremoteno credentialsCRM & sales
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 42 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 99/100
What it does: 42 tools · 18 read, 24 write (incl. delete/pay) · CRM & sales
Test call list_supported_data_connectors: worked (852 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +9
- Read/write annotations: +5
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://app.customerdashboard.io/mcpTools
42 tools listed at last check
get_platform_overviewExplain 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_connectorsList 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_typesList 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_limitsList 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_filteringExplain 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_startedExplain 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_accountGet 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_sourcesList every data source connected to your workspace. Connection credentials are never included.get_data_sourceGet one data source by id, including its non-secret connection settings. Credentials are never included.test_data_source_connectionCheck 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.add_data_sourceConnect 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.update_data_sourceRename 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.get_data_source_schemaList 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.run_query_previewRun 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.list_dashboardsList every dashboard in your workspace, with its type, publishing state and share URL if published.get_dashboardGet 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.create_dashboardCreate 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 dashboardupdate_dashboardRename 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.list_viewsList the views (tabs) on a dashboard, in display order, with how many widgets each one holds.create_viewAdd a view (tab) to a dashboard. New views are appended after the existing ones. Subject to your plan's view limit.update_viewRename a view. Use reorder_views to change the tab order.reorder_viewsSet 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.list_widgetsList the widgets on a view, including each widget's query and visualization configuration.create_widgetAdd 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 widgetupdate_widgetChange a widget's title, query, visualization type, configuration, data source or position. Only the fields you pass are changed.set_widget_layoutReposition 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.list_customersList the customers on a multi-customer dashboard, each with the customerId their data is filtered by and how many logins they have.add_customerAdd 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. Subjectupdate_customerRename 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.add_customer_userCreate 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.validate_customer_filteringAudit 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.set_dashboard_themeSet 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.set_dashboard_formattingSet the default locale and number, currency, percentage, duration, date and datetime formatting for a dashboard. Individual widgets can still override these.publish_dashboardPublish 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).unpublish_dashboardMake a dashboard private again. The existing share link stops working immediately, and any shared username and password are cleared. Widgets and data are untouched.get_dashboard_share_urlGet the public URL of a published dashboard, and who can open it. Returns nothing to share if the dashboard is still private.delete_dashboardPermanently 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.delete_viewPermanently delete a view and every widget on it. Calling this without confirm returns a preview. This cannot be undone.delete_widgetPermanently delete a widget. Calling this without confirm returns a preview. This cannot be undone.delete_data_sourcePermanently 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.delete_customerPermanently 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_userPermanently 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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.customerdashboard/customerdashboard)