Developers

Build dashboards from your own AI assistant

Dance Party runs an MCP server, so you can build office dashboards from the AI assistant you already use. Describe a dashboard and it deploys straight to your office screens. Claude users can add it from Claude’s Connectors Directory. You sign in once. There is no token to copy or store.

Connect in Claude

This works on claude.ai and in the Claude desktop app.

  1. Open the Dance Party listing in Claude’s Connectors Directory and add it.
  2. Claude opens the Dance Party sign-in. Sign in, approve access, and you are connected to the workspace you signed in to.

You can also add it by hand. Open Settings, then Connectors, choose Add custom connector, name it Dance Party, and paste the server URL:

https://app.danceparty.ai/api/mcp

Connect Claude Code

Run this once:

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

This registers Dance Party for every project. Start Claude Code, run /mcp, select Dance Party, and follow the authentication prompt. Sign in to your Dance Party workspace in the browser and approve access. Return to /mcp to confirm the connection.

Connect Cursor

Open this link on the computer where Cursor is installed. Review the server configuration in Cursor and confirm the installation, then sign in to Dance Party when prompted.

Add Dance Party to Cursor

The link installs this remote server configuration:

{
  "url": "https://app.danceparty.ai/api/mcp"
}

Confirm Dance Party is connected in Cursor’s MCP settings. Installing the configuration and signing in are separate steps.

Connect Codex

Add this table to ~/.codex/config.toml. If Dance Party is already configured, update its existing table. Preserve your other settings.

[mcp_servers.dance-party]
url = "https://app.danceparty.ai/api/mcp"

Then sign in:

codex mcp login dance-party

Approve access in the browser, then start a new Codex session. Run /mcp to confirm Dance Party is available.

Other AI assistants

Any assistant that supports remote MCP servers with sign-in can connect. Add a remote MCP server, paste the server URL, and sign in to Dance Party when it asks.

https://app.danceparty.ai/api/mcp

These instructions use Streamable HTTP with OAuth sign-in. You need a Dance Party account and workspace; connect your data sources in the Dance Party web app before asking for live data. The separate /api/mcp/chatgpt endpoint is for ChatGPT only. Do not use it for the clients above.

Tools

Seven tools only read:

  • list_data_sources The integrations connected to your workspace, and the ones you could connect.
  • preview_data A live sample from one connected integration, or from a public JSON or RSS URL, so the widget is built on real data.
  • list_dashboards The dashboards you can see in this workspace.
  • read_dashboard_widgets The widgets already on a dashboard, so new ones match their style.
  • show_dashboard The dashboard layout and render state, with a preview card in clients that support MCP Apps.
  • get_dashboard_layout Where every tile sits on a dashboard's grid.
  • read_context_file Notes your admins wrote about your data, such as field names and definitions.

Three change your Dance Party workspace:

  • create_dashboard Creates a new, empty dashboard in your workspace.
  • set_dashboard_layout Moves or resizes the existing tiles on a dashboard.
  • deploy_widget Adds a widget to a dashboard, or replaces one.

Your client controls tool approvals. In clients that support the preview card, three additional tools are reserved for the card UI: get_dashboard_preview, list_screens, and send_to_screen. The last one adds a dashboard to a TV’s rotation without replacing the current picture.

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. Things to ask:

  • “Build a pipeline by stage widget from HubSpot for the sales dashboard.”
  • “Add Stripe MRR to the office dashboard.”
  • “Show this week's website traffic from Google Analytics next to new signups.”

Good to know

  • Read-only on your integrations. It reads HubSpot, Stripe and every other connected provider and never writes to them. It changes dashboards and widgets in your Dance Party workspace; the preview card can also add a dashboard to a TV’s rotation.
  • 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 Dance Party from Settings, then Connectors in Claude, or run claude mcp remove dance-party in Claude Code.
  • “This request is no longer active.” That sign-in link can no longer be used. Check Settings, then Connectors in Claude. If Dance Party shows as connected, you are done. If not, start the connection again from there.
  • Support. Email chris@danceparty.ai.