Developers

Build dashboards from your own Claude session

Dance Party runs an MCP server. Connect Claude Code or Claude Desktop, describe a dashboard, and it deploys straight to your office screens. You build on the Claude subscription you already pay for. Nothing to install. It is a hosted server you point your client at.

Get a token

Generate a workspace access token on your API keys page. You see it once, so copy it. The token reads your connected data sources and deploys widgets into your workspace. It cannot change your integrations or reach any other workspace.

Generate a token

Connect Claude Code

Run this once, with your token in place:

claude mcp add --transport http dance-party https://app.danceparty.ai/api/mcp --header "Authorization: Bearer <your-token>"

Add --scope user to use it across every project. Confirm it connected with claude mcp list, or /mcp inside a session.

Connect Claude Desktop

Claude Desktop does not take a token in its settings yet, so use the mcp-remote bridge. Open your config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this with your token in place, then fully quit and reopen Claude Desktop. It needs Node 18 or newer.

{
  "mcpServers": {
    "dance-party": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.danceparty.ai/api/mcp",
        "--header",
        "Authorization: Bearer ${DP_TOKEN}"
      ],
      "env": { "DP_TOKEN": "<your-token>" }
    }
  }
}

Use it

From your connected session:

  1. Ask what data sources you have connected.
  2. Preview one to see real data.
  3. Describe the widget you want and have it deployed into a dashboard.

It shows up in Dance Party and on any screen running that dashboard, live on your workspace’s own connections, the same as a widget built in the app.

Good to know

  • Read-only. It reads your connected providers and deploys widgets. It never writes back to your providers.
  • Your subscription covers the building. A widget that reshapes its data on a schedule still uses your workspace model key for that refresh, so keep a provider key on the API keys page if you use those.
  • Revoke any time. Revoke a token from the API keys page and the session loses access immediately.