Customer Dashboard Help

MCP and AI assistants

CustomerDashboard exposes a remote Model Context Protocol server. An assistant that speaks MCP can do the same work you do in the app: connect a data source, create dashboards and widgets, add customers, and publish.

The endpoint is:

https://app.customerdashboard.io/mcp

You do not create a static API token. The client starts OAuth, you sign in with the same account you use on the website (Google or email), and the assistant works inside your workspace.

Connect from ChatGPT

  1. Open ChatGPT settings and find Connectors / Apps & connectors (wording varies).
  2. Add an MCP server.
  3. URL: https://app.customerdashboard.io/mcp
  4. Leave custom headers empty.
  5. Sign in when ChatGPT opens the CustomerDashboard authorization screen.

If you have never created a workspace, finish that once on the website after sign-in. MCP does not create workspaces.

Connect from Claude or Cursor

In Cursor, add a remote server in ~/.cursor/mcp.json:

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

Other MCP hosts that support Streamable HTTP plus OAuth only need that same URL. Discovery documents are published at:

  • /.well-known/oauth-protected-resource/mcp
  • /.well-known/oauth-authorization-server

A tool call that needs an account and arrives without a token gets 401 plus a WWW-Authenticate challenge. That is what makes the host show its sign-in button.

What the assistant can do without an account

These tools are public. They describe the product so a directory listing or a first conversation is still useful:

get_platform_overview, list_supported_data_connectors, list_widget_types, list_plans_and_limits, explain_customer_filtering, get_started.

Answers come from the same connector and widget lists the app uses.

What requires your account

After you authorize, the assistant can list and edit data sources, dashboards, views, widgets, and customers, preview a query, and publish. Destructive deletes take two steps: a preview, then a confirmation that includes the resource’s exact name.

Three safety rules are stricter over MCP than in the UI:

  1. Credentials never reach the model. Passwords and service-account keys are redacted.
  2. Per-customer filtering is enforced. On a customer dashboard, saving a widget whose query omits :customer_id is rejected unless you explicitly allow a shared widget.
  3. Deletes are confirmed by name, not by a single click.