Model Context Protocol server for Rollbar
Nothing to run from here
CustomerDashboard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
42
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Build dashboards on your own data, including multi-customer views with per-customer login.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http customerdashboard-mcp https://app.customerdashboard.io/mcp
# 2 — ask your agent for something these tools do
# get_platform_overview, list_supported_data_connectors, list_widget_types and 39 more
CustomerDashboard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CUAll 1 server
customerdashboard1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http customerdashboard-mcp https://app.customerdashboard.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
42 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
List every data source connected to your workspace. Connection credentials are never included.
No parameter schema on file.
Get one data source by id, including its non-secret connection settings. Credentials are never included.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | yes | Data source id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | no | Test a saved data source. Omit to test new settings. |
| type | string | no | Connector type. Call list_supported_data_connectors for the settings each one expects. |
| config | object | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | A name for this connection, shown in the dashboard editor. |
| type | string | yes | Connector type. Call list_supported_data_connectors for the settings each one expects. |
| config | object | yes | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | yes | Data source id. |
| name | string | no | — |
| config | object | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | yes | Data source id. |
| table | string | no | Return only this table. Useful when a database has many tables. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | yes | Data source id. |
| query | string | yes | The SQL to run, or an A1 range for Google Sheets. Use :customer_id where a customer's own identifier belongs. |
| customerId | string | no | 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 | no | A customer dashboard whose configured test customer should be used instead of a real customer. Only needed when the query uses :customer_id. |
| limit | integer | no | Rows to return. Defaults to 25. |
List every dashboard in your workspace, with its type, publishing state and share URL if published.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| includeWidgets | boolean | no | Include every widget on every view. Defaults to true. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Dashboard name. |
| type | string | no | 'customer' for a per-customer, login-gated dashboard; 'internal' for a single shared dashboard. Defaults to 'internal'. This cannot be changed later. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| name | string | no | — |
| viewRotationSeconds | no | Seconds each view is shown before rotating to the next, for wall displays. 0 or null turns rotation off. | |
| testCustomerId | no | 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. |
List the views (tabs) on a dashboard, in display order, with how many widgets each one holds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
Add a view (tab) to a dashboard. New views are appended after the existing ones. Subject to your plan's view limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| name | string | yes | View name, shown on the tab. |
Rename a view. Use reorder_views to change the tab order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| viewId | string | yes | View id. |
| name | string | yes | New view name. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| viewIds | array | yes | Every view id on this dashboard, in the order you want. |
List the widgets on a view, including each widget's query and visualization configuration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| viewId | string | yes | View id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| viewId | string | yes | View id the widget belongs to. |
| dataSourceId | string | yes | Data source the query runs against. |
| title | string | yes | Widget title. |
| query | string | yes | SQL, or an A1 range for Google Sheets. On a customer dashboard include :customer_id, for example "WHERE customer_id = :customer_id". |
| visualizationType | string | yes | — |
| visualizationConfig | object | no | Field mappings and display options for this visualization type. Call list_widget_types for the keys each type expects. |
| layout | object | no | Position and size on the 12-column grid. Omit on create and a free slot is chosen for you. |
| allowSharedAcrossAllCustomers | boolean | no | 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. |
Change a widget's title, query, visualization type, configuration, data source or position. Only the fields you pass are changed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| viewId | string | yes | View id the widget belongs to. |
| widgetId | string | yes | Widget id. |
| title | string | no | — |
| query | string | no | — |
| visualizationType | string | no | — |
| visualizationConfig | object | no | Replaces the whole configuration object, so include every key you want to keep. |
| dataSourceId | string | no | — |
| layout | object | no | Position and size on the 12-column grid. Omit on create and a free slot is chosen for you. |
| allowSharedAcrossAllCustomers | boolean | no | Only for customer dashboards. Set true, after the user explicitly confirms, to allow a query with no per-customer filter. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| viewId | string | yes | View id. |
| layouts | array | yes | The widgets to move, with their new positions. |
List the customers on a multi-customer dashboard, each with the customerId their data is filtered by and how many logins they have.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| includeUsers | boolean | no | Include each customer's login email addresses. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | A dashboard of type 'customer'. |
| name | string | yes | Display name for this customer, for your own reference. |
| customerId | string | yes | The identifier for this customer in your own data, for example the value in your orders.customer_id column. Must match exactly. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| customerRecordId | string | yes | The customer's id from list_customers (not their customerId). |
| name | string | no | — |
| customerId | string | no | New identifier from your own data. This changes which rows this customer can see. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| customerRecordId | string | yes | The customer's id from list_customers. |
| string | yes | The person's email address. Must be unique on this dashboard. | |
| password | string | no | Leave empty to have a strong password generated. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| backgroundColor | string | yes | Page background. |
| surfaceColor | string | yes | Background of each widget card. |
| primaryTextColor | string | yes | Main text. |
| secondaryTextColor | string | yes | Muted and secondary text. |
| primaryBrandColor | string | yes | Main accent, used as the first chart series colour. |
| secondaryBrandColor | string | no | Secondary accent, used for the second chart series. |
| chartSeriesColors | array | no | Explicit chart series palette. Leave empty to derive one from the brand colours. |
Set the default locale and number, currency, percentage, duration, date and datetime formatting for a dashboard. Individual widgets can still override these.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| locale | string | no | BCP 47 locale such as en-US, en-GB or de-DE. |
| nullDisplay | string | no | What to show for an empty value, for example a dash. |
| number | object | no | — |
| currency | object | no | For example { "currency": "USD", "decimals": 2 }. |
| percentage | object | no | — |
| duration | object | no | — |
| date | object | no | — |
| datetime | object | no | — |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| access | string | no | 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 |
| username | string | no | Shared username, for 'protected' access. |
| password | string | no | Shared password, for 'protected' access. Leave empty to have one generated and returned once. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
Get the public URL of a published dashboard, and who can open it. Returns nothing to share if the dashboard is still private.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
Permanently delete a view and every widget on it. Calling this without confirm returns a preview. This cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| viewId | string | yes | View id. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
Permanently delete a widget. Calling this without confirm returns a preview. This cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| viewId | string | yes | View id. |
| widgetId | string | yes | Widget id. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataSourceId | string | yes | Data source id. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| customerRecordId | string | yes | The customer's id from list_customers. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboardId | string | yes | Dashboard id. |
| customerRecordId | string | yes | The customer's id from list_customers. |
| userId | string | yes | The login's id. |
| confirm | boolean | no | 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 | no | The exact current name of the item being deleted, copied from the preview. Required alongside confirm. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CustomerDashboard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CustomerDashboard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.