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. Point your client at the hosted server and sign in — there is no token to copy or store.

Connect Claude Code

Run this once:

claude mcp add --transport http --scope user dance-party https://app.danceparty.ai/api/mcp

Your browser opens to sign in to Dance Party. Approve access and you are connected, on the workspace you sign in to. Add --scope user (shown above) to use it across every project. Confirm it connected with claude mcp list, or /mcp inside a session.

Connect Claude Desktop

Claude Desktop connects through the mcp-remote bridge, which opens the same browser sign-in. Open your config file:

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

Add this, then fully quit and reopen Claude Desktop. It needs Node 18 or newer. The first time it runs, your browser opens to sign in.

{
  "mcpServers": {
    "dance-party": {
      "command": "npx",
      "args": ["mcp-remote", "https://app.danceparty.ai/api/mcp"]
    }
  }
}

Use it

From your connected session:

Ask what data sources you have connected.
Preview one to see real data.
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.
Disconnect any time. Remove the dance-party server from your MCP client to disconnect that session.